Purchase Order Change – without leaving Central Procurement
Modify replicated purchase orders directly in SAP Ariba Central Procurement. No ERP context switch, no waiting for sync. Built on RAP and standard SAP APIs – Clean Core compliant from day one.
PO changes require an ERP detour – until now.
In a standard SAP Ariba Central Procurement setup, purchase orders are replicated from connected ERP systems (SAP ERP or S/4HANA) into the Ariba realm. Any subsequent changes to those POs – price, quantity, currency – have to be made in the originating ERP, then wait for synchronisation back to Central Procurement.
For buyers working centrally, this means constant context switching between systems with different interfaces and versions. The ASAPIO PO Change service eliminates this entirely.
- Open PO in Ariba Central Procurement
- Switch to connected ERP system
- Locate the same PO in ERP interface
- Make changes in ERP
- Wait for synchronisation back to Ariba
- Open PO in Ariba Central Procurement
- Click Change via the object link
- Modify price, quantity or currency
- Standard approval workflow triggers
- Done – no system switching
How the PO Change flow works
The change is triggered via object link access directly from the "Manage Purchase Order Centrally" app. GR and IR status is checked via standard APIs before the change is applied, and any configured approval workflow runs automatically.
Built for Central Procurement users – and for IT.
The PO Change service is designed to work with your existing landscape, not against it. Clean Core by architecture, delivered via standard transport.
Built on SAP ABAP RESTful Application Programming Model (RAP) and standard APIs throughout. No modifications to SAP standard objects – eligible for S/4HANA upgrade certification.
Buyers work in a consistent Fiori interface across all connected ERP backends. No system-specific screen navigation to learn or maintain across different ERP versions.
System switching is eliminated. Changes, GR/IR checks, and approval workflows all happen within Central Procurement – reducing errors and processing time.
Changes trigger the configured approval workflow automatically. No custom workflow logic required – the standard SAP approval process runs end to end without exception handling.
Delivered via SAP transport request into your S/4HANA or ERP system. Fits standard change management processes – no additional middleware or deployment infrastructure required.
Price, quantity, and currency are supported out of the box. The architecture is explicitly designed to be extended for additional PO fields without modifying the core implementation.
See PO Change in action
A walkthrough of the complete PO Change workflow – from object link access in "Manage Purchase Order Centrally" through the change form, GR/IR validation, and approval routing.
ASAPIO PO Change – full workflow demo in SAP Ariba Central Procurement
Questions about PO Change or Central Procurement?
Krystsina and her team have implemented Central Procurement and the PO Change service for global enterprises across multiple industries. Whether you're scoping a new Central Procurement rollout or extending an existing one, get in touch for a direct conversation.