Вы находитесь на странице: 1из 4

SAP Note No.

Number Version Processor Processing Status Implement. Status Language Short Text 1268821 3


Page 1


New Cannot be implemented EN SRM 7.0 / ERP 6.04: Config. of Central Contract Management SRM-EBP-CON Purchase Contract


________________________________________________________________________ Long Text Symptom

You want to configure the newly introduced integrated Procure-to-Pay Scenario Contract Management.


Other terms
CCM, central contract, global outline agreement, GOA

Reason and Prerequisites

1. You installed all required Business Package as mentioned in note 1232945. 2. You need SAP ERP 6.0 EHP4 and SAP SRM 7.0 installed in your landscape.

The Procure-to-Pay Scenario Central Contract Management has been introduced newly with SAP Business Suite 7 and is designed as an integrated scenario between SAP SRM 7.0 and SAP ERP 6.04. It enables to use the SRM central contract as a source of supply in ERP. In what follows the technical steps to get the process up and running are described. Settings in SRM 7.0 =================

1.Configure Backend Systems

In 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 ->SRM Server ->Technical Basic Settings ->Define System Landscape This configuration should be done for all the ERP systems which are connected 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 should have following roles: /SAPSRM/ST_PURCHASER and /SAPSRM/EMPLOYEE. Settings in ERP 6.04 =================

1. Activate Business Function

In the ERP Systems you have to activate the EhP4 business function "Purchasing - SAP SRM Integration" (LOG_MM_P2PSE_1).

2. Register SRM System

In the connected ERP systems you have to register the SRM system: in IMG choose

SAP Note No. 1268821


Page 2

-->Materials Management -->Purchasing -->Portal -->Set Up Landscape Then select SRM System Connected and save your input. You must make this setting so that links are created in the ERP applications used in the scenario.

3. Set Up Synchronous Service

The following synchronous service is used to get current pricing information from SRM during ERP pricing (e. g. if you create a purchase order): PurchaseOrderSRMPricingSimulateQueryResponse_In For this service, SRM is the provider system and ERP is the consumer system. Following synchronous service is used to get the archival status of the replicated contracts of ERP during archiving of Central Contract: PurchasingContractSRMArchivingCheckQueryResponse_In For this service, ERP is the provider system and SRM is the consumer system. If multiple ERP 6.04 systems are connected to the SRM system, configure the archiving service for different destinations using the following IMG activity in SRM: SAP Implementation Guide - SAP Supplier Relationship Management ->SRM Server ->Technical Basic Settings ->Define Logical Port and Back-End Destinations for ESOA. Refer to note 1268336 for setting up synchronous services.

4. Customizing of document type

In IMG navigate to the customizing of contract document types: IMG -->Materials Management -->Purchasing -->Contract -->Define Document Types Create the same document types which you use in SRM to create central contracts to be replicated to ERP. If e. g. you want to replicate SRM contracts of type CCTR to ERP this type CCTR would have to be created in ERP as well. Enter an internal number range in the column 'Number Range for SRM Central Contract' for this document type, to store the corresponding ERP contract in.

5. Customizing of conditions mapping

o The logic of condition mapping between SRM central contracts and ERP replicated contracts is as follows: First the system checks the conditions mapping as defined in Customizing. If no mapping condition has been defined in Customizing the system checks whether an ERP condition with the same ID exists. If no mapping condition has been defined in Customizing the SRM condition won't be replicated.

The conditions mapping between SRM central contract conditions and ERP replicated contract conditions can be customized here: IMG -->Integration with Other mySAP.com Components -->Supplier Relationship Managment -->Central Contract -->Assignment of Conditions

6. Usage of Central Contract field in ERP business process

After activating the business function LOG_MM_P2PSE_1, the field 'Central Contract' to enter the SRM central contract ID is available on several UIs in purchasing and MRP.

SAP Note No. 1268821


Page 3

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 be included from the column set of the GRID layout.

7. Authorizations for users

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

8. Upgrading from an earlier release of SRM / support package of ERP

If you are upgrading from an earlier release of SRM / support package of ERP and you are already using SRM Globals Outline Agreements (GOAs) as source of supply in ERP you need to convert the replicated GOAs in ERP to replicated Central Contracts. Please refer to the program documentation of report MMBSI_CONTRACT_MIGRATION. For converting the GOAs created the lower releases 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 in both the systems. The preferred sequence would be to run the migration report in SRM first to convert GOA to CC and then run the migration report in ERP. Running the report in ERP presupposes that the system connectivity regardings SOA services between ERP and SRM has been set up completely.

9. Condition Groups in SRM

For Central contracts, the condition groups 01HD, 01CO and 0100 would be relavent for creating new contracts. For migrated contracts that existed aleady as GOA, the old condition groups 01CH, 01CP and 01CC would be supported 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 following asynchronous 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; 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 note 1263876.

SAP Note No. 1268821

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


Page 4


________________________________________________________________________ Valid Releases

SAP Application 604 700

________________________________________________________________________ Links to Support Packages

Software Component Release Package Name

________________________________________________________________________ ________________________________________________________________________