Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 3 of 6

Guided buying and intake into S/4HANA

10 min

Listen to this lesson

0:00 / 6:49

Guided buying is the consumer-style front end of SAP Ariba Buying: requesters search catalogs and forms, get policy guidance, and submit requests that route for approval. The integration question is where the requisition and the purchase order live. SAP's integration scenario for guided buying with S/4HANA (scope item 2NV, via the managed gateway) supports, broadly, two patterns described in SAP Community material: the PO is created and sent in Ariba with numbers copied to S/4HANA for reference, or the approved requisition is replicated to S/4HANA as a purchase requisition and the PO is created in S/4HANA. Contoso uses the second pattern so that S/4HANA stays the system of record for POs, receipts and invoices.

Contoso's guided buying pattern: approval in Ariba, PR and PO in S/4HANA, follow-on numbers back to the requisition for traceability.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-305

Worked example: Rosa orders bearings

Rosa, the Detroit maintenance planner, needs 40 bearings for the rotor line. She finds them in the MRO supplier's catalog in guided buying at 85.00 USD each, 3,400.00 USD in total, for plant 1710 with account assignment to cost center 17101107 Detroit Rotor Line. Guided buying checks the budget, routes the request to her manager, and after approval sends it through the managed gateway. S/4HANA creates a purchase requisition and converts it into a purchase order; the PO goes to the supplier through Business Network. Guided buying shows Rosa the PR and PO numbers and later the receipt and invoice status.

Field in guided buyingS/4HANA fieldRosa's value
Company codeCompany code1710
Ship-to / plantPlant1710, delivered to maintenance
Purchasing unitPurchasing organization and group1710 / 001
Account assignmentAccount assignment category and cost centerK, 17101107
Commodity codeMaterial groupMRO bearings (illustrative)
SupplierSupplier numberMRO supplier 17300030 (illustrative)

Field mapping for one guided buying line; each mapping is a test assertion.

Approvals: one place, not two

Contoso's approval rules in S/4HANA are purchase requisitions over 10,000 USD need release and purchase orders over 25,000 USD need approval in flexible workflow. Guided buying has its own approval flows. If both apply, a requisition is approved twice and buyers chase two inboxes. Contoso's design (illustrative): approval of guided buying requests happens in Ariba; the replicated S/4HANA requisitions use a document type without release strategy; and the 25,000 USD PO approval in S/4HANA still applies, because it is the finance control Dan relies on. Testers check both thresholds on both sides.

  1. Was the request approved in guided buying?Yes → replicate to S/4HANA as PR · No → stays in Ariba
  2. Does the replicated PR document type have a release strategy?Yes → double approval: defect in Contoso's design · No → convert to PO
  3. Is the PO value above 25,000 USD?Yes → flexible workflow approval in S/4HANA · No → output to Business Network
Contoso's approval logic across the two systems.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-305
The requisition's life across both systems; the Error state is where most integration tests find defects.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-305

Intake management

SAP Ariba Intake Management, generally available since April 2026, is a front door for any procurement request, including requests that are not catalog purchases (new suppliers, contracts, software). It routes the request to the right process, which may end in guided buying, sourcing or a contract. For S/4HANA integration it changes little at first, because the documents that reach S/4HANA are still requisitions and orders. For testers it adds a new start point: end-to-end cases now begin in intake, not in guided buying.

Step by step: testing one guided buying request

  1. Log on to guided buying in the test realm as a test requester with Rosa's profile; choose the catalog item and quantity.
  2. Enter account assignment cost center 17101107 and submit; capture the budget check result and the approval route.
  3. Approve as the test manager; note the time of approval.
  4. In the gateway tracker, find the requisition message and its status; in CMQ, find the purchase requisition and the PO created from it.
  5. Compare field by field against the mapping table; check that no S/4HANA release was required.
  6. Check PO output to the supplier test account; then confirm, receive and invoice, and check the journal entry account.
  7. Back in guided buying, confirm that the requisition shows the PO, receipt and invoice references.

What would you do?

A guided buying request for 12,500 USD of safety equipment arrives in S/4HANA as a PR and waits for release in Omar's inbox, although the manager approved it in guided buying. What should the team conclude?

Key points
  • Contoso replicates approved guided buying requisitions to S/4HANA as PRs; POs are created in S/4HANA.
  • Every field mapping is a test assertion; check account assignment down to the journal entry.
  • Approvals in one place: avoid double approval across Ariba and S/4HANA.
  • Intake Management adds a new start point for end-to-end cases.

Check your understanding · not graded

Lesson check

  1. 1. Which scope item covers guided buying with S/4HANA via the managed gateway?

  2. 2. In Contoso's pattern, where is the purchase order created?

  3. 3. Rosa orders 40 bearings at 85.00 USD. What is the total?

  4. 4. Why must testers check the journal entry for guided buying purchases?