cancel
Showing results for 
Search instead for 
Did you mean: 

Distribution of Contract from SRM to ERP - Screen output without connection to user.

Former Member
0 Kudos

Hi All,

System: SRM 702 and ECC- 605 for SOA technlogy with the help of PI 7.31 .

My scenario is to pass central contract from SRM to ECC system through PI.

Central contract available as XML in SRM side and its need to replicate to ECC same as in SRM.

So, I have configured proxy to proxy scenario in PI by using standard software components SAP SRM Server 7.02 and SAP APPL 6.05.

While creating central contract in SRM, XML message is passing to ECC through PI. But its struggle in SMQ2 of ECC side with the error message 'screen output without connection to user'.

While debugging ECC side proxy, i found one pop up window asking for pricing condition type. If i choose condtion type manually then the central contract created at ECC side.

I believe the pop up that occurs during debugging is casing issue with SMQ2 for background processing.

Can some one help me how to suppress this popup.

Thank you.

Regards,

Murugan S

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member208244
Active Participant
0 Kudos

Hello Murugan,

Naveen was partially correct, you need to map the price conditions from SRM to ECC, but the way is not to map it using that BADI. You are using services for transfer Contracts and no IDOCs.

Note that step 9 introduces the newly way to map ECC conditions from SRM, you need to fulfill that customizing table to make it works correctly.

Also, do not forgive the Syncrhonous Peer-to-peer Services, that are used to complete pricing procedures during Contract consumption.

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

Former Member
0 Kudos

Hi,

you need to map the Condition type of SRM to that of the ECC condition type. You can use badi BBP_CTR_BE_CREATE for the same.

Regards,

Naveen

Former Member
0 Kudos

Hi Murugan,

Is there any other way to transfer Contracts from SRM 7 EHP2 to ECC?

It sounds bizarre that you have so many forms to transfer documents:

- PO by RFC/BAPI

- Invoice and goods receipt by IDOCs

- And now the contracts must be by XI/PI

And if the client doesn't have the integrator?

What a mess.

Regards!

Palmeiro

Former Member
0 Kudos

Hi Palmeiro,

If the client doesnt have XI/PI you can use the WSRM process to transfer Contracts from SRM to eCC. Please find the link below for more details.

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/06/13/transfer-of-central-contract-from...

Regards,

Naveen