why we are not using "Message Control" for Master data ?

[Former Member]

Hi friends,

We are using Message control as output determination for Transactional data, <b>what is the main reason for not using the msg control for Master data.</b>Please explain with details...

I am very thankful to them...

Thanks and Regards.

<i><b>Naveen Kumar. Chamala</b></i>

[Former Member]

Hi Naveen,

Listing down those I know -

1. Master data is expected to be changed/created less frequestly.

2. Transactional data is expected to be chnaged/created more frequestly.

3. Transactions to create/change/display master data do no have message control integration, since you are not supposed to print/fax/mail master data to your partners.

4. Distribution of master data in generally supposed to happen within Enterprise boundry and typically you will have one central server maintaining master data which will be distributed to multiple downstream operation system (Some thing where MDM fits). So ideally when distributing master data using ALE you will be sending it to multiple systems.

5. Distributing transactional data PO/SO etc is same as sending fax/print which fits with the requirement of message control.

Hope this helps,

Regards,

Sanjeev

[christian_wohlfahrt]

Hi Naveen!

Documents are mostly containing info about FROM (creator) and TO (receiver) - so necessary data for print-out, e-mail... is pretty easy to get -> general (dynamic) message output can be implemented.

Master data is there - but to whom it's relevant? Should I send a creditor change to FI department - or all debitors - or some logistic purchasing department... The relevance of master data is never well defined: there are most times specific views, which deal only with a small part of your ERP customer, others are valid for nearly everyone.

So change analysis and data distribution has to be much more sophisticated to be useful -> only change pointers are available and follow-on functions are seldom delivered by SAP.

Regards,

Christian