cancel
Showing results for 
Search instead for 
Did you mean: 

Group ID, ID-Mapping, storage of data

Former Member
0 Kudos

Hi,

I've got a question concerning <b>where which data or data attributes are being stored in the (re-)distribution of cleansed master data</b>.

Please have a look at the following example:

In my understanding MDS extracts Master Data (only special identifying attributes) from the MDCs, puts it in the staging area of CI, normalizes data and identifies matching candidates - matches of identical data-record-sets get a Group-ID (a new field to the record), which is created newly by MDS, right?

<b>Now, which information is stored on the MDS and what goes back to the Client systems?</b>

In my understanding the cleansed/ merged data gets back to the MDCs (with Group ID?) or if you just follow the scenario "Consolidation", which aims at the knowledge about redundancies but not at redistributing cleansed data, the reference object is maintained on the MDS, containing a Mapping/ Group ID and probably information about the source systems.

Is that right?

Thanx for help.

Matthias Kasig

Accepted Solutions (0)

Answers (1)

Answers (1)

Mark63
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Matthias,

Loaded data enter the MDS staging, and from there feed CI. CI then matches identical data and stores this information as MDS object including key mapping information (example: "A" = MDC object "1" and MDC object "2". => It's not just a common group ID attached.

When it comes to data distribution to the Master Data Clients (Master Data Harmonization, Central Master Data Management scenarios) the MDS object is replicated to the relevant MDCs using the key mapping information.

Kind regards,

Markus

Former Member
0 Kudos

so the key mapping information is stored in a separate table on the MDS with (I assume) somehow following structure:

Table Mapping_Information:

mapping-id -- mds-object -- location(MDC)

-

-


A -- hammer150g --   R/3 0814

A -- 150g hammer -- CRM 0815

right?

another different question...

is the integrtation engine of the MDM-System needed for something? in the configuration of the int.engine on the mdm i entered: role of system = loc anwendungssystem and corresponding int.server = IX 30 Integrationserver

with the result, that i can see (on mdm under sproxy) the software-components on the XI Int.Server

and one more:

how to establish the connection between EP and MDM?

is it enough to act corresponding to the config-guide content-consolidation MDM 3.0, which states on different pages to install the mdm30-components on the different systems and EP-Plugin-Versions on clients...

is it correct, that i don't have to establish sm59-connections? didn't read anything about that.

thank you once more,

matthias

Mark63
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Matthias,

Your assumption regarding the storage of key mapping information is correct.

I have forwarded your questions on MDM installation and configuration, since I am not the specialist in these areas.

Kind regards, Markus

Former Member
0 Kudos

Hi Matthias,

Concerning the local Integration Engine of MDS:

It facilitates the message exchange between MDS and the Central Ingegration Engine that connects to the MDCs.

Concerning the configuration of EP:

If you want to connect your MDCs for navigation purpose (e.g. including SSO, central user management), configuration according the config. guide is sufficient.

Kind regards,

Alexander