Change Requests & Editions

When you set an entity type or attribute to not be governed in a data model's governance scope, what happens to that field in maintenance?

An ungoverned field sometimes still gets updated during a data import, and sometimes is ignored. What decides which?

After you change several fields from governed to ungoverned, why can changed values still overwrite data in the connected target systems?

While a change request is still in flight (not yet approved), why don't downstream transactions see the new master-data values?

A change request status can grant one of three "permitted processing" levels. What does each allow?

Given a change request's status number, how do you tell whether it is finished or still open?

A change request header shows a Target Systems tab in one system and not another for the same domain. Why?

You attach a compliance document to a change request. Where does that attachment live after the CR completes?

In MDG, what is the actual job of a "logical action" like create, change, or display?

Why does the same logical action "create" map to different business activities like CUP1, SUP1, and BPP1?

How do logical action, business activity, and change request type chain together to launch a process?

On a change request type, what makes its change requests edition-independent versus edition-dependent?

The Parallel checkbox on a change request type only makes sense for a certain kind of entity. Which, and why?

The Switch classification (lean classification) property on a change request type is greyed out for most objects. When is it available?

When does MDG automatically pick the change request type instead of asking the user to choose?

In a change request step you can reorder checks — but two of them won't move. Which, and to what fixed positions?

You set a change request step to "Issue Error Messages as Warnings" so requesters aren't blocked. Which errors still hard-stop them, and does the CR ever activate dirty?

For a change request step's Field Properties, what's the difference between "No Required Field Check" and "Not Relevant"?

Four change request actions are exempt from MDG's implicit check-before-complete rule. Which, and why does that exemption exist?

The same change request step could have several UIs assigned along its determination chain. Which assignment wins?

You want to use editions to schedule changes for a custom object. What must be true of that object?

When a master data object is changed under an edition, what determines its valid-to date?

What does an edition's edition type actually pin down, and what is delivered 0G_ALL?

For multiple-object processing, which logical action corresponds to mass change, data import, hierarchy, and multiprocessing?

Mass change and file upload both run on the MASS logical action, so what practically distinguishes when you'd use file upload?

Data import (Transaction DTIMPORT) by default writes straight to the active area. How do you force it through governance instead?

In hierarchy processing, what's the behavioral difference between Loose and Strict interlocking when a node is changed?

Where is it decided whether a change request can hold one record or many records?

MDG normally needs the entity key up front. What does the Keys checkbox on a change request step change about that?

What does the Validation checkbox on a change request step guarantee about the process?

Which checks does MDG run per change request step as its standard set?

Under what condition can an edition type be retired, and what stops working once it is?

The SAP customer-on-client scenario (business function MDG_CUST_ERPCLIENT_1) suddenly doesn't apply after a system move. When and why?

Which fields can never be removed from governance scope, regardless of how you configure a data model?