Cannot replicate identical products categories from two backend systems
We have implemented SRM 5.0 and two ECC6 backends.
We have also configured a list of material groups codes identically in the both backend systems manually e.g STAT- Stationery, COMP - Computing, SECT -Security. This way we can share catelogies in SRM for example and also to keep material group reporting consistent between the two backend clients through BW.
We repplicate material groups via CRM Middleware from the first backend client into SRM without any problems.
When we try to replicate the identical set of material groups from the second backend client, the material groups donot replicate across. No error messages are reported in any systems of CRM middleware q logs. If we ure a unique material group code, in the second backend system, this replicates automatically to SRM as expected.
When me view table comm_category, we notice that replicated material groups/product categories have a unque GUID that points to a logical backend system. So SRM should accomodate identical material group codes as long as they are replicated from a different backend system.
Can somebody confirm that we can or should be able to replicate identical material groups from two separate backend systems.
Sundeep Ravande replied
Create RFC destinations and test connections.
1.) Note: Deactivate CRM specific settings. In the backend system, go to table: CRMPRLS (Logical system data is in this table).
2.) Run the program BBP_PRODUCT_SETTINGS_MW in SRM. This will make the basic settings.
Report <SE38> : BBP_PRODUCT_SETTINGS_MW
Run this report to deactivate CRM specific settings, to ensure EBP data replication. Maintain Unit of Measures and currencies using the customizing object DNL_CUST_BASIS3.
<b>3.) SMOEAC: Maintain sites: Source site and destination site. Type: CRM, Site attributes: Specify the RFC destination.</b> <u>(Here you need to ensure you have defined your other backend system for replication)</u>
4.) Similarly for R/3
Go to SM30 in R/3 and using tables.
CRMCONSUM (Maintaining the consumer).
CRMPAROLTP (Setting the filtering for the materials so that you can download materials from SRM).
CRMRFCPAR (This is an important table used for setting initial and delta downloads).
5.) SMOFPARSFA (SRM table contains several parameters to drive the middleware)
One parameter value must be created and maintained in the EBP system.
Linkage of EBP middleware to the backend EBP consumer object maintains the following.
PARAMETER NAME- MCRM_CONSUMER
6.) <R3AS> in SRM to select the source and the target system that are maintained using SMOEA and to start the initial download
7.) <R3AC1> Set up the filters (Initially uncheck Inactive Object) then maintain the Table and filter options here.
8.)These are the standard customizing objects maintained in <R3AC3>
Each adapter object maintains different tables.
DNL_CUST_BASIS3 (units of measure, dimensions, and currencies)
DNL_CUST_PROD0 (product categories)
DNL_CUST_PROD1 (product categories)
DNL_CUST_SRVMAS (service categories)
9.) SMW01: Used to maintain BDOC objects. (used to monitor any errors during download)
Hope this helps !!
Pls reward points for usefull answers !!