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

SAP Error Message - Details

• Message type: E = Error

• Message class: /SEHS/DG_DGA -

• Message number: 336

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

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

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

  The SAP error message /SEHS/DG_DGA336 indicates that a data record could not be saved because the associated change number is locked. This typically occurs in the context of SAP's Engineering Change Management (ECM) or similar modules where change numbers are used to manage modifications to data records.
  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 is a system or transaction error that has left the change number in a locked state.
  
  
  
  User Authorization: The user attempting to save the record may not have the necessary authorizations to modify the change number.
  
  
  Solution:
  
  
  Check Lock Status:
  
  Use transaction code SM12 to check for locks on the change number. You can search for the specific change number to see if it is locked by another user.
  If you find a lock that is no longer needed, you may need to contact the user who has the lock or, if appropriate, you can delete the lock yourself (ensure you have the necessary authorizations to do this).
  
  
  
  Change Number Status:
  
  Verify the status of the change number using transaction CC03 (Display Change Number). Ensure that the change number is in a status that allows modifications.
  If the change number is in a status that prevents changes, you may need to create a new change number or change the status of the existing one if you have the necessary permissions.
  
  
  
  User Authorization:
  
  Ensure that the user has the appropriate authorizations to modify the change number. This may involve checking roles and authorizations in transaction PFCG.
  
  
  
  Retry Saving:
  
  After resolving any locking issues or authorization problems, try saving the data record again.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: To check and manage locks.
  CC03: To display change number details.
  PFCG: To manage user roles and authorizations.
  
  
  
  Documentation: Refer to SAP Help documentation for Engineering Change Management for more details on how change numbers work and their statuses.
  
  
  Support: If the issue persists after checking locks and authorizations, consider reaching out to your SAP Basis or support team for further assistance.
  
  
  By following these steps, you should be able to resolve the error and successfully save the data record.