SAP Master Data Governance · Change Requests & Editions

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

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in 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?

Start learning today

Free to start — download the app or use it in your browser.