Skip to Content
author's profile photo Former Member
Former Member

MDM-XI-ECC for Master data like Vendor and customer

If there are some changes like addition or deletion of some fields in customer or vendor, then it is not possible to use the standard pre-delivered content which SAP has provided.

So in that case, how can we handle that in XI?

For example DEBMDM or CREMDM?

The predefined content splits this into two idocs CREMAS & ADRMAS and serialises and then sends to ECC.

So when there is customization of Idocs, how can we handle it?

Any clues please?



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on May 23, 2008 at 12:12 AM

    For various reasons I would recommend not using the predefined content. Mainly for the exact scenario in which you describe. If you have to add custom fields, then you can't use the predelivered content, however you can copy the predelivered content and modify it. The MDM content for XI uses XSLT mappings, so if you are familiar with XLST then you can work with those, however I prefer to generate a graphical mapping, because it only takes a few seconds anyway. You simply have your source message be the CREMDM (or DEBMDM) format, and the target is CREMAS and ADRMAS. You simply select the top node of CREMDM and do a 1:1 mapping to CREMAS, then map the ADRC segment of CREMDM to the ADRMAS IDoc. If you use the graphical tool then you can modify your map easier if you need to add or remove fields. For example, if you want to do a IDoc reduction, then you can perform the IDoc reduction in ECC, and then swap that message type out with the one in your graphical map. Or if you want to add fields you can perform an IDoc extension in ECC, and then swap that message type out in XI. It's much easier to make these changes when you've built a graphical map.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      What you want to do is have one source, and two targets in your message mapping. The two targets will be ADRMAS and DEBMAS. You can populate the common fields easily, just the same as normal mapping, you just do it twice.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.