Process documentationSRM Central Contract Management

 

With the SRM central contract created in SAP Supplier Relationship Management (SAP SRM), buyers can determine release-authorized purchasing organizations in both SAP SRM and SAP ERP. The strategic buyer enters and edits the contract data in the SRM system. This data is then available for sourcing in both SAP SRM and SAP ERP.

Prerequisites

You must run a version of SAP Supplier Relationship Management.

You must make the following settings in Customizing in the ERP system:

  • Define document types

    When the SRM system transmits the data of the SRM central contract to the ERP system, it also transfers the document type. The standard document type for distributed contracts in SAP SRM is CCTR. This document type must also exist in SAP ERP. For this reason, define this document type in Customizing for Materials Management, under Start of the navigation path Purchasing Next navigation step Contract Next navigation step Define Document Types End of the navigation path.

  • Define number range

    The SRM central contract also gets a separate ERP contract ID in the ERP system, in addition to the ID transmitted from the SRM system. We recommend that you use a separate number range for SRM central contracts in SAP ERP. The number range is defined by the document type. For this reason, assign the document type (see above) to its own number range in Customizing for Materials Management, under Start of the navigation path Purchasing Next navigation step Contract Next navigation step Define Number Ranges End of the navigation path.

    Note Note

    If ERP and SRM number ranges for contracts are identical, you can use the BAdI BADI_MMBSI_SELECT_CTR_ID to define which contract is to be used.

    End of the note.

  • Assign conditions

    Assign the appropriate ERP condition types to the SRM condition types in Customizing for Integration with Other SAP Components, under Start of the navigation path Supplier Relationship Management Next navigation step Central Contract Next navigation step Assignment of Conditions End of the navigation path.

  • Migrate existing SRM contracts

    If you have distributed global outline agreements from SAP SRM to SAP ERP in a lower release (lower than SAP SRM 7.0 and SAP ECC 6.0, EHP 4), you must migrate these contracts in SAP ERP and SAP SRM. For more information, see the documentation of the migration report MMBSI_CONTRACT_MIGRATION.

Process

  1. Create central contract (SAP SRM)

    A strategic buyer creates the SRM central contract in SAP SRM.

    The original system of the SRM central contract is the ERP system. For this reason, you can create and change contract data in this system only. To ensure that you can always access current data in both systems, the SRM system transmits the changed data to the ERP system, if the changes are relevant to ERP. Due to the distribution of the data to the ERP system, there are fields in the SRM central contract that cannot be changed. For example, you cannot change the business partner.

    Note Note

    If you are not using an SRM system, you can create an ERP central contract directly in the ERP system, and also change the data in the ERP system. For more information, see ERP Central Contract.

    End of the note.

  2. Distribute central contract (SAP SRM)

    When the SRM central contract has the status Released in the SRM system, the SRM system sends the header and item data, plus hierarchy information and the information whether tolerance limits for exchange rates are defined, to the connected ERP systems.

    For more information about communication between the SRM and ERP systems, see Distribution of SRM Central Contracts to the ERP System.

  3. Create central contract (SAP ERP)

    The ERP system runs validation checks on receiving data from the SRM system. The ERP system transmits the result of the validation check, together with the contract ID assigned in the ERP system, back to the SRM system.

  4. Use central contract as source of supply (SAP ERP)

    After successful validation of the SRM central contract data from the SRM system, the buyer can now access the data in sourcing in the ERP system, and can propose or assign the SRM central contract to a purchase requisition or purchase order as a source of supply.

    For more information, see Sourcing with SRM Central Contracts.

  5. Creating a purchase order with reference to a contract (SAP ERP)

    Once the buyer has assigned a source of supply to the purchase requisition in the ERP system, he or she can create a purchase order from the requisition. The ERP system sends a request to complete the data of the SRM central contract to the SRM system.

  6. Run pricing (SAP SRM)

    On receipt of the request from the ERP system, the SRM system runs pricing and sends the results and further data to the ERP system. SRM-specific conditions may be used here, which take into account release values across several contract hierarchies.

    For more information, see Pricing for the SRM Central Contract.

  7. Update central contract (SAP SRM)

    Once you have saved the purchase order, the ERP system transfers the release information to the SRM system, to update the contract data in the SRM system. The exchange occurs either via enterprise services or via the IDoc BLAREL, depending on the ERP system you are using.

    For more information about communication between the SRM and ERP systems, see Distribution of SRM Central Contracts to the ERP System.

  8. Update document history (SAP ERP)

    The ERP system updates the history of the purchase requisition document with the data of the purchase order.

  9. Archive central contract (SAP SRM and SAP ERP)

    The SRM central contract is first completed in the SRM system, and then archived in the ERP system. Then you can archive in the SRM system. For more information, see Archiving SRM Central Contracts.