Kimball Forum
Would you like to react to this message? Create an account in a few clicks or log in to continue.

Handling customers merged via MDM

2 posters

Go down

Handling customers merged via MDM Empty Handling customers merged via MDM

Post  contactkpatel Wed May 13, 2015 9:53 am


I would really appreciate if you can shed some light on how we could handle these situations:

Situation #1:
Two similar customers exist in the customer dimension "ABC" & "ABC inc.". Both of these customers have sales entries in the sales fact. The MDM system identifies these two customers as duplicates and decides to merge the two customers into one - "ABC inc".  What updates need to happen in the datawarehouse?
        1. Inactivate "ABC" in the customer dimension.
        2. For the entries in the sales fact that correspond to "ABC", update the customer dimension key to point to "ABC inc"

Is there an alternative design approach to handle this more gracefully? Perhaps, avoiding updates to the sales fact?

Situation #2:
Similar to above situation, the sales territory (geographic assignment of a customer to a territory) for a given customer "ABC Inc" can change from territory 101 to 102. How do we handle that?

Thanks in advance.


Posts : 1
Join date : 2015-05-13

Back to top Go down

Handling customers merged via MDM Empty Re: Handling customers merged via MDM

Post  ngalemmo Wed May 13, 2015 4:22 pm

One thing to understand about MDM matching is it is not always correct. So, you need to take an approach that would allow for corrections.

To that end, never merge or rekey dimension entries in the DW, otherwise you will not be able to deal with corrections.

Store the MDM identification of the customer as an alternate key in the dimension table. Customer attributes coming from the MDM system would be updated against the dimension using the alternate key. If multiple rows apply to the same MDM id, all will have attributes set to the same value. It is these attribute values that will consolidate different customers into a 'merged' customer.

Same process with references and hierarchies, simply apply the update to all members with the same alternate key.

You do not remove dimension rows or alter fact table foreign keys.

Posts : 3000
Join date : 2009-05-15
Location : Los Angeles

Back to top Go down

Back to top

- Similar topics

Permissions in this forum:
You cannot reply to topics in this forum