Skip to end of metadata
Go to start of metadata


The purpose of this page is to provide admin users with a guide on the replication process of the central purchasing system.


The replication process is triggered by the central system through the application Schedule Import of Purchasing Documents F3268.

In the application the following replication programs can be scheduled:

  • Import Central Purchase Requisitions Relevant for Hub System Processing
  • Import Purchase Requisitions from Connected Systems
  • Import Purchase Orders from Connected Systems
  • Import Texts for Purchasing Documents from Connected Systems
  • Import History for Purchase Orders from Connected Systems


The replication objects have three import types: full import, delta import and ad-hoc import. 

The full import is the most important one, as it fills a timestamp value in the central system and creates cache data for the later delta and ad-hoc import to be used.

If Gateway caches are deleted in a central system a full import must be executed. 

Without a full import the delta and ad-hoc imports would not run.  

The replication programs run by the following ABAP programs:


These programs initialize a job object with the respective purchasing document object type, which will create an OData call to the connected system to fill the *EXT tables.


Every replication program was written in the same manner.

The programs will check if there are any other jobs running, if so then it will terminate.

If not, the program will call the given method EXTRACT_*_FROM_BACKEND.

Based on the load type the method will call an extraction method which can be extract_pr/po or extract_adhoc or extract_delta.

The extractor classes are:



The methods GET_PR_PACKETS or GET_PO_PACKETS will call the connected system with predefined filter criteria and will initiate a metadata call to the connected system.

For this filtered call the connected system will return a list of documents, which later will be replicated with the get_details method call.

Both method calls are using the connected service MM_PUR_PR_BULK_EXTRACT_SRV or MM_PUR_PO_BULK_EXTRACT_SRV

A typical best place to check if the call is sent to the connected system is the Method: IF_MMPUR_CAT_DATA_SRV_HUB~TRIGGER_SERVICE Class: CL_MMPUR_HUB_SRV.

The admin user can see here what call was made by the central system and what error the connected returned.

If the connected system returned an error, then the request URL can be used on the connected side in the gateway service maintenance to analyze the root cause further.

Related Content 

Related Documents 

Schedule Import of Purchasing Documents

SAP Community

How to create a Level 3 ICM Trace

Related SAP Notes/KBAs 

KBA:  3027455 - Descriptions are missing from Central Purchasing System

SAP Note: 2841251 - Central purchasing: Delta import fails with error.

SAP Note: 2838986 - Central procurement: Extraction of purchase orders from backend connected system fails.

SAP Note: 2847699 - Central Purchasing: Local PO extraction fails with an exception

SAP Note: 2849477 - Central Procurement - Adhoc import of PO fails to update the job status

SAP Note: 2690499 - Improvements for Purchase Order(s) Extraction from Connected systems

SAP Note: 2697328 - S/4HANA Schedule Import of Release Orders: Important corrections for importing of release order data for Central Contracts

SAP Note: 2941291 - Delta extraction of Purchase Requisitions fails

SAP Note: 2766037 - Additional properties expected by odata service during purchase requisition extraction for central procurement

SAP Note: 2698128 - Central purchasing Purchase Requisition extraction import correction

SAP Note: 2813226 - Central procurement: Delta import for text fails for Purchasing Documents from Connected Systems

SAP Note: 2852004 - Central procurement: Delta extraction of PO and PR fails after Delta text extraction.

SAP Note: 2834268 - Delivery address in not displayed in Manage PO centrally app

SAP Note: 2692262 - Improvements in Text Extraction for Purchasing Documents from Connected System

SAP Note: 2832585 - Supplier details are not shown in the Manage PO centrally app

SAP Note: 2964467 - Central Purchase order history extraction clears the header information once complete

SAP Note: 2970618 - Purchasing Document Status/Approval Status in Manage Purchase Orders Centrally

SAP Note: 2681190 - Workflow Improvements for Manage Purchase Order Centrally App

SAP Note: 2813569 - Incorrect termination of Central Purchasing local PO extraction

  • No labels