Middleware Configuration and Monitoring for Master Data Transfer from SRM to ECC Applies to: SRM 5.0, SRM 7.0 For more information, visit the Supplier Relationship Management homepage. Summary Master data transfer from ECC to SRM takes place using Middleware which sends the data in the form of BDocs from ECC to SRM. In order for the communication and data transfer from (ECC to SRM) happen efficiently Middleware configurations need to be completed in ECC as well as SRM Author: Virender Singh, CPIM CSCP Company: Intelligroup Inc. Created on: 24 Aug 2010 Author Bio Virender Singh is a SAP SRM 7.0 Certified Professional consultant with more than 9 years of SAP Consulting Experience working with Leading IT Organization serving global clients. He has extensive experience of a number of implementations, upgrades, rollouts and run/maintain lifecycles of SAP Solutions running on SAP SRM, ECC, SNC, SAP Solution Manager. As a professional member of APICS and APICS Certified CPIM CSCP associate he has adequate knowledge and experience of modern day Supply Chain and Supplier Relationship processes. Currently in Intelligroup Inc., he is involved in providing innovative solutions to Global clients on SAP SRM and SCM. 2010 SAP AG 1
Table of Contents Configuration in R/3... 3 R/3 Table Updates... 3 CRMCONSUM and CRMSUBTAB... 3 CRMRFCPAR... 4 CRMPAROLTP... 4 TBE11 and TBE31... 5 Configurations in SRM... 5 Site Definitions in SRM using Transaction SMOEAC... 5 SMOFPARSFA... 6 Master Data Transfer Monitoring... 7 R3AM1 Monitor Objects in SRM... 7 SMQ1- - Outbound Queue in ECC... 7 SMQ2 Inbound Queue in SRM... 9 SMW01 Display BDOC messages... 10 Disclaimer and Liability Notice... 12 2010 SAP AG 2
Configuration in R/3 R/3 Table Updates CRMCONSUM and CRMSUBTAB For an SRM system, you set the middleware parameters in the OLTP system. If a "CRM" consumer entry for a CRM system has already been entered in the table CRMCONSUM in the OLTP system, the system ignores an additional consumer entry ("SRM", for example). The additional required settings are described in this note. If you correctly implement these settings, another consumer ("SRM", for example) can exist in addition to the "CRM" consumer. You can then determine the RFC destination entry in the table CRMRFCPAR for the "SRM" consumer, instead of for the "CRM" consumer. Make the following entries for your new consumer in the table CRMCONSUM in the R/3 system: o CONSUMER = SRM (for example) o AKTIV = X o TEXT = SRM Consumer (for example) o Q_PREFIX = R3A Copy the following entries into the table CRMSUBTAB in the OLTP system: o CONSUMER = CRM, OBJCLASS = MATERIAL o CONSUMER = CRM, OBJCLASS = CUSTOMIZING o CONSUMER = CRM, OBJCLASS = SERVICE_MASTER When you copy an entry, only change the CONSUMER entry that refers to the consumer name that you created ("SRM", for example in table CRMCONSUM). 2010 SAP AG 3
CRMRFCPAR Maintain the following entries in CRMRFCPAR table for user SRM. Make sure that the Send XML and InQueue Flag is configured as follows for all the entries. CRMPAROLTP Maintain following values in CRMPAROLTP: 2010 SAP AG 4
TBE11 and TBE31 Configurations in SRM Site Definitions in SRM using Transaction SMOEAC The sending and receiving systems are defined here for master data as sites. The site for receiving system is preconfigured and delivered as CRM. Therefore only the sending system need to be configured. 2010 SAP AG 5
SMOFPARSFA Make the following entry in SRM table SMOFPARSFA 2010 SAP AG 6
Master Data Transfer Monitoring R3AM1 Monitor Objects in SRM R3AM1 is the transaction used for monitoring the master data replication from R/3 to SRM. This replication includes the new object s replication as well as Delta Replication depending on filter settings. SMQ1- - Outbound Queue in ECC If for any reason, there is no status found for data transfer in monitor load objects in SRM, then check the outbound queue in ECC using transaction SMQ1. Check the queues which are sending data to SRM system 2010 SAP AG 7
Check the Items failed and stuck in the respective queue.. 2010 SAP AG 8
SMQ2 Inbound Queue in SRM 2010 SAP AG 9
On displaying the queue details, you will see the first qrfc in failed status and all other follow on items waiting for this item to be cleared. BDoc Monitorng can be done using SMW01 explained in next steps. SLG1 logs will also show the details of the error occurred here shown in the queue. Try to get into the details of this failed item in the queue. Reprocess it if possible. This LUW can also be processed in Debug mode in order to find out the problem with this record. If it is Ok to proceed without this item, just delete this item in the queue and the system will resume processing the items from next item. SMW01 Display BDOC messages This transaction can be used to check the details of the BDOCs which are shown as failed in the previous step. Follow the steps shown in the below screens to look into the details of failed BDocs 2010 SAP AG 10
2010 SAP AG 11
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2010 SAP AG 12