How does MDG-F gets the reference data?

[Former Member]

Hello All,

This is regarding MDG-F.

We are deploying it as Hub mode but I want to understand how the reference data is loaded.

E.g: On Create Cost Center screen, we can select Controlling area from F4.

When I debugged it it was coming from TKA02 Table, should it not be coming from staging etc..? If it is coming from underlying ECC, how do we take care of the reference data?

Is it possible to get this reference data somewhere from staging?

It is a strange question but the idea behind this is that it should be independent of the underlying ECC environment.

Please suggest.

Thanks

[bpawanchand]

Hi

It is a strange question but the idea behind this is that it should be independent of the underlying ECC environment.

MDG is tightly integrated with the Net Weaver Application server. Logically speaking, MDG understands different master data objects and how they should be governed without deviating from the core business logic of ERP (ECC) Business Applications. To clarify your point , precisely we do this as a cut over activity called as "Customization & Synchronization". In other words,

1. First synchronize ERP customization with MDG HUB.
2. Secondly, the Data Element which is used to define the technical attributes of an Attribute within an entity in the Data Model actually refers the underlying Value table or Search Help. This is the default behavior or MDG Attributes.
3. Finally, The result is what you asked.

Yes its possible to overwrite the Default list of possible values. Define your own search help and assign it to the Attribute.

Is it possible to get this reference data somewhere from staging?

I guess its possible, however, I would not recommend to do this.

Thanks, Pavan

[Former Member]

Thanks Pavan!

I understand the integration part and other points as mentioned by you makes sense.

But, lets say we have a look at GL Account creation.

For example, In entity ACCOUNT we have COA (Charts of Acc.) and ACCGRPACC (Acc. Group). COA directly refers to ECC data element with a check table while ACCGRPACC is assigned an USMD* field, which also refers to ECC table to build search results using OVS.

Q1: If we are anyway refereeing to ERP system for fetching the reference data, then how does MDG Hub system becomes stand alone?

Q2: If I have 10 legacy systems which are from different countries following different business standards, there reference data varies. How to I consolidate the reference data under one EP system (Hub)?

Please let me know your thoughts on this.

PS: This whole idea is to prepare a HUB system and make it independent.

Thanks,

Dinesh