Show TOC

Background documentationConfiguration Options for Operational Contract Management Locate this document in the navigation structure

Procedure

The following provides a short overview regarding the standard and alternative configurations for central contracts. It outlines the use of Business Add-Ins (BAdIs) available for Operational Contract Management in SAP SRM and in the back-end system(s).

Note Note

When creating a central contract from the sourcing application of SAP SRM or from SAP Bidding Engine, the system uses the following logic:

  • It first checks whether the CT_PROC_TY attribute is maintained in the organizational plan. If so, the attribute determines the transaction type CCTR for central contacts.

  • If no attribute exists, the system checks the transaction type settings for follow-on documents. For more information, see Customizing for SAP Supplier Relationship Management under   SAP Implementation Guide   SRM Server   Cross-Application Basic Settings   Define Transaction Types  

  • If the transaction type settings are not available, the system uses the first transaction type for contracts that exists in the BBPC_PROC_TYPE table.

End of the note.

Process Alternatives

(I)

If a contract is to be created directly in the back-end system (with no copy in SAP SRM) you need to implement and activate a BAdI. This allows you to determine, for example, whether contracts of certain purchasing organizations are to be created directly in a back-end system or in SAP SRM.

You have two optional BAdIs at your disposal to change the data, before actually creating a contract in the back-end system, one in SAP SRM, the other in the back end system.

(II)

In the standard, the system creates a central contract, from the sourcing application in SAP SRM or from SAP Bidding Engine, depending on system customizing.

  • You can distribute the central contract to one or more back-end systems

    You can determine in the central contract which contract type shall be used for creation in the backend system. Ultimately, it depends on the document type Customizing in the back-end system

  • The BAdI (B1 in the figure above) that determines whether a contract is created directly in the back-end is either deactivated or the preconditions within the BAdI are not fulfilled. You have two optional BAdIs at your disposal to change the data, before actually creating a contract or a scheduling agreement in the back-end system, one in SAP SRM, the other in the back-end system (B2 and B3 in the figure).

For more information, see Making Settings for Central Contracts

(III)

When creating a central contract from the Contract Management application of SAP SRM, the system does not use BAdI B1. The implementation of BAdIs B2 and B3 is optional. For more information, see Making Settings for Central Contracts .

Note Note

BADI B3 is only relevant for scheduling agreements created in SAP SRM.

End of the note.