How To Fix CMS_AST103 - User &1 is currently working on the asset

SAP Error Message - Details

• Message type: E = Error

• Message class: CMS_AST - Message Class for Asset

• Message number: 103

• Message text: User &1 is currently working on the asset

What causes this issue?

Asset with the specified lock parameter is locked for editing by another
user.

System Response

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

How to fix this error?

Contact the other user and decide who should be editing the asset.

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 CMS_AST103 - User &1 is currently working on the asset ?

  The SAP error message CMS_AST103 indicates that a specific user is currently working on an asset, which prevents other users from making changes to that asset simultaneously. This is a common issue in systems where concurrent access to data is restricted to maintain data integrity.
  Cause:
  
  Locking Mechanism: SAP uses a locking mechanism to prevent multiple users from editing the same asset at the same time. When a user opens an asset for editing, the system locks it for that user.
  Session Timeout: If a user has left an asset open and their session has not timed out, the asset remains locked.
  Unfinished Transactions: If a user is in the middle of a transaction involving the asset and has not completed it, the asset will remain locked.
  
  Solution:
  
  Wait for Release: The simplest solution is to wait until the user currently working on the asset completes their task and releases the lock.
  Contact the User: If possible, contact the user who is currently working on the asset to see if they can finish their work or release the lock.
  Check for Active Sessions: Use transaction codes like SM12 (to view and manage locks) to check if the asset is locked and by whom. If the user is no longer active, you may need to unlock the asset.
  Unlock the Asset: If you have the necessary permissions, you can manually unlock the asset in SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still working on it.
  Review User Sessions: If the issue persists, review user sessions and ensure that users are logging out properly after their work is done.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view locks), SM21 (to check system logs), and SU01 (to manage user accounts).
  User Training: Ensure that users are trained on how to properly log out of sessions and manage their work to avoid leaving assets locked unnecessarily.
  System Configuration: Review system settings related to session timeouts and locking mechanisms to ensure they align with your organization's needs.
  
  If the problem continues to occur frequently, it may be worth investigating the workflow processes or user training to minimize the chances of assets being locked for extended periods.