Master Data Management

(0) Share

Report

Posted on by Community Member

Good afternoon,

I'm hoping someone can point me in the right direction. I'm looking to see if anyone has a simple way to describe the attributes of the primary Master Data elements (entities); example: Customer, Vendor, Product... etc.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

André Arnaud de Cal... 301,053 Super User 2025 Season 2 on at

Like (0)

Report

Hi Wayne,

Can you explain your question? What are you exactly looking for?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Andre,

I have a few answers I think:

1. I don't have MDS installed yet so I'm not sure I can get to the answer I'm looking for yet.

2. Also, I don't think there is a single answer for my question to be honest. I'm looking for what others are doing as it relates to organization responsibility towards Master Data. Example: For Products... What attributes is the Technical Services department responsible for? What attributes is the Finance and Accounting department responsible for.

3. Basically, I think this is something that is completely dependent on the individual company to define.

If you have any specific guidance or direction that would be great.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,053 Super User 2025 Season 2 on at

Like (0)

Report

Hi Wayne,

This is getting interesting now.

MDS is used to synchronize e.g. master data between environments (or companies) or other software solutions.

You are right that currently you could get a hundred of different answers. That is because you did not describe your requirements in detail.

The definition Master Data Management can be a quality process within one single or source system. A second interpretation might be synchronization of data and detect duplicates.

The interpretation, implementation and requirements are indeed different per organization, but the two interpretations of process or synchronization are the same.

If you are talking about different responsibilities for different attribute of e.g. the products this is about managing the process. I do have experience at a customer where they indeed had several people involved to complete all details of the products. For this particular issue I found an add-on solution as standard AX does not cater for this requirement. Multiple people can have access to the product, but a workflow to guide them when input is required is missing.

I would love to continue this discussion. Please share your thoughts and directions where you are looking for some particular answers.

Was this reply helpful? Yes No
Weaveriski 23,620 Moderator on at

Like (0)

Report

Point 3 is correct - the attributes are dependent on the individual company to define. Also the implementation of MDM changes this - from a system where there is no common approach with local ownership it may even have differed by company, but having a central repository where data is entered and controlled may remove rights at the local level. I am afraid when you get into the MDM sphere the first step is to look at the data that needs to be controlled by the hub or locally and then "who" is responsible for it "where" is then supported by security.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

You can define attributes as per your requirements. If you are looking for an example : we achieved MDS with AX 2012 R3 by simply using DIXF MDM & MS SQL MDS. Entity and attributes were set as per requirements. In our case customer wanted to manage customer master data of multiple AX instances along with credit limits checks so that they can consolidate and check credit limits of some shared customers.

There is a very informative course on MDM available on DLP.

Was this reply helpful? Yes No