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

Lesson 6 of 6

End-to-end S2P test design

9 min

Listen to this lesson

0:00 / 6:19

An end-to-end source-to-pay test crosses at least four systems and two companies: the requester in Ariba, the buyer and accounts payable in S/4HANA, the network, and the supplier. It succeeds only if every party sees the right thing at each step. That makes it a coordination exercise as much as a test design: test realms and accounts, supplier participation, data that exists in all systems, and an evidence plan per step.

The test environment

ComponentTest instance at ContosoNotes
S/4HANACMQ client 100Add-on connected to the managed gateway test project
Managed gatewayTest projectSame mappings as production; separate cross-references
SAP AribaTest realmMaster data exported from CMQ
Business NetworkBuyer test accountLinked to the test realm
SuppliersSupplier test accountsThree pilot suppliers, including Riverbend
Integration SuiteCMC_TESTOnly for any custom extensions

The connected test landscape; every component must point at its test partner, never production.

Test and production must never cross: a test PO reaching a supplier's production account is a real order.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-305

The core test set

CaseStartEndKey assertions
Catalog purchaseRosa in guided buyingPayment remittance in supplier accountMapping, single approval, account, 3-way match
Service purchaseService PO to RiverbendRemittanceService sheet approval; invoice equals service entry
PO changeQuantity change after confirmationUpdated order in supplier accountNo duplicate order
Partial confirmation and ship noticeSupplier confirms 30 of 40Inbound delivery for 30Open quantity correct
Invoice exceptionInvoice above receiptPayment block, Ana resolvesBlock reason, resolution log
Network rule rejectionInvoice without PORejection in supplier accountNothing in S/4HANA
Sourcing to contractEvent in Ariba SourcingContract used as sourcePrices equal on both sides
PO above 25,000 USDGuided buying requestFlexible workflow approval in S/4HANAApproval before output

Contoso's core end-to-end S2P cases.

A two-week cycle: preparation, execution, a real payment run in CMQ, and evidence review.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-305

Evidence per step

  • Ariba: requisition with approval history and follow-on document IDs.
  • S/4HANA: PR, PO with output status, confirmation, inbound delivery, goods receipt or service entry, supplier invoice, journal entries, payment document.
  • Managed gateway: transaction tracker entries per document, with status.
  • Business Network: buyer outbox and inbox entries.
  • Supplier: screenshots or exports from the supplier test account showing order, confirmation, invoice status and remittance.
Few systems, rareManual credit memo: one test per release
Many systems, rareSourcing to contract: full end-to-end each release
Few systems, frequentPO approval above 25,000 USD: automate in S/4HANA regression
Many systems, frequentCatalog purchase to payment: end-to-end every cycle, supplier view included
Where to spend end-to-end effort: frequent, multi-system flows get full coverage every cycle.
The Sign-Off Table · thesignofftable.com/academy/sap-mm-305

After go-live: regression with a moving partner

Ariba and Business Network are cloud services with frequent updates, and next-generation SAP Ariba features will arrive through 2026 and 2027. SAP's release notes for each update are an input to Contoso's regression plan: Priya's team reviews them, maps changes to the core cases, and runs the affected cases in the test landscape. S/4HANA releases trigger the same set from the other side.

Working with suppliers in testing

Suppliers are not Contoso's testers, and their time is limited. Contoso's approach: a one-page script per supplier with the exact documents to expect and to send, a fixed two-day window, and a named contact on both sides. For suppliers that cannot take part, Omar's team logs on to a Contoso-owned test supplier account and plays the supplier role, which proves the technical flow but not the supplier's own process. The test report marks which cases had a real supplier and which a simulated one, so the residual risk is visible at sign-off.

What would you do?

Halfway through the cycle, a pilot supplier says it received a "real" order for 40 bearings from Contoso in its production account, matching a test PO. What should Priya do first?

Key points
  • End-to-end S2P spans Ariba, S/4HANA, the gateway, Business Network and the supplier.
  • Keep test and production strictly separated in every component.
  • Collect evidence from the supplier's test account, not only from the buyer side.
  • Use Ariba release notes to drive regression after go-live.

Check your understanding · not graded

Lesson check

  1. 1. Which S/4HANA test client does Contoso connect to the gateway test project?

  2. 2. What is the biggest risk if test and production routing cross?

  3. 3. Which end-to-end case proves a guided buying PO above 25,000 USD is controlled?

  4. 4. What should drive regression planning after go-live?