Master data upload

[Former Member]

Dear Experts,

when there is a green filed implementation(a new sap implementation) for any manufacturing & suppling industry.

once you desing the repositories for material, customer and vendor.

what is the frequency of data upload for all these repositories?

As per my knowledge,

once we design the repository , it will be blank witout any data in it!!!

so we do data transfer of mat, cust and vendor data!!!!

how often will we add records to these repositories?

If its daily or weekly or monthly, why do we do so?

what are the business requirements which force them to do so?

on the other hand in production envirnment,

if we have done some changes in QA env and we want to update the same in PROD.

If we do a transport to PROD then the data in prod for that repository will be updated!!

By avoiding this backlock how can we update the changes in production??

And moreover will we get any such situation to update the data in PROD?

If so what could be the Situations for business to tell us to update??

Please read my questions line by line and if you are aware of answers please answer in detail.

Kind Regards

John

[Former Member · Accepted solution]

HI John

how often will we add records to these repositories?

If its daily or weekly or monthly, why do we do so?

what are the business requirements which force them to do so?

Data load in MDM repository depends on the scenarios implemented and business needs.

1. Assuming in your project MDM is used for Central Master data management. WE will need to do an initial FULL LOAD for the master data objects(material, Customer, vendor etc) and going forward all delta should be created first in MDM and then distributed to downstream systems.

2. If MDM is used only for consolidation scenario even after doing a FULL data load initially we need to do DELTA loads in MDM. The frequency depends purely on business needs at what fequency MDM needs to be synched with source systems. Mostly this is kept daily. Materials created in source systems for previous day will be loaded in MDM.

In any case you need to do a FULL load of data initially as part of Cutover before going live.

If we do a transport to PROD then the data in prod for that repository will be updated!!

By avoiding this backlock how can we update the changes in production??

And moreover will we get any such situation to update the data in PROD?

If so what could be the Situations for business to tell us to update??

For any delta data model schema change first we transport the schema to PROD and data for additional fields/tables introduced needs to be loaded separately. This can be done again before the go live as part of Cutover during the freeze time. Also we can prepare specific import maps for updating only the newly cretaed field/tables in MDM.

A typical scenario when this may happen is during rollouts to different geographies/locations Business may identify need for adding few new fields in MDM data model.

Hope I am able to reply.

Thanks

Ravi

[Former Member · Accepted solution]

Hello ravi,

When you said materials will be uplaoded on daily basis. then what about the frequencies of customer and vendor data?

And y r those freq?

kind regards

john

[Former Member · Accepted solution]

Hi John

I quoted Material as an example. The same will be true for Customer, Vendor or any Master data repository implemented in MDM program.

The frequency for the delta load is purely a business decision, on what intervals they want to synch data between MDM and source systems. For all logical reasons this is done on Daily basis in most of the implementations I have seen.

thanks

Ravi

[Former Member · Accepted solution]

Dear Ravi,

Regarding your statement

'

For any delta data model schema change first we transport the schema to PROD and data for additional fields/tables introduced needs to be loaded separately. This can be done again before the go live as part of Cutover during the freeze time. Also we can prepare specific import maps for updating only the newly cretaed field/tables in MDM.

A typical scenario when this may happen is during rollouts to different geographies/locations Business may identify need for adding few new fields in MDM data model.

'

I am quite clear that the Actual business data will only be available in PROD.

Which means that we just create a map with some old/dummy data in DEV and QA. Based on the success we implement that map in prod which deals with real data.

Now, When i uploaded data in Prod, i found that i have done something wrong in the map which led me to change the uploaded 'wrong data ' in Prod.

1)For this requirement i need to first change the map in qa and update in PROD?

2) Regarding the 'wrong data' in Prod, How can i correct them? should i need to change it manually in DM?

Can you please take some time in answering my questions!!!

Kind Regards

John

[Former Member · Accepted solution]

Hi John,

1)For this requirement i need to first change the map in qa and update in PROD?

Yes, your understanding is correct. On a safer side, you can take Archive of Production as back up and can unarchive this .a2a file on QA server. After this you can change your Import map on QA server and then can transport this map to PROD.

2) Regarding the 'wrong data' in Prod, How can i correct them? should i need to change it manually in DM?

Yes, you can do correct data manually using Data Manager but it would be lil bit laborious task if you have to correct data for many records. I would suggest that you should reimport correct data file using Import Manager since your matching field would be same during import so select import Action as Update All Mapped fields which will update all the mapped fields for previously wrong data and in this manner you will have correct data after reimport.

Regards,

Mandeep Saini

[Former Member]

Hi John,

In addition to Ravi, when there is a green filed implementation(a new sap implementation) for any manufacturing & suppling industry. Please refer the detailed document on Implementing a "Green Field" MDM where you need to read

Realizing the Need of a New Master Data Object, Conceptualization of a New Entity, Implementing a Sustainable Model

Data Collection, Data Consolidation into MDM etc.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50df64a9-a102-2d10-60b6-c9263dd27...

The article explains the nuances & challenges of implementing a "green field" MDM project from a functional & business perspective for a new master data object in an organization.

Regards,

Mandeep Saini