Read this first
Guided buying is a lens over SAP Ariba Buying, not an application that owns anything.
It renders a consumer-grade surface for casual users and functional buyers. It does not own the requisition, the catalog, the commodity code, the contract, the supplier record, or the approval flow. Every one of those lives in the underlying solution; guided buying shows a filtered projection of it. That splits every “can we make it do X?” question in two: does the Buying configuration support X, and does guided buying expose X to this user, in this purchasing unit?
Design questions get answered at layer one. Support tickets almost always land at layer two. Across the 612 indexed guided buying articles the split is 289 Problem to 269 How To — near 1:1. Strategic Sourcing runs 2.5:1 the other way. Sourcing generates questions; guided buying generates symptoms — what you'd expect from a thin presentation layer over a deep transactional one.
The dependency order
Enablement fails on sequencing more often than on any individual step. Things have to exist before they can be pointed at.
| # | Step | Depends on | Owner |
|---|---|---|---|
| 1 | Enable the guided buying capability | SAP-side activation, plus enablement parameters in ICM | SAP + Customer Administrator |
| 2 | Users, groups, purchasing units | Master data import (PurchasingUnit.csv, user/group loads) | Customer Administrator |
| 3 | Commodity codes and accounting master data | ERP extract, UNSPSC mapping | Data lead |
| 4 | Catalogs — CIF, cXML, punchout, order-from-contract | Suppliers active in Ariba; valid commodity codes | Catalog Manager |
| 5 | Contracts for compliance buying | Catalogs and suppliers | Contracts lead |
| 6 | Approval processes compatible with guided buying | Purchasing units, groups | Process lead |
| 7 | Landing pages and tiles | Everything above — tiles point at catalogs, commodity codes and forms | Guided buying admin |
| 8 | Policies | Suppliers, commodity codes, form fields | Guided buying admin |
| 9 | Custom forms and RFQ | Field configuration; form approval processes | Forms admin |
| 10 | Help community and contextual help | Content authoring | Enablement lead |
Step 7 is where the order bites. A tile is a pointer. Point it at a catalog that hasn't been activated, or a commodity code that isn't loaded and enabled, and it fails at creation — the class behind “No Catalog is found for uniqueName” and “Classification code … does not map to a Commodity Code object.” Teams that build landing pages early to have something to demo rebuild them later.
| Activity | Estimate |
|---|---|
| Basic enablement | 1–2 weeks |
| Catalog configuration | 2–4 weeks |
| Custom forms | 2–6 weeks |
| Help community | 1–2 weeks |
| Testing and adjustment | 2–4 weeks |
| Typical total | 8–18 weeks |
If someone sold guided buying as a four-week UI project, that range is the conversation to have early.
The two parameter namespaces
ICM parameters use dot notation. A large part of guided buying's own behaviour is controlled by parameters in an entirely different convention — UPPER_SNAKE_CASE with a PARAM_ prefix. Searching one convention will not surface the other.
Application.Buying.Catalog.enablePunchout Application.Base.Approval.escalationPeriod PARAM_ENABLE_NEW_CHECKOUT PARAM_ENABLE_ADDING_GROUP_APPROVERS_TO_APPROVAL_REQUEST
- Not finding a parameter usually means SAP-controlled, not absent
- Visible in ICM but not directly editable — changing it means a change request SAP reviews and deploys. Budget calendar time.
- ICM validates the data type, not the range
- Any value of the correct type will save, including values meaningless for your business. Check the ICM Parameters Reference first.
- Only the most recent deployment can be reverted
- There is no full version history. Beyond N−1 it is forward-fix only. Plan package granularity around that.
- Parent-child landscapes inherit downward only
- Parent-site changes reach children; child changes never propagate up or sideways. Decide deliberately what belongs in the parent.
Landing pages are not cosmetics
BNS-ARI-GB-ADM-LP carries 43 indexed articles — the fifth-largest guided buying component, ahead of catalog (38), preferred suppliers (28), custom forms (23) and policies (14). For something widely treated as a styling exercise, landing page configuration is a top-five driver of support volume.
Tiles are typed pointers
The target must exist and be enabled at the moment the tile is created. Creation-time failures are dependency failures, not UI bugs.
Landing pages are scoped by purchasing unit
The decision that matters most and gets made most casually. Fix the purchasing-unit matrix before building; every variant is permanent maintenance.
Search behaviour differs from classic
Keyword matching, tile searchability and result limits are configured, and the guided buying result limit differs from classic. Have the answer ready.
Translation fails separately
Landing page, policy and default field translations each have their own failure modes. A working English site tells you nothing about the others.
Bulk config is Excel or JSON
Both have documented failure modes, including duplicate home pages and malformed JSON blocking a catalog publish. Version these files — they are code.
Policies are the actual product
If guided buying's value proposition is “the system guides the user,” policies are where the guiding happens. Everything else is navigation.
| Policy type | What it does |
|---|---|
| Supplier policy | Steers users toward preferred and qualified suppliers; flags or blocks others |
| Touch policy | Determines how much process a request gets — light touch for low-risk, full process for the rest |
| Validation policy | Blocks or warns on requests that violate a rule, evaluated against request fields |
| Justification policy | Requires the user to record a reason when going off-policy |
- 01
A policy that triggers is not necessarily one the user sees.
There's an indexed problem for supplier and touch policies triggering but not displaying. Test what the user experiences, not just whether the rule evaluated.
- 02
Field evaluation is the usual root cause.
When a policy silently does nothing, suspect the field reference before the rule logic.
- 03
Commodity code hierarchy needs explicit testing.
If your policy is written against a parent node, verify what happens with child codes — don't assume inheritance.
- 04
Justification data is only useful if you can report on it.
Confirm the reporting path during design, or you'll have collected compliance evidence you cannot extract.
A guided buying rollout with beautiful tiles and no policies is a catalog search engine.
What guided buying does not do
Documented explicitly, and worth quoting into a scope document. Guided buying does not replace SAP Ariba Procurement solutions for:
- Demand aggregation
- Asset receiving
- Complex services procurement
- Invoice reconciliation
- Advanced payments
Those users stay in the full Buying interface, so most real deployments are dual-surface: casual users in guided buying, procurement professionals in Ariba Buying, sometimes meeting on the same document. Design the handoff deliberately.
The same applies to error visibility. ERP push errors are documented as not visible in guided buying — a requisition the user believes is fine can be failing downstream where they cannot see it. Someone else has to watch the ERP-side monitors. That ownership gap belongs in your support model, not in a footnote.
Configuration failure patterns
| Symptom | Usual cause | Where to look |
|---|---|---|
| Guided buying not visible to a user | Capability not enabled, or user not in the right group | User's group membership; enablement parameters |
| User sees the wrong tiles or landing page | Purchasing unit scoping | Landing page ↔ purchasing unit assignment |
| Tile can't be created | Target catalog, commodity code or form missing or disabled | Activate the target first; confirm commodity code is enabled |
| Landing page import fails | Duplicate home page, malformed JSON/Excel | Import log; validate the file before upload |
| Policy doesn't fire | Field evaluates false; child commodity code not covered | Policy field references; test hierarchy explicitly |
| Policy fires but user sees nothing | Display-side issue, distinct from evaluation | Test as an end user, not as an admin |
| Supplier not shown as preferred/qualified | Supplier management data not surfacing to guided buying | Supplier qualification status; BNS-ARI-GB-PQS |
| Commodity code search returns nothing | Codes not loaded, disabled, or classifier upload failed | Commodity code master data; ad-hoc classifier load |
| Custom form field not reaching the requisition | Widget-to-field mapping | Form field mapping to requisition header/line custom fields |
| Form name unchanged after revision | Revision/publish behaviour | Republish; verify the revision took effect |
| Translations not displaying | Per-object translation configuration | Landing page, policy and default-field translations, separately |
| Requisition fine in guided buying, absent in S/4HANA | Integration scenario behaviour | BNS-ARI-GB-IES; ERP-side monitors |
| Parameter “doesn't exist” | Wrong namespace, or SAP-controlled | Search both PARAM_* and Application.*; check the SAP-controlled flag |
A note on the integration component. BNS-ARI-GB-IES (17 articles) covers guided buying against S/4HANA integrated scenarios — scope items 2NV and 3EN. Recurring themes: approved requisitions not updating in S/4 or showing as blocked, multiple Ariba orders for a single S/4 purchase order, contract reference numbers not replicating, and fields missing from the outbound requisition payload. Read that component during design, not during hypercare.
Error messages decoded
The exact strings people paste into a search box, and the layer each one actually comes from. Guided buying rarely tells you which of the two layers failed — this table does.
| Message | What it actually means | What to do |
|---|---|---|
No Catalog is found for uniqueName | A tile points at a catalog that is not activated in the target environment, or was activated only in TEST. | Activate the catalog subscription, republish it, then recreate the tile. The tile stores the reference at creation time. |
Classification code … does not map to a Commodity Code object | The UNSPSC or ERP classification on the item has no enabled commodity code counterpart in Ariba. | Load or enable the commodity code, then re-run the classifier upload before retrying the tile or catalog publish. |
Landing page import failed / duplicate home page | The Excel or JSON definition declares a second home page for a purchasing unit that already has one, or the JSON is malformed. | Read the import log line number, remove the duplicate home flag, validate the JSON, and re-import. Keep the file in version control. |
Parameter does not exist | You searched one namespace only. ICM parameters use Application.* dot notation; guided buying's own parameters use PARAM_UPPER_SNAKE_CASE. | Search both conventions. If it appears but is not editable, it is SAP-controlled and needs a change request with calendar time budgeted. |
You are not authorized to view this page (guided buying tile or form) | Group membership or purchasing-unit scoping, not the tile itself. Guided buying filters what the underlying Buying configuration already permits. | Check the user's group memberships and the purchasing unit assigned to their landing page, then re-test as that user rather than as an admin. |
Requisition approved in guided buying, missing in S/4HANA | An ERP push error under BNS-ARI-GB-IES. These errors are documented as not visible in guided buying. | Check the ERP-side monitors and the integration scope item (2NV or 3EN). Assign explicit ownership for this monitoring in your support model. |
Policy fires in test but the user sees nothing | Evaluation and display are separate behaviours for supplier and touch policies. | Verify the policy field references, then test the end-user journey in the browser instead of reading the evaluation result. |
Commodity code search returns no results | Codes not loaded, loaded but disabled, or an ad-hoc classifier upload that failed silently. | Confirm the commodity code master data is enabled, then re-run the classifier load and check its status before blaming the search configuration. |
Parameter reference
The parameter names people search for verbatim, and which of the two namespaces each one lives in. If a name below returns nothing in your tenant, search the other convention before concluding it does not exist — and if it appears but will not save, it is SAP-controlled and needs a change request.
| Parameter | Namespace | What it governs |
|---|---|---|
PARAM_ENABLE_NEW_CHECKOUT | Guided buying (PARAM_) | Switches the requester checkout experience. Test the full approval journey after changing it — the checkout is where policy display and approval preview surface. |
PARAM_ENABLE_ADDING_GROUP_APPROVERS_TO_APPROVAL_REQUEST | Guided buying (PARAM_) | Controls whether group approvers can be added to an approval request. Changes approval flows already in flight, so validate against your approval rules before enabling. |
Application.Buying.Catalog.enablePunchout | ICM (Application.*) | Site-level PunchOut enablement for Buying, which guided buying tiles depend on. Guided buying cannot expose a PunchOut catalog the underlying Buying configuration does not allow. |
Application.Base.Approval.escalationPeriod | ICM (Application.*) | Approval escalation timing at site level. ICM validates the data type, not the range — a value of the right type saves even when it makes no business sense. |
This is a working subset, not the full list. The authoritative inventory is the ICM Parameters Reference for your release — read it before assigning a value, because ICM will happily accept a correctly typed value that is meaningless for your business.
Pre-go-live checklist
Configuration
- Capability enabled and verified in the target environment (not just TEST).
- Every landing page tested as a real user, in every purchasing unit that has a variant.
- Tile targets confirmed active: catalogs activated, commodity codes enabled, forms published.
- Each policy tested for BOTH evaluation and user-visible display.
- Policy behaviour verified against child commodity codes, not just parent nodes.
- Every translation tested per object type.
- Landing page JSON/Excel definitions committed to version control.
Operations
- Justification / off-policy reporting path confirmed to produce extractable data.
- Handoff to full Ariba Buying tested for the professional-buyer journey.
- Redirect group behaviour verified — users land where you intend on login.
- Someone owns ERP-side error monitoring for documents guided buying users can't see.
- ICM packages named descriptively; team briefed that only the last deploy is reversible.
- Search result behaviour explained to users who also work in classic buying.
- Help community content published and linked, if in scope.
Frequently asked questions
- What is guided buying in SAP Ariba?
- Guided buying is a simplified, policy-aware buying interface on top of SAP Ariba Buying. It routes casual requesters through landing pages and tiles to catalogs, contracts and forms, applying policies as they shop instead of after they submit.
- How long does a guided buying implementation take?
- Basic enablement takes 1–2 weeks, but a realistic end-to-end deployment including catalogs, custom forms, help content and testing typically runs 8–18 weeks depending on how many purchasing units and form types are in scope.
- What is the correct configuration order for guided buying?
- Enable the capability first, then load users, groups and purchasing units, then commodity codes and accounting master data, then catalogs and contracts, then approval processes. Landing pages, tiles, policies and custom forms come last because they point at everything built before them.
- What is the difference between guided buying and SAP Ariba Buying?
- Guided buying targets occasional requesters with a consumer-style, guided journey. Full Ariba Buying remains the workspace for professional buyers who need line-level control, mass edits and the complete requisition and order toolset. Most deployments run both and hand off between them.
- Why are my guided buying policies not firing?
- The most common cause is testing only against a parent commodity code. Policy evaluation and user-visible display are separate behaviours, so verify both, and test against child commodity codes and each purchasing unit variant rather than a single sample.
- Can guided buying changes be rolled back?
- Only the last ICM deployment is reversible, so name packages descriptively and brief the team. Landing page JSON and Excel definitions should be kept in version control as the real safety net.
- What does “No Catalog is found for uniqueName” mean in guided buying?
- The tile points at a catalog that is not active in that environment. A tile is a typed pointer resolved at creation time, so activate and republish the catalog subscription first, then recreate the tile. It is a dependency-order failure, not a UI bug.
- Why does a guided buying parameter say it does not exist?
- You are almost certainly searching one namespace. ICM site parameters use Application.* dot notation, while guided buying's own parameters use PARAM_UPPER_SNAKE_CASE. If the parameter appears but cannot be edited, it is SAP-controlled and requires a change request that SAP reviews and deploys.
- Why is a requisition approved in guided buying missing in S/4HANA?
- ERP push errors are documented as not visible in guided buying, so the requester sees success while the document fails downstream. Check the ERP-side monitors and the BNS-ARI-GB-IES integration scope items (2NV, 3EN), and assign explicit ownership for that monitoring.
- How do you scope landing pages by purchasing unit?
- Landing pages are assigned per purchasing unit, so fix the purchasing-unit matrix before building any pages. Every variant you create is permanent maintenance, and users seeing the wrong tiles is nearly always a scoping assignment rather than a page defect.
Glossary
- Guided buying
- Consumer-style buying surface integrated with SAP Ariba Buying / Buying and Invoicing, aimed at casual users and functional buyers
- ICM
- Intelligent Configuration Manager — central self-service site parameter management for Customer Administrators
- Landing page
- A configurable guided buying page, scoped by purchasing unit, composed of tiles
- Tile
- A typed pointer on a landing page to a catalog, commodity-code search, form or URL
- Touch policy
- Policy determining how much process a request receives, based on its characteristics
- Purchasing unit
- Organizational buying structure that scopes documents, catalogs, contracts and landing pages
- Punchout
- Buying from a supplier's own site embedded in Ariba, returning items as requisition lines (cXML or OCI)
- CIF
- Catalog Interchange Format — SAP Ariba's pipe-delimited catalog file format
- IES
- The guided buying component covering SAP S/4HANA integrated scenarios (scope items 2NV, 3EN)
- Configuration package
- ICM container grouping parameter changes for deployment from TEST to PRODUCTION
Grounded in SAP Help Portal documentation at release 2605 and 612 indexed guided buying articles within a corpus of 13,050 SAP KBAs and Notes (2013–2026). Read it before a design workshop, not instead of the SAP Help Portal.