Skip to Content

Usage of standard or MDM customer IDoc

Hello

I'm presently working to exchange customer information (both inbound/outbound IDoc) with an external non-SAP MDM system.

Which IDoc should we prefer ?

- DEBMAS & ADRMAS (to record emails too).

- the MDM IDoc ?

-> Does the integration and the sending of MDM IDoc require further customizing (other than the distribution model) ?

-> Can this transaction be used in "standalone mode" ?

I have other issues :

- How do I send back the DEBMAS or MDM message as soon as the inbound message has been integrated ?

it seems the change pointers modification doesn't not trigger on creation !?

- How could I prevent customers from being sent according to KNA1-SORTL field ?

i tried to add a new filter field but didn't succeed the whole procedure.

i also thought about BADI IDOC_CREATION_CHECK

what' are the possibilities ?

Thanks for any clue ;-)

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Dec 22, 2013 at 06:28 PM

    Let's answser to my question.

    - I couldn't find a solution to integrate the MDM Debitor IDoc, it seems it only can be generated !

    - As regard the integration of DEBMAS & ADRMAS, i'm searching how to handle best the "range number" since it appears we'll deal with two mode (external range on start, then internal ) !!!!!

    - I didn't find a way to trigger master data IDoc at creation or trigger it only once when i desire it.

    - Other question was "How could I prevent customers from being sent according to KNA1-SORTL field" ? the BADI IDOC_CREATION_CHECK works but that's not the best way, i couldn't make the BADI BDCP_BEFORE_WORK work !!

    i'll update if i have some news.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi

      Thanks Dwaraka for checking my problem. Here's an update.

      First Question "I didn't find a way to trigger master data IDoc at creation or trigger it only once when i desire it" :


      I want to trigger the sending of the master data IDoc only at creation.

      I used BD52 for the concerned IDoc and left only the KEY field.



      Second Question "How could I prevent customers from being sent according to KNA1-SORTL field ?"

      As you said, I had already tried this but I failed.

      And as you mentioned, i'm not sure I could filter on a pattern or a non-null value.


      It seems the implementation of BADI BDCP_BEFORE_WORK would work !? I need to check this.



      You told me you didn't cope with master data exchange with a non-SAP system ;


      The topic has been made twice as complicated by using internal range number.

      It implies the MDM must send us back our own number !


      Consequently, we're meeting difficulties with the DEBMAS standard integration (only one user-exit does exist and require a specific IDoc), email address is not managed as you all know ...




      Have a nice day

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.