MDG Architecture & Deployment

In the MDG hybrid approach, in what order do consolidation and central governance act on a record?

Which MDG capabilities are available only when MDG runs on SAP S/4HANA, not on the SAP ERP 6.0 add-on?

For MDG 9.2 not on S/4HANA, which software component carries the consolidation functionality versus central governance?

Why can't you activate the MDG business function for a domain (e.g. material or business partner) on its own?

On MDG 9.2 with SAP ERP, why can consolidation be installed in a standalone system while central governance cannot stand alone the same way?

What can SAP Business Client host that the SAP Fiori launchpad cannot?

A colleague calls Floorplan Manager 'the Fiori design for MDG.' Why is that wrong?

While a change request is still in its workflow, where does the entered master data physically reside?

What landscape condition pushes you toward a separate MDG hub rather than co-deploying MDG on an existing system?

SAP recommends co-deploying MDG only on S/4HANA, not on ERP 6.0. What is the reasoning?

Name a landscape condition that outright blocks co-deploying MDG on an operational ERP system.

What is the upgrade-lifecycle advantage of an MDG hub, and what cost do you pay for it?

What is the hidden testing risk of co-deploying MDG on your operational ERP/S/4HANA system?

In a hub deployment, how do you keep a master record findable by the same number in both the client system and the MDG hub?

Which deployment platforms does MDG (9.2 / on S/4HANA 1809) support, and which is notably excluded?

When running MDG on SAP ERP (not S/4HANA), why is the database choice a governance decision, not just a performance one?

Which IMG transaction do you use for governance configuration versus consolidation configuration in MDG?

In a hub landscape, which Customizing data belongs in the MDG hub as its system of record, versus in the operational system?

In MDG, which scenarios use a Web Dynpro UI and which use SAP Fiori?

A company wants to actually govern a piece of Customizing data inside MDG, not just copy it in. What is the modeling move?

You built the MDG hub as a system copy of the operational S/4HANA box. What step must precede ongoing Customizing synchronization?

Among the options for ongoing Customizing synchronization to an MDG hub, which does SAP recommend, and why over the alternatives?

In SAP Solution Manager, what is the division of labor between Customizing Scout and Customizing Distribution?

Why must you be careful running an initial Customizing Distribution against a target that already holds real configuration?

What does Cross Landscape Distribution (XLD) add over the classic Customizing Distribution tool, and when would you choose it?

Why can't SAP Solution Manager's Customizing Distribution synchronize everything an MDG hub needs to maintain master data?

Which ALE message types synchronize material class/characteristics versus G/L accounts and profit centers into the MDG hub?

Consolidation for analytics and consolidation for initial load use the same merge-and-match engine. What distinguishes the two use cases?