How To Fix USMD1B020 - An open change adjustment exists in client &1 for data model &2

SAP Error Message - Details

• Message type: E = Error

• Message class: USMD1B - Meldungen: MDF Anschluss

• Message number: 020

• Message text: An open change adjustment exists in client &1 for data model &2

What causes this issue?

A preceding change in the data model required an adjustment of change
requests that were not yet finalized.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

This error occurred because <ZH>all</> of the following are true:
The data model was extended with attributes that are related to an
active area
The data model was activated
Open change requests relating to this data model existed in the
respective client
These open change requests have not yet been adjusted.
This situation can happen in the following scenarios:
The data model was extended and activated manually<(>,<)> and the open
change requests have not yet been adjusted.
One or more Switch BC Sets containing data model changes were activated.
If more than one of these BC Sets were activated during one process
(e.g. an activation of a business function)<(>,<)> this message will
appear as an error message in all activation logs starting from the
second BC Set involved.

System Response

In the manual activation scenario (scenario 1 above)<(>,<)> this message
is displayed after pressing the <LS>Activation</> pushbutton and the
data model is not activated.
In the Switch BC Set activation scenario, the inactive version of the
data model was completely updated with the changes of all respective BC
Sets. However the active version of the data model was only updated with
the changes of the first activated BC Set.

How to fix this error?

In order to adjust the open change requests, perform the following
steps:
1. Update SMT Mapping:
When new fields are added to a data model with a reuse active area, you
may first have to extend the mapping of the access class for the reuse
active area. You can use the <DS>
<DS:TRAN.SMT>Service Mapping Tool (SMT) to edit the mapping.</></>
2. Adjust BP Mappings:

If the data model BP or a custom data model that uses the same reuse
active area was enhanced, run the <DS>
<DS:TRAN.SMT>Service Mapping Tool (SMT) to adjust the mappings
BP_BP_CENTRL_2API and BP_BP_CENTRL_2STA.</></>

3. Adjust Open Change Requests:
Afterward, you need to adjust the change requests with regard to the
modified data model. This is done by using the program
USMD_ADJUST_STAGING. You can execute this program for a specific data
model by choosing the <ZK>Adjust Staging Area of Linked Change Requests
</> pushbutton in Customizing for Master Data Governance, Central
Governance under <ZK>General Settings</> -> <ZK>Data Modeling</> ->
<ZK>Edit Data Model</>. This ensures the program is executed in all
respective clients via batch jobs. If any issues occur, manually run the
program again in the respective clients.
4. Adapt changes from Switch BC Sets:
If multiple Switch BC Sets were activated, manually activate the data
model and repeat the steps 1 to 3.
The changes that are executed must also be executed in all target
systems linked to the transport of the data model change - <ZH>esp
ecially in live systems</>. Only then can you again create new change
requests in those target systems after the data model is changed. Before
those changes are executed, you also cannot make additional local
changes to the same data model.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message USMD1B020 - An open change adjustment exists in client &1 for data model &2 ?

  The SAP error message USMD1B020 indicates that there is an open change adjustment in the specified client for the specified data model. This typically occurs in the context of SAP Master Data Governance (MDG) when there are pending changes that need to be addressed before proceeding with further actions, such as activating or modifying the data model.
  Cause:
  The error is caused by the existence of an open change request or adjustment that has not been completed or released. This can happen if:
  
  A change request is still in process and has not been finalized.
  There are pending adjustments that need to be addressed before the system can allow further modifications to the data model.
  The user is trying to perform an action that is not permitted while there are open changes.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Open Change Requests:
  
  Navigate to the relevant transaction in SAP MDG (e.g., transaction MDG_CHANGE_REQUEST).
  Look for any open change requests related to the specified data model.
  
  
  
  Complete or Release Change Requests:
  
  If you find any open change requests, you will need to either complete them or release them, depending on your business process.
  Ensure that all necessary approvals are obtained if required.
  
  
  
  Review Change Adjustments:
  
  If there are adjustments that need to be made, address those as necessary.
  Make sure that all changes are properly documented and processed.
  
  
  
  Consult with Team Members:
  
  If you are unsure about the status of a change request or adjustment, consult with your team members or the person responsible for managing the data model.
  
  
  
  Check for Locks:
  
  Sometimes, the error can also be related to locks on the data model. Ensure that no other users are currently editing the same data model.
  
  
  
  System Logs:
  
  Check system logs for any additional information that might help diagnose the issue further.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  MDG_CHANGE_REQUEST: To manage change requests.
  MDG_MAINTAIN: To maintain master data.
  
  
  
  Documentation:
  
  Refer to SAP Help documentation for Master Data Governance for more detailed information on managing change requests and data models.
  
  
  
  Support:
  
  If the issue persists after following the above steps, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
  
  
  
  By following these steps, you should be able to resolve the error and proceed with your tasks in SAP MDG.