Skip to Content

Does MDM really reflect ECC?

I've come to understand that MDM is intended as the master data repository for a variety of R/3 (ooops, I guess it's called ECC these days 😊 data types (or I suppose we can say business objects), such as vendors, customers, materials and so on. However, in trying to figure out why business partners related to a customer were not deleted in the related R/3 system after having been removed from the customer master in MDM, I got the reply from SAP that "we do not send deletions from MDM to R/3. The reason is that MDM simply does not know how the data is used in R/3 - meaning if it is already part in any processes (like billing, and so on) or not. If this is the case, a deletion would completely invalidate and falsify R/3 processes. From an MDM perspective, we cannot do this."

Does this not invalidate the principle of MDM? Or is MDM more like BW; just an accumulation or snapshot of the underlying business data (from various R/3 systems), with more of a one-way communication?

I'm slightly confused here... but a newbie in the MDM world... 😉

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on May 27, 2008 at 03:09 PM

    This is a good question you bring up, it's sort of interesting how it acts that way isn't it? The main reason is that MDM can simply delete records, where as in ECC you can't delete a record by which a transaction has been posted on. What you can do is "flag" the record for deletion. So one way to accomplish this goal is to have MDM send an IDoc with the flag for deletion field filled out so that it will trigger the record in ECC to be flagged for deletion. This further prevents transactions to posting on that record.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Trond Stroemme

      Hi Trond,

      Its a controversy but form my point of view as of now you are right because on R3 side we dont have any standard mechanism or say fields/attributes to indicate that this customer record not required anymore or say customer deleted his/her record.

      Yet one alternative is to use custom things, say any table/Idoc having indicator field for deletion or to deactivate the record on R3 side and once a customer do that R3 system should trigger the record to MDM to update the actual record, hence removing the confusion.

      And having the indicator set to 'customer data deleted' , the record on R3 side still can be used for reporting, accounting and CRM related tasks.

      But it may lead confusion when we dont have all the things custom.

      Correct me if i am wrong.


      Alok Sharma

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.