How To Fix EI360 - Data blocked by user &

SAP Error Message - Details

• Message type: E = Error

• Message class: EI - Foreign Trade: Gen. Output

• Message number: 360

• Message text: Data blocked by user &

What causes this issue?

The data in the database is blocked by user &V1&.

System Response

The data cannot be changed until user &V1& is finished editing it.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EI360 - Data blocked by user & ?

  The SAP error message EI360, which states "Data blocked by user," typically indicates that a user is attempting to access or modify data that has been locked or blocked by another user or process. This can occur in various SAP modules, such as SAP ERP or SAP S/4HANA, and is often related to data integrity and concurrency control.
  Causes:
  
  User Locking: Another user has locked the data for editing, which prevents other users from making changes until the lock is released.
  Transaction in Progress: A transaction is currently being processed, and the system has locked the data to ensure consistency.
  Background Jobs: A background job may be running that is accessing the same data, causing it to be locked.
  System Configuration: Certain configurations or settings in the system may lead to data being locked under specific conditions.
  
  Solutions:
  
  Wait and Retry: If the data is locked by another user, you may need to wait until the other user completes their transaction and releases the lock.
  Check Lock Entries: Use transaction code SM12 to check for lock entries. You can see which user has locked the data and, if necessary, you can delete the lock (if you have the appropriate authorizations).
  Communicate with Users: If you identify the user who has locked the data, you can communicate with them to understand why the data is locked and when they expect to release it.
  Review Background Jobs: Check if any background jobs are running that might be locking the data. You can use transaction code SM37 to monitor background jobs.
  System Configuration Review: If this issue occurs frequently, it may be worth reviewing the system configuration and settings related to data locking and concurrency.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage lock entries.
  SM37: To monitor background jobs.
  SM21: To check system logs for any related errors or warnings.
  
  
  User Authorizations: Ensure that users have the necessary authorizations to access or modify the data in question.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search the SAP Support Portal for relevant notes.
  
  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.