- Send master data (Materials, customers, vendors, articles etc) from MDM to other systems, normally termed as business partners (BP) (This is called as harmonization).
- And a vice-versa (This is called consolidation) is also possible.
I am completely a naïve to MDM scenarios and searched many forums and kept calling many friends on how to achieve my scenarios. But then, what are my scenarios? I shall discuss them rather say, share my experiences on one of those scenarios where MDM sends customers to R/3. I am sure, there is no blog that is covering this kind of scenario and this is for the first time even am BLOGGING!!! Thanks a lot for the contributions from my friend Shiva Kumar Garugu & his friend Mr.Mallikarjun Rao, who helped me us lot with his inputs. Besides, I read many articles blogs & posts on SDN to achieve my scenario successfully and finally this inspired me to share my experiences.
Scenario: MDM shall place a File (DEBMDM06). This should be sent to ECC6.0 system.
Sender system: MDM 5.5 SP05
Receiver system: ECC 6.0 Requirement is to pick a file whose structure is equivalent to Idoc Type DEBMDM06. I have to create Idocs in R/3 using this file. Cool, it sounds very simple that you will need FILE & IDOC adapters at source and receiver sides respectively. But, catch you there!!! It’s not as simple as it sounds because you first have to understand the importance of stressing Idoc type DEBMDM06? DEBMDM06 is an Idoc type which in turn has two Idoc types with in it.
- DEBMAS & ADRMAS. You can see this ADRMAS as one of the segments “E1ADRMAS” in DEBMDM06.
- DEBMDM06 can hold multiple Idoc data records. Where as DEBMAS holds only one Idoc data at any point of time. Thus DEBMDM is mass capable and further more, it is MDM specific.
With these bumps, I had to stop dreaming about it being a normal simple File to Idoc scenario. I was even thinking that I may have to go for a BPM even as some splitting of ADRMAS & DEBMAS in DEBMDM06 is required to process!!! How to go about it was a million dollar question to me? But all that I realized is that two Idocs (ADRMAS & DEBMAS) have to be created in R/3.
Functionally point to be noted: ADRMAS has to be posted first and then DEBMAS.
The best part of this type of integration is, SAP has already delivered a pre-defined content which is available in marketplace. This will have all the data types, message types, message interfaces, mappings, interface mappings, communication channel templates and also the integration scenarios for all the master data types like material, customer, vendor, articles etc. You can ask your basis guys to import this content into XI and you will only need to re-use this content in your scenario. Yes, now its very simple scenario. Simpler than a File to Idoc scenario!!!
- Considering MDM pre-defined XI content is imported into XI
- All SLD settings are done for both sender and receiver.
- RFC Destination and other Configurations done in XI & ECC 6.0
Step 1: Have your own Namespace created under any SWCV
Step 2: Copy the IM “Debmdm06_600ToAdrmas02” & “Debmdm06_600ToDebmas06”from the pre-defined imported Content into your Namespace created in step 1.This has all the pre-defined data types and mappings required for our design.
Step 3: So, if you try to activate, you get an error. How to correct it? Copy the Imported archives “MDM55_DebmdmCremdm_ToCremasDebmas” From the pre-defined imported content in to the same working namespace. This imported archive will hold three XSL mapping programs. Now you activate again and you are done with the design part. I am not showing any screen shots as it is not so complex to understand and it is only a copy paste work.
Configuration Time. You can use the pre-defined integration scenarios provided by SAP. But to have a better understanding, I shall explain the configuration steps to be done one by one here.
Step 1: Create a scenario and have your BS assigned to it.
Step 2: Create a File CC. You can fill your own options in processing and advanced Tabs
Step 3: Create Receiver CC
Step 4: Create a Sender Agreement. Choose your sender service & interface as shown
Step 5: Create two receiver agreements for two IDOC types (ADRMAS & DEBMAS)
a) First create for ADRMAS. In both the agreements, receiver CC remains same.
b) Similarly Create for DEBMAS
Step 6: Create Interface determination
Note 1: It is important that you first create Interface determination for ADRMAS and then for DEBMAS.
Note 2: Also it is very important to maintain the check box below Quality of service. This is important because, you will have to post the address Idoc (ADRMAS) for a customer before DEBMAS is posted as already specified earlier.
Note 3: Choose the respective Interface mappings which we re-used during design time
Step 7: Create Receiver determination
Remember that we had two receivers physically though the receiver system is Only one. Hence two agreements and thus shall have two determinations as well.
See the two agreements shown below. This will come automatically come up once you create two receiver agreements
Now you activate and you are done with the configuration part.
Testing Time & Obervations in R/3:
- Place a file in specified folder and you will find two Idocs triggered to R/3.
- You can view them through WE02.
- To have your DEBMAS successfully posted, first ADRMAS should be successfully posted.
- There are lot many fields which are inter dependent. So please take help of a functional resource to validate your input file data. Otherwise you will end up with lots of errors while testing.
Observations in XI:Go to SXMB_MONI and watch your message. You will find 3 messages for each poll as shown below:First one for ADRMAS, Second for DEBMAS and third for Message Branching.
Alas!! That’s how I succeeded in doing this scenario. You can apply the same process for all other Idoc types like CREMDM etc which are MDM specific in data harmonization scenarios.
For any more doubts or errors or trouble shoot you face, refer to SNote: 1052964
I am yet to do a scenario for data consolidation. I.e. R/3 à MDM.If some one has done this, I appreciate if you can share the procedure. Am sure, a similar process is required. We are still doing R&D on it. But we are unable to get the data extract from R/3. Hope this is helpful.
I once again thank my friends who helped me complete this scenario successfully!!!