Function documentationDistribution of SRM Central Contracts to the ERP System

 

A purchasing organization negotiates conditions for a concern (client), and the strategic buyer creates an SRM central contract with the corresponding information in the SRM system. The buyer specifies in which purchasing organizations the central contract is to be available as a source of supply, or sends a message to inform the purchasing organizations that a new central contract is available. The purchasing organizations can use a registration process to determine for themselves whether the central contract is to be available as a source of supply in their ERP system.

The buyer can also specify whether the central contract is also available locally in the SRM system for sourcing, or whether it is only for distribution to the ERP systems.

Note Note

Some of the fields that are at item level in the SRM central contract are at header level in SAP ERP. One example is the Terms of Payment field. In such cases, the ERP system may create several local contracts for one SRM central contract.

For more information about splitting the SRM central contract, see Splitting of SRM Central Contracts on Distribution.

End of the note.

Prerequisites

You are using version 7.0 or higher of SAP Supplier Relationship Management.

Features

For replication of the SRM central contract in the connected ERP systems, there are the following options, depending on the SAP ERP release you are using:

  • IDoc: This procedure supports communication if the ERP version you are using is below SAP enhancement package 4 for SAP ERP 6.0. You also use data transfer via IDoc if you want to create scheduling agreements from the central contract in an ERP system below enhancement package 4 for SAP ERP 6.0.

  • Enterprise Services: Enterprise services are used to distribute contracts to ERP systems as of SAP enhancement package 4 for SAP ERP 6.0.

Communication using IDoc is described below. For more information about communication using enterprise services and the setting up of the communication procedure, see the documentation for enterprise services.

Times of Data Transmission

The SRM central contract is replicated in the ERP system when the SRM central contract is released.

Distribution via IDoc

The SRM system uses the IDocs BLAORD and COND_A to transmit the data to the ERP system. When the ERP system receives the data, it makes validation checks. For example, the ERP system checks whether the supplier ID from the SRM central contract exists in the ERP system.

If you want to transmit data that is not included in the standard solution to the ERP system from the SRM system, you can use the Business Add-In Change Contracts and Conditions (BBP_CTR). For more information, see the documentation for the Business Add-In.

Distribution via Services

The following services are relevant to data exchange:

  • PurchaseOrderSRMPricingSimulateQueryResponse_Out

  • PurchasingContractSRMReplicationRequest_In

  • PurchasingContractSRMReplicationConfirmation_Out

  • PurchaseOrderERPContractReleaseNotification_Out

  • PurchasingContractSRMArchivingCheckQueryResponse_In

For more information, see the documentation of the enterprise services.

Error Handling

You can process events that have occurred during data transfer in the Postprocessing Office. To do this, call the transaction Edit Postprocessing Order (transaction code /SAPPO/PPO2) and specify the object type Purchasing Contracts (BUS2014).

For more information about postprocessing orders, see the documentation for the Postprocessing Office under Postprocessing Order.

More Information