Hi Binoy,
I am an independent SAP MDG consultant doing implementation for my clients. I proposed the same thing "Copying using BC Sets". But my client declined. As I am not a complete BASIS person, so I was asking for their Basis team to do this job which they politely declined :-). Moreover, it was the best time for them to actually do the cleanups in the configs and have only specific values configured in MDG.
Good thing about implementing MDG as HUB is that it will not hold the Transnational Data & it will be a stand-alone system, which means all the config values are plain dumb text.
Like having Company Code configured is just a text and it will not have any type of intelligence associated (i.e go to OX02 and have 4 digits and description configured. that's it). Same goes for Sales & Purchase Org etc etc.
So for me it took very less time to configure manually what is required and only relevant for MDG-S, MDG-C & MDG-M.
I see you tagging me here, this is what I followed.
May be experts here can better guide you for the MDG S/4 HANA implementation.
Cheers,
Rohit
We have been trying some proof of concept trying to copy standard T table from ECC to S/4 Hana MDG HUB and we find warnings while transporting . There seems to be structural changes for standard config tables ..
Any other options that has been proven approach to copy config. that as been adopted for ECC to S/a Migration for MDG ? We are setting up MDG as a HUB on S/4 and our ECC is 6.0 .
Add comment