14.08.2013 Page 1 of 4

SAP Note 1268821 - SRM 7.0 / ERP 6.04: Config. of CentralContract Management

Note Language: English Version: 3 Validity: Valid Since 23.03.2009

Summary

SymptomYou want to configure the newly introduced integrated Procure-to-PayScenario Central Contract Management.

Other termsCCM, central contract, global outline agreement, GOA

Reason and Prerequisites1. You installed all required Business Package as mentioned in note1232945.2. You need SAP ERP 6.0 EHP4 and SAP SRM 7.0 installed in your landscape.

SolutionThe Procure-to-Pay Scenario Central Contract Management has beenintroduced newly with SAP Business Suite 7 and is designed as an integratedscenario between SAP SRM 7.0 and SAP ERP 6.04. It enables to use the SRMcentral contract as a source of supply in ERP.In what follows the technical steps to get the process up and runningare described.

Settings in SRM 7.0=================1.Configure Backend SystemsIn the SRM Server the table BBP_BACKEND_DEST must be maintained correctly.The settings can be done in the IMG.SAP Implementation Guide - SAP Supplier Relationship Management ->SRMServer ->Technical Basic Settings ->Define System LandscapeThis configuration should be done for all the ERP systems which areconnected to SRM. SLD Id should be maintained for each of the ERP systems.

2. Add WF-BATCH user to SRM Organization plan.WF-BATCH user should be added to SRM organization plan and this user shouldhave following roles: /SAPSRM/ST_PURCHASER and /SAPSRM/EMPLOYEE.

Settings in ERP 6.04=================1. Activate Business FunctionIn the ERP Systems you have to activate the EhP4 business function"Purchasing - SAP SRM Integration" (LOG_MM_P2PSE_1).

2. Register SRM SystemIn the connected ERP systems you have to register the SRM system: in IMGchoose-->Materials Management -->Purchasing -->Portal -->Set Up LandscapeThen select SRM System Connected and save your input. You must make thissetting so that links are created in the ERP applications used in thescenario.

3. Set Up Synchronous ServiceThe following synchronous service is used to get current pricing

14.08.2013 Page 2 of 4

SAP Note 1268821 - SRM 7.0 / ERP 6.04: Config. of CentralContract Management

information from SRM during ERP pricing (e. g. if you create a purchaseorder):

PurchaseOrderSRMPricingSimulateQueryResponse_In

For this service, SRM is the provider system and ERP is the consumersystem.

Following synchronous service is used to get the archival status of thereplicated contracts of ERP during archiving of Central Contract:

PurchasingContractSRMArchivingCheckQueryResponse_In

For this service, ERP is the provider system and SRM is the consumersystem.

If multiple ERP 6.04 systems are connected to the SRM system, configure thearchiving service for different destinations using the following IMGactivity in SRM:

SAP Implementation Guide - SAP Supplier Relationship Management ->SRMServer ->Technical Basic Settings ->Define Logical Port and Back-EndDestinations for ESOA.

Refer to note 1268336 for setting up synchronous services.

4. Customizing of document typeIn IMG navigate to the customizing of contract document types:IMG -->Materials Management -->Purchasing -->Contract -->Define DocumentTypesCreate the same document types which you use in SRM to create centralcontracts to be replicated to ERP. If e. g. you want to replicate SRMcontracts of type CCTR to ERP this type CCTR would have to be created inERP as well.Enter an internal number range in the column 'Number Range for SRM CentralContract' for this document type, to store the corresponding ERP contractin.

5. Customizing of conditions mapping

o The logic of condition mapping between SRM central contracts andERP replicated contracts is as follows:

- First the system checks the conditions mapping as defined inCustomizing.

- If no mapping condition has been defined in Customizing thesystem checks whether an ERP condition with the same ID exists.

- If no mapping condition has been defined in Customizing the SRMcondition won't be replicated.

o The conditions mapping between SRM central contract conditions andERP replicated contract conditions can be customized here:

IMG -->Integration with Other mySAP.com Components -->SupplierRelationship Managment -->Central Contract -->Assignment ofConditions

14.08.2013 Page 3 of 4

SAP Note 1268821 - SRM 7.0 / ERP 6.04: Config. of CentralContract Management

6. Usage of Central Contract field in ERP business processAfter activating the business function LOG_MM_P2PSE_1, the field 'CentralContract' to enter the SRM central contract ID is available on several UIsin purchasing and MRP.Only in case of ALV-Grid display (e.g. item overview in ME51N, ME21N,result list in source of supply tab of ME51N and ME52N) the field has to beincluded from the column set of the GRID layout.

7. Authorizations for users No specific authorization is needed to use an SRM central contract assource of supply in ERP; the usual roles and authorizations for sourcingactivities (transactions, purchasing organization, plant, purchasing group,etc.) have to be assigned to the user.

8. Upgrading from an earlier release of SRM / support packageof ERPIf you are upgrading from an earlier release of SRM / support package ofERP and you are already using SRM Globals Outline Agreements (GOAs) assource of supply in ERP you need to convert the replicated GOAs in ERP toreplicated Central Contracts. Please refer to the program documentation ofreport MMBSI_CONTRACT_MIGRATION. For converting the GOAs created the lowerreleases in SRM to Central Contract in SRM 7.0 system please use the report/SAPSRM/MIGRATE_GOA_TO_CC. These reports have to be executed saperately inboth the systems. The preferred sequence would be to run the migrationreport in SRM first to convert GOA to CC and then run the migration reportin ERP. Running the report in ERP presupposes that the system connectivityregardings SOA services between ERP and SRM has been set up completely.

9. Condition Groups in SRMFor Central contracts, the condition groups 01HD, 01CO and 0100 would berelavent for creating new contracts. For migrated contracts that existedaleady as GOA, the old condition groups 01CH, 01CP and 01CC would besupported but any fresh contract will use only the condition gruops 01HD,01CO and 0100.

Settings in PI=================For CCM scenario to work, PI set up is required for the followingasynchronous enterprise services.

(Namespace; Software Component Version; Interface:)

http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0;PurchasingContractSRMReplicationRequest_Out

http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchasingContractSRMReplicationRequest_In

http://sap.com/xi/APPL/Global2; SAP APPL 6.04;PurchasingContractSRMReplicationConfirmation_Out

http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0;PurchasingContractSRMReplicationConfirmation_In

http://sap.com/xi/APPL/Global2; SAP APPL 6.04;

14.08.2013 Page 4 of 4

SAP Note 1268821 - SRM 7.0 / ERP 6.04: Config. of CentralContract Management

PurchaseOrderERPContractReleaseNotification_Out

http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0;PurchaseOrderERPContractReleaseNotification_In

Settings in SAP Enterprise Portal=================Please refer to paragraph Settings in the Enterprise Portal in note1263876.

Notes to be implemented=================Notes 1262480, 1252865, 1263470, 1260829

Header Data

Release Status: Released for CustomerReleased on: 23.03.2009 12:50:07Master Language: EnglishPriority: Recommendations/additional infoCategory: CustomizingPrimary Component: SRM-EBP-CON Contract Management

Secondary Components:MM-PUR-OA Outline Purchase Agreements WithVendors

EP-PCT-PUR-BP BP for Buyer

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_APPL 604 604 604

SRM_SERVER 700 700 700

Related Notes

Number Short Text

1547977 FAQ: Central Contract Management (SOA based)

1276845 Release Info SRM7.0: Installation and Upgrade Information

1268336 Synchronous peer-to peer Services Configuration

1263876 SAP SRM: Configuration of Procure-to-Pay Scenario

1263470 CCM:Replication of Central Contracts with more than 10 items

1262480 Wrong value in check table constant

1260829 CCM: Changes to GOA service items overwritten in EHP4

1252865 Central Contracts: Search help for Central Contract dumps

1232945 BP for SRM 7.XX: Installing the Business Packages