How To Fix EB360 - Change to the lock for process &1 and contract account &2 was not reset

SAP Error Message - Details

• Message type: E = Error

• Message class: EB - IS-U invoicing

• Message number: 360

• Message text: Change to the lock for process &1 and contract account &2 was not reset

What causes this issue?

A lock was changed for process &V1& and contract account &V2& during
invoicing
in event R582. Reason &V3&, period &V4&.
This change cannot be undone,
since the lock has been changed in the meantime or the original
period is found in the past.

System Response

The change to the lock is not undone.

How to fix this error?

Check the locks for process &V1& and contract account &V2& ,
and change these manually if required.

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 EB360 - Change to the lock for process &1 and contract account &2 was not reset ?

  The SAP error message EB360 indicates that there was an issue with changing the lock for a specific process and contract account. This error typically arises in the context of contract account management, particularly when there are concurrent processes trying to access or modify the same contract account.
  Cause:
  
  Concurrent Access: The most common cause of this error is that multiple users or processes are trying to access or modify the same contract account simultaneously. This can lead to a situation where the system cannot reset the lock for the process.
  System Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If a process is already locked and another process tries to change it, the system will throw this error.
  Long-running Transactions: If a transaction takes too long to complete, it may hold onto the lock longer than expected, causing other processes to fail when they attempt to access the same data.
  
  Solution:
  
  Check for Active Sessions: Use transaction codes like SM12 (to check for locks) and SM21 (to check system logs) to identify if there are any active sessions that are holding locks on the contract account.
  Wait and Retry: If the error is due to concurrent access, waiting for the other process to complete and then retrying the operation may resolve the issue.
  Review Long-running Processes: If there are long-running transactions, consider optimizing them to reduce the time they hold locks.
  Manual Lock Release: If necessary, you can manually release locks using transaction SM12, but this should be done with caution and typically only by an administrator.
  Check for Custom Code: If there are custom developments or enhancements that interact with contract accounts, review them to ensure they are not causing locking issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view and manage locks), SM21 (to view system logs), and ST22 (to check for dumps).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Performance Monitoring: Regularly monitor system performance and locking behavior to identify potential bottlenecks or issues before they lead to errors.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.