How To Fix DGA336 - Data record &1, &2, &3 not saved (change number &4 is locked)

SAP Error Message - Details

• Message type: E = Error

• Message class: DGA - DG: Messages for Dangerous Goods Management (A)

• Message number: 336

• Message text: Data record &1, &2, &3 not saved (change number &4 is locked)

What causes this issue?

You attempted to send a data record from a source system to a target
system.
However, the change number for this data record is being used by
another user in the target system.

System Response

The system does not allow you to post the data record to the target
system.

How to fix this error?

Wait until the data record is no longer locked in the target system.
Start sending the data record again.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DGA336 - Data record &1, &2, &3 not saved (change number &4 is locked) ?

  The SAP error message DGA336 indicates that a data record could not be saved because the associated change number is locked. This typically occurs in scenarios where change management is implemented, and it prevents modifications to data records that are associated with a locked change number.
  Cause:
  
  
  Change Number Locking: The change number associated with the data record is currently locked. This can happen if:
  
  Another user is currently editing or has locked the change number.
  The change number is in a status that does not allow changes (e.g., released or completed).
  There are pending approvals or workflows associated with the change number.
  
  
  
  Authorization Issues: The user may not have the necessary authorizations to modify the data record associated with the locked change number.
  
  
  Solution:
  
  
  Check Change Number Status:
  
  Use transaction codes like CC03 (Display Change Number) to check the status of the change number. If it is locked, you may need to wait until the lock is released or contact the user who has it locked.
  
  
  
  Unlock the Change Number:
  
  If you have the necessary permissions, you can unlock the change number using transaction CC02 (Change Change Number) or by contacting the relevant team or user who has locked it.
  
  
  
  Review User Authorizations:
  
  Ensure that the user attempting to save the data record has the appropriate authorizations to make changes to the data associated with the change number.
  
  
  
  Consult with Change Management Team:
  
  If the change number is part of a larger change management process, consult with the change management team to understand the reason for the lock and the appropriate steps to take.
  
  
  
  Retry After Lock is Released:
  
  If the lock is temporary, you may need to wait and retry saving the data record after the lock is released.
  
  
  
  Related Information:
  
  Change Management in SAP: Understanding how change numbers work in SAP can help in managing data records effectively. Change numbers are often used in configuration management and project management within SAP.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CC01 (Create Change Number), CC02, and CC03 for managing change numbers.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message, as there may be specific fixes or recommendations provided by SAP.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to your SAP support team for further assistance.