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

Lesson 5 of 6

Sourcing, contracts and master data flows

9 min

Listen to this lesson

0:00 / 6:33

Guided buying and Business Network only work if both sides agree on the reference data: suppliers, plants, purchasing organizations, cost centers, G/L accounts, material groups, units of measure, currencies and payment terms. And sourcing and contracts only pay off if their results reach the ordering system. This lesson covers the flows that feed the transactions: master data from S/4HANA to Ariba, and sourcing and contract results back.

Master data from S/4HANA to Ariba

With the managed gateway, master data is exported from S/4HANA to SAP Ariba solutions in scheduled full and incremental loads. Guided buying uses it for the values requesters can choose and for validation before replication. If master data is missing or stale in Ariba, requests are either impossible to submit or fail when they reach S/4HANA.

Master dataUsed in Ariba forContoso check
Company codes, plants, purchasing organizations and groupsShip-to, purchasing unit, approval routing1710 and 1720 present; purchasing group 001
Cost centers and G/L accountsAccount assignment choices and validationAll active cost centers, such as 17101107, present and valid
SuppliersSupplier selection, catalogs, network linkingEvery network-enabled supplier linked to its S/4HANA number
Material groups (commodity codes)Classification and account derivationMapping table to Ariba commodity codes complete
Units of measure, currencies, payment termsLine validationSame codes on both sides

Master data Contoso exports to Ariba and the check for each.

The links that must hold: S/4HANA suppliers to Ariba suppliers to network accounts, and Ariba contracts to S/4HANA outline agreements where that scenario is used.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-305

Sourcing results back to S/4HANA

In the sourcing integration with S/4HANA, an RFQ can start from S/4HANA purchase requisitions or be created in SAP Ariba Sourcing; suppliers bid in the sourcing event; and the award returns to S/4HANA, where it can become a purchase order or a contract, depending on the scenario configured. Contoso's first case is the annual MRO supply agreement: Omar runs an event with four suppliers for 120 MRO items, awards to one, and the award is created in S/4HANA as a contract that guided buying and S/4HANA purchasing then use as a source.

  1. PrepareOmar defines the event in SAP Ariba Sourcing: 120 items, 4 invited suppliers
  2. BidSuppliers bid in their Business Network accounts
  3. AwardOmar awards; approval per sourcing rules
  4. TransferAward sent through the managed gateway to S/4HANA
  5. CreateContract (outline agreement) created in S/4HANA with prices
  6. UseSource determination finds the contract for new requisitions
From sourcing event to contract in S/4HANA: the award is only useful once purchasing finds it as a source.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-305

Contracts

SAP Ariba Contracts manages the contract workspace and documents; depending on the scenario, contract terms are replicated to S/4HANA as outline agreements so that release orders reference them, or referenced in Ariba for catalog pricing. Either way, testers check that the price a requester sees in guided buying equals the contract price in S/4HANA, and that a contract expiry stops its use on both sides.

Master data reaches requesters only after a successful export; a failed job silently keeps old values in Ariba.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-305

Supplier master data from the other direction

Some data starts on the supplier side. If SAP Ariba Supplier Lifecycle and Performance is used, new suppliers register and qualify in Ariba, and the approved supplier is created in S/4HANA as a business partner in the supplier role. Contoso does not use it in phase one; supplier creation stays in S/4HANA with its existing approval. But bank details deserve a specific test either way: a supplier changing its bank account in a network profile must not change the bank account used for payment in S/4HANA without Contoso's own control, because that is a classic fraud path.

DataMasterDirection at Contoso
Supplier general and purchasing dataS/4HANAS/4HANA to Ariba
Supplier bank details for paymentS/4HANA, changed only with dual controlNever overwritten from the network
Catalog content and pricesSupplier and Omar (approval)Catalog in Ariba, contract in S/4HANA
Network account and contactsSupplierStays on the network

Who masters which supplier data.

What would you do?

Requesters see last year's price for an MRO item in guided buying, while S/4HANA has the new contract price from the recent sourcing award. What should Omar check first?

Key points
  • Master data flows from S/4HANA to Ariba in scheduled full and incremental loads.
  • Supplier links (S/4HANA, Ariba, network account) are the most critical master data.
  • Sourcing awards return to S/4HANA as POs or contracts, depending on the scenario.
  • Know the export schedule; new values are not usable until the next load.

Check your understanding · not graded

Lesson check

  1. 1. How does S/4HANA master data reach SAP Ariba with the managed gateway?

  2. 2. Why did a new cost center fail in a guided buying test?

  3. 3. Where can a sourcing award be created in S/4HANA?

  4. 4. Which link must exist for a supplier to collaborate on the network?