Central Governance: Data Modeling

During an open change request, where does the record being edited live versus the version that other applications and replication consume?

How does a record first land in the staging area in a create scenario versus a change scenario?

What exactly is the step called activation in the MDG governance process?

What single data-model property determines whether an activated MDG record ends up in tables like MARA and MARC versus in MDG's own generated tables?

After activation, what happens to the data sitting in MDG's generated database tables, and how does it differ by mode?

Why are all standard MDG Financials objects delivered in flex mode rather than reuse mode?

Two governed entity types both have generated tables and can carry attributes, but only one can be the entry point of a change request. Which storage/usage type, and why the other cannot?

A check-table entity in MDG has no generated persistence and cannot be changed in MDG at all. Is it storage/usage type 2 or type 3, and what is the contrast?

You need to add an attribute to a check-table (storage/usage type 3) entity type. Why will MDG not allow it, and what do you do instead?

What are the data-type and length limits on an entity type's own data element, and which storage/usage type cannot have one at all?

An entity type is set to internal key assignment. What extra object must be configured, and what key does the user actually see during the change request?

A data model has a reuse active area set at model level, but one entity type must persist in MDG's own tables instead. How is that achieved?

Why can't you change or delete certain entity types and attributes from the Edit Data Model activity?

Leading and qualifying relationships both place the from-entity at a higher level than the to-entity. What single condition makes a relationship qualifying instead of leading?

What does a referencing relationship actually do to the from-entity type, versus a leading relationship?

A hierarchy entity type has two independent properties: version-dependent and synchronized. What does each one control?

For a node relationship in a hierarchy, when is a hierarchy attribute set from a data element versus from a reference?

In the business partner data model, what actually links the governed business partner to the S/4HANA/ERP customer and vendor records?

The business partner model is delivered in reuse mode, yet its hierarchy entity types persist in MDG's own tables. How is that possible?

Which storage/usage type is required before you can enable Attachments or Sets on an entity type?

Why does extending the financial (0G) data model not require SMT mapping, when extending the material or business partner model does?

You are adding a custom field to the material data model. What decides whether it is a reuse extension or a flex extension?

From which MDG releases is internal-order governance available in the 0G model, and what changed to the 0G model at release 9.1?

For the material and business partner data models, what happens to MDG-specific authorizations you configure with object USMD_MDAT?