cancel
Showing results for 
Search instead for 
Did you mean: 

MDM scenario query

Former Member
0 Kudos

Hi All,

I wanted to understand how a MDM repository designed for the following scenario:

I have 4 remote systems, A,B,C and D.

For example ,lets take a customer Master data.

I have 30 fields for the custmer,out of which the field "payment term " is different for each remote system.For eg,payment term 15 in system A,means as follows:

Remote System Value

A 15

B B1

C C1

D D1

And there are lots of payment terms which are dynamic.

We can do it by having a lookup table called PaymentTerms with a field "PaymentTerm" for the payment term and managing four keys on each record(say for above example,an record entry for 15 with four keys as:

A 15

B B1

C C1

D D1

So when I mark the field as a display field, it will appear as 15 for all records .which have payment term as either 15,B1,C1 or D1 as data cn be fed from any of the four system.

That will be confusing for the MDM data administrator as for a record coming from system B,should be B1 and not 15.

Please let me know if my scenario is unclear.

Edited by: Premjit Mishra on Feb 9, 2011 11:45 AM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Premjit,

Your scenario is very clear, also your repository structure is exactly how it should be.

I think MDM data administrator should be clear with remote key concept for avoiding confusion.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Premjit Mishra

For me it's clear

Create next LUT"Payment term":

System - related (LUT) - name of system( should be related lut with list of our system names) - Display field (1) - order in DM

Term - (text or real or measure) - name of payment term or, maybe, value - Display field (2)

XXX- - dome another dfields if you want

Create in your main table filed like "Payment term"

type = LUT (Flat)

lut name =Payment term

Value selection= Mini-search

Regards

Kanstantsin Chernichenka