Central Contract not replicated to ECC

[Former Member]

Hello Experts,

We are in 7.02 and recently had a refresh of the SRM Server. Since then, I am facing an issue with replication of Central contract to ECC.

Following error found in RZ20. But in SM59, all the test for ECC, SRM and PI are fine.

Please suggest.

Best Regards,

Dinesh

[ivy_li]

Hi,

Did you use BADI BBP_DETERMINE_LOGSYS in SRM side? If so, please deactivate it to see if the error persists.

Meanwhile please also check if BADI BBP_CTR_BE_CREATE contains any coding in method CONTRACT_INTERFACE_FILL. If so, check if logical system is changed within the coding.

BR,
Ivy

[former_member190255]

Hello - Please check the below settings, it might help you.

To solve your issue you must follow some steps all are available in SAP Note 1268821 - SRM 7.0 / ERP 6.04: Config. of Central Contract Management

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

-->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

    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.

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.

Notes to be implemented

=================

Notes 1262480, 1252865, 1263470, 1260829

Thanks,

VM

[Former Member]

Hi ,

We also came across the similar situation and we found that, there was custom code determining  backend systems for some criteria, that was overriding our settings in bbp_backend_dest table.

So, please check with your development team if they have implemented a BAdI which is controlling the backend destination.

Srini J

[Former Member]

Please also check in your Org structure if System Alias, etc have been changed due to your refresh. Make sure all appropriate attributes are pointing to correct backend system.

Srini J

[Former Member]

Hi Dinesh

Please check the entries in BBP_BACKEND_DEST, and confirm QA  SRM is pointing to QA ECC

Regards

Ajit

[Former Member]

Thanks Ajith...Yes, all the entries for ECC and SRM found in BBP_BACKEND_DEST table and also QA SRM is pointing to QA ECC..

What else to check?

Best Regards

Dinesh

[Former Member]

Hi Dinesh,

Can you check the Authorisation is working fine between SRM and ECC in RFC.

Regards,

Suneel