| |||||||||
Search results returned in Guided Buying catalog searches may appear in an unexpected order or certain catalog items may not be displayed as anticipated. Customers request clarification on how Guided Buying determines search relevance, filtering, and item visibility.
SAP Ariba Guided Buying
Guided Buying uses a multi-layered search logic where catalog results are processed through multiple filtering and relevance steps, including keyword matching, catalog views, supplier visibility rules, and system-level filters.
When a search is executed in Guided Buying (P2P), the request is sent to Arches and evaluated through several search components, each applying specific rules.
The search logic consists of the following main parts:
This step processes the user-entered search term and applies locale-specific logic. The search runs across multiple catalog item fields, including:
Keywords
Supplier part number
Supplier name
Category name (catalog hierarchy leaf name)
Catalog visibility can be restricted based on user attributes such as group or cost center:
Catalog Views limit catalog subscriptions available to specific users or regions.
Item Constraints restrict individual catalog items based on user attributes.
Item constraints require an extensible field at the catalog item level to store the filtering value.
Supplier visibility rules depend on the customer’s realm variant:
SAP variant
Generic variant
PeopleSoft variant
Each variant applies supplier visibility logic differently during search execution.
This is the default system behavior applied across all Guided Buying configurations. It filters results based on:
Expiration date
Kit-only items
Guided Buying–specific filtering
Realm and partition
Short Name Boost
Parameter: Application.Catalog.Search.ShortNameBoost
When enabled, items whose ShortName contains matching keywords are boosted higher in the search results.
Popular Terms Boost
Parameter: Application.Catalog.Search.PopularTermsBoost
When enabled, frequently used search terms associated with popular items are indexed and boosted in future searches.
Multi-Term Split
Parameter: Application.Catalog.Search.MultiTermSplit
This parameter is being deprecated by engineering and should not be enabled for new customers.
Guided Buying