Quantcast
Channel: SCN : Discussion List - SAP Master Data Governance
Viewing all articles
Browse latest Browse all 2047

MDG-F Import of Master Data/File Upload and replication timing option in Edition

$
0
0

Hello everyone,

 

I was trying to use "MDG-F Import of Master Data" function to load each invididual cost center master records and then use "MDG-F File Upload" function to load cost center hierarchy, cost center group, and their relationship assigemnet files to complete the build of cost center hierarchy on MDG-F.  Since each process mentioned here has to with an Edition that specifies the repliation timing 1- manually started after release of edition, 2 - on final approval of change request, 3 - selected in each change request. Does the replication timing option matter in this case from hierarchy build perspectve? Which option I should go with? What about valid from date in Edition?

 

these question are asked because I got in the situtation described below. Note there are a number of events on timeline.

 

1) 10/01/2014 A full cost cneter hierarchy similar to OKEON is already in place on MDG-F using file upload/file import

2) 10/05/2014 several new cost center codes (A. B. C) are created from MDG-F. these new cost centers are assigned to cost center group, they are they are showing perfect on MDG-F

3) 10/10/2014  Add new cost centers (X, Y, Z), new cost center group and assign them to cost center groups. While I was using "Process Hierarchy for cost center group", I was getting an error message that says "cost center A, B, C are not in standard hierarchy".  Why are those cost centers that have been added to the hierarchy in early Edition not automatically rolled over into late Edition?

 

Should I release the Edition used in building the hierarchy to avoid this situation? If this is the way to go, have I use replication timing choice 1 - manually started after release of edition?

 

Thanks,

LUO


Viewing all articles
Browse latest Browse all 2047

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>