Skip to Content
author's profile photo Former Member
0
Former Member

Group ID, ID-Mapping, storage of data

Posted on Jan 26, 2005 at 09:14 AM 19 Views

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Markus Ganser
    Markus Ganser
    Posted on Feb 11, 2005 at 09:58 AM
    0

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Markus Ganser
      Feb 11, 2005 at 01:59 PM

      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

    Comment on This Answer

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.