Guide · SAP Ariba
SAP Ariba Scope Items 1ZM, 2NV, 42K: Which for S/4HANA?
Which SAP Ariba scope item fits your S/4HANA landscape in 2026: 2NV, 1ZM, 42K, 3EN or the CIG add-on. Decision tree, handoffs and test evidence.


For an on-premise S/4HANA system, the scope item is no longer a free choice. SAP has deprecated the Procure-to-Pay integration with SAP Ariba Buying and Invoicing (1ZM), so new work should start from Guided Buying with SAP Ariba Buying (2NV). Business Network commerce documents such as purchase orders, confirmations, ship notices and invoices run through 42K and the SAP Integration Suite managed gateway, and supplier master data is a separate track through SLP and the business partner model. Pick the path by process and by deployment edition, then test each handoff on its own.
Why the scope item code still matters
Most teams still say "the Ariba integration" as if it were one interface. It is not. Each scope item bundles its own set of services, connectivity options, configuration steps and support boundaries. If the project plan names the wrong code, the build team configures the wrong communication arrangements and the test team writes cases for a process the business never runs.
The code also tells you where to look. Scope items are how SAP maps a process to the best-practice content in SAP Best Practices and Activate, so the code on your project's scope list is the first thing to check against the SAP Help Portal entry for integration with SAP Ariba applications.
What changed from ECC
In ECC, the usual route was the Business Suite add-on for Ariba Network, which let the ERP send and receive cXML either directly or through SAP Process Integration. The 1ZM style of procure-to-pay integration relied on IDoc-based communication and middleware such as PI/PO or the Cloud Integration Gateway. That is the design you are retiring when you move to S/4HANA.
The biggest change is in how S/4HANA reaches Ariba. Integration with the Ariba Cloud Integration Gateway is now the standard route, and SAP's roadmap note 2705047 says standard integration scenarios for S/4HANA on-premise and Cloud Private Edition are being provided on CIG and standard APIs in the S/4HANA core component. The existing scope items can be changed to fit that new technology, so do not assume last year's scope item document still describes the current behavior. Check the note in SAP Community's discussion of the managed gateway add-on and then confirm the current status on SAP for Me.
| Scope item | What it covers | Status and connectivity for S/4HANA (2026) | Typical test owner |
|---|---|---|---|
| 1ZM: Procure-to-Pay with Ariba Buying and Invoicing | Requisition-to-invoice in Ariba Buying and Invoicing | Deprecated on-premise; no further enhancements. Plan a move to 2NV. | Procurement lead, Ariba consultant |
| 2NV: Guided Buying with SAP Ariba Buying | Guided buying and requisition replication from Ariba into S/4HANA | Current path for single-instance S/4HANA. Direct, CIG or SAP Cloud Integration connectivity. | Procurement lead, integration team |
| 3EN: Guided Buying for Central Procurement | Guided buying when S/4HANA for central procurement serves several backends | Uses separate web services for different operations; verify against the current scope item set-up guide. | Integration team, procurement lead |
| 42K: Automation of Source-to-Pay with SAP Business Network | POs, confirmations, ship notices, receipts, invoices and payment remittance exchanged with suppliers | Routed through the SAP Integration Suite managed gateway; the add-on is required for SAP Business Network for Supply Chain. | Integration team, AP and receiving leads |
| 4BL and 4AZ: Sourcing and Contracts | Sourcing projects and contract prices fed to S/4HANA | Supported on S/4HANA Cloud Public Edition and on-premise; set up separately from P2P. | Strategic sourcing lead |
Sources for the table are the SAP Help pages and the scope item documents linked in the Sources list below. Confirm the status column against the current Product Availability Matrix before you sign a design.
Decision tree: choose the path before you build
Work through these questions in order. Record the answer and the scope item code in your solution design so the test plan can point to it.
- Are you on S/4HANA Cloud Public Edition?Yes → use the Public Edition integration set-up, which does not support multi-ERP or the SystemID in the cXML payload · No → go to question 2.
- Do you still run Ariba Buying and Invoicing (1ZM) in production?Yes → open a migration item to 2NV now, because 1ZM will not be enhanced · No → go to question 3.
- Is the buying process guided buying with a single S/4HANA instance?Yes → 2NV · No, central procurement across several backends → 3EN.
- Do you exchange POs, confirmations, ship notices or invoices with suppliers on SAP Business Network?Yes → add 42K and the managed gateway add-on for S/4HANA · No → supplier documents stay outside the integration scope.
- Do you run sourcing events or contracts that set prices in S/4HANA?Yes → add 4BL and 4AZ with their own test cycle · No → skip them and record the decision.
Step 1: Confirm the deployment and the add-on version
Start with the edition. On-premise S/4HANA uses the add-on for S/4HANA. The SAP Help guide for the Cloud Integration Gateway lists the add-on as a component that must be installed on the S/4HANA system, and the Supported Systems page names the ARBCI1 software package and the add-on. Note that the add-on component list changes by release, so read the Supported Systems page for your S/4HANA release rather than copying a version from an old project.
Next, check the service pack cadence. For SAP Ariba 2602 and later, the add-on service pack is released four times a year, in February, May, August and November. The November 2026 service pack is due in this window, so check SAP's installation guide for the add-on for the support window before you schedule an upgrade in a freeze period.
Step 2: Set up the supplier master handoff
Most failed integrations break on supplier data, not on purchase orders. SLP is the supplier lifecycle piece, and it needs a clear rule for who owns the supplier record. The S/4HANA side uses the business partner model by default, and SAP's course notes say customers still on the old vendor model cannot use the bi-directional SLP integration. Confirm that before anyone builds a replication.
The supplier ID scheme also needs a test. In SLP, a supplier created manually in Ariba gets a placeholder ERP vendor ID that starts with VDR until it syncs to the integrated system and receives its real ID. If your import tasks add suppliers from S/4HANA without a business partner ID for each one, the ERP may treat the returning supplier as new. The SAP Help page on supplier IDs covers the field rules.
Direction matters too. SAP's course material says the integration is bi-directional only where the customer has an SLP entitlement; otherwise it runs one way. Your test script must match the entitlement on the contract, not the design you hoped for.
Step 3: Test each document handoff with its own evidence
Treat each message type as a separate test object. For a 42K purchase order, the minimum evidence set is:
- The S/4HANA purchase order (EKKO and EKPO) with the Ariba order reference kept in the external reference field.
- The outbound cXML OrderRequest captured in the integration monitor, with the buyer's network ID and the supplier's network ID visible.
- The supplier's ConfirmationRequest, ShipNoticeRequest and InvoiceDetailRequest posted back to S/4HANA, with the document numbers matched.
- A change, a cancellation and a rejected order, because error paths are where most defects appear.
- A rerun after a deliberate master data error, to prove the failure lands in monitoring and not in a silent drop.
For 2NV, add the requisition replication test. The purchase requisition from Ariba Buying should arrive in S/4HANA with the right account assignment, plant and purchasing group, and the test should include the approval path in your flexible workflow configuration.
If you are carrying PI/PO interfaces forward, the cutover is where the work doubles. Use the guide on testing migrated PI/PO interfaces in Integration Suite to build the parallel-run plan.
Who signs off what
The procurement lead signs the business outcome: order flow, receipts and invoice matching. The integration lead signs the message evidence and the error handling. The ERP test manager signs the master data rules and the end-to-end P2P run. Get all three signatures before go-live, not after the first supplier complaint.
Read the old documentation with care
Many public set-up guides date from the ECC and early S/4HANA era. One integration package document for 2NV still lists S/4HANA 1809 and 1909 as supported on-premise versions. Treat such dates as history. The scope items 2NV and 3EN integration document is useful for the flow design, but the version list must come from current SAP sources.
The same rule applies to the Joule-based features that now sit inside Ariba. If your team is also setting up AI features in Ariba, follow the entitlement and test checks in Joule in SAP Ariba: Setup, Entitlement and Test Checks, which covers the prerequisites that the scope item choice does not solve.
Where to go deeper
If your team is new to Ariba and S/4HANA, start with the free SAP Ariba and SAP Business Network with S/4HANA course, which covers integration scenarios and end-to-end testing. For the test sign-off side of procure-to-pay, the free Testing and Signing Off Procure-to-Pay course walks through the evidence you need. Integration leads who run the middleware should also take the Cloud Integration with SAP Integration Suite course.
For how Ariba testing fits inside the RISE responsibility split, read RISE with SAP: what it includes, and why testing is still your job.
Frequently asked questions
Is SAP Ariba Buying and Invoicing (1ZM) still supported with S/4HANA?
SAP's on-premise S/4HANA documentation says integration with SAP Ariba Buying and Invoicing is deprecated and will not be enhanced in upcoming releases. SAP recommends Guided Buying with SAP Ariba Buying (2NV) for the same business process. Any project that still plans 1ZM should open a migration decision now.
When do I need the 42K scope item instead of 2NV?
Use 42K when you exchange purchase orders, confirmations, ship notices, receipts and invoices with suppliers on SAP Business Network. The 2NV scope item covers guided buying and requisition replication from Ariba Buying. Many programs need both, and the add-on decision depends on the Business Network scope.
Does the managed gateway work with S/4HANA Cloud Public Edition?
Yes, SAP supports integration of S/4HANA Cloud Public Edition with the SAP Integration Suite managed gateway and SAP Business Network. The Public Edition set-up does not support multi-ERP scenarios or the SystemID in the cXML payload, so check those limits before you design a multi-ERP landscape.
Why does a supplier keep showing up as a new vendor after SLP sync?
The most common cause is a missing business partner ID on suppliers imported from the ERP into the Ariba procurement solutions. SLP uses a VDR placeholder ERP vendor ID until the supplier syncs back and receives its real ID. Check the ID mapping in your test data before each sync cycle.
Sources
- Integration with SAP Ariba Applications, SAP Help Portal, S/4HANA on-premise documentation
- Overview of Integrating SAP ERP or SAP S/4HANA with SAP Ariba Solutions Using SAP Integration Suite, Managed Gateway, SAP Help Portal
- Integrating SAP S/4HANA Cloud Public Edition with SAP Integration Suite, Managed Gateway and SAP Ariba Solutions, SAP Help Portal
- Supported Systems, SAP Help Portal, Ariba Cloud Integration Gateway migration guide
- Installing and Upgrading the Add-On for SAP ERP and SAP S/4HANA, SAP Help Portal
- Supplier IDs in SAP Ariba Supplier Lifecycle and Performance, SAP Help Portal
- Examining the Stipulations of SAP Ariba Supplier Lifecycle (SLP) Integration, SAP Learning
- Analyzing SAP Ariba Strategic Sourcing Integrations, SAP Learning
- SAP Ariba Integration scenarios with SAP S/4HANA Public Cloud system, SAP Community, SAP Spend Management blog
- Add-on for SAP Managed integration gateway for Ariba, SAP Community Q&A (quotes SAP Note 2705047)
- SAP Ariba Buying Integration with SAP S/4HANA Scope Items 2NV and 3EN, SAP API Business Hub document
- S/4HANA-ECC Integration with Ariba for Procure to Pay Business Process, SAP Community blog, 2020
Dates and release statements reflect the sources as found on 12 November 2026. Verify the current scope item status and add-on version in SAP for Me and the Product Availability Matrix before you finalize a design.
Free S/4HANA testing templates
Master test strategy, migration test plan, cutover runbook, go/no-go checklist and more.
The RISE Testing Playbook
One practical move a week for testing your ECC to S/4HANA transformation.
How this guide is made: researched with AI-assisted search across SAP documentation and practitioner sources, with every fact linked to its source. Found an error or have field experience to add? Tell us.