Skip to Content

Deploying MDG during Transformation

As part of a enterprise transformation, we are deploying MDG 9. I have done this several times but not when transitioning from ECC to s/4 HANA.

There are pros and cons to having a separate MDG (on s/4) hub server or just using the embedded MDG on the Production instance. As we have a private cloud solution, is there "best practice" for deploying MDG (landscape, transport and use) when moving many legacy ECC systems to S/4?


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • May 14 at 10:49 AM

    Hi William,

    MDG ensures that its master data can be replicated to any kind of target system. This also works across system release levels (e.g. you can send data from a MDG on S/4 into a common ECC). W.r.t. SAP owned systems, most of the configuration steps needed are delivered either by SAP MDG, or the stakeholders of the integration scenario (e.g. SAP C4C). Considering this aspect, the reply to your question is more or less - from data perspective, it doesn't matter if you go for a MDG Hub or a co-deployed system.

    I think you should consider the administrative and technical aspects. Using MDG as a hub surely means additional costs since you need yet another system. On the other hand, a hub also means that you can easily upgrade the system to leverage new functionality, even w/o having the need to re-test your whole business (which is usually required if you go for co-deployments). The reason for re-testing your business is simple: many parts of the MDG functionality is meanwhile integrated into S/4 core (especially the consolidation and mass processing). If you go for a SP upgrade, you will also get changes to your core business.

    The question whether to go for MDG using a ECC or a S/4 as system foundation is a no-brainer. S/4 is currently SAP's future, don't install MDG on ECC anymore.

    Kind regards


    Add comment
    10|10000 characters needed characters exceeded