cancel
Showing results for 
Search instead for 
Did you mean: 

Master Data Client Strategy

Former Member
0 Kudos

Hi -

We are on R/3 4.6C version. Is master data (such as material) client dependent or client independent?

Thanks,

Kalven

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

If I understand the question right, I don't think Kalven is asking about how master data is done at different customers.

He is coming from a traditional SAP Stand point. My view is that Material Master will be different in different clients of the SAP system i.e., it is client dependent. Its just the ABAP code that will be client independent.

You should be seeing different data in each of the clients that you have. But again, it again depends how the system is confugured.

Regards,

Ravi

Former Member
0 Kudos

Hi Ravi,

Even I feel that the question is about R/3master data. If that is the case, then probably the question is posted in a wrong forum (????).

Regards,

Rajani Kumar

Former Member
0 Kudos

Ravi - Thanks, you answered my question.

Former Member
0 Kudos

Not being sure I understand your question I'll comment on different clients' points of view of the same data in MDM.

In MDM5.5 there is a repository which in general doesn't care who those clients are that request and/or update it (content manager, API, import manager or syndicator). You may think about it as a RDBMS knows nothing about clients connecting to it. I'm not considering different permission levels and security issues here.

MDM behaves almost the same but it has a great feature I don't find an analogy in the RDBMS world - key mapping. The notion of the key mapping is about assigning a unique distinct key for every record per client system (or agency in SP1). Client systems describe depersonalized user profile for import manager and syndication. So you don't use client systems to connect through the client or the API but you do use it for importing and syndication. Beside the ability to assign its own record key for every client system the syndicator traces who and when did last time syndication and based on this data calculates records eligible for "delta" syndication.

Hope this helps:-)