How To Fix ECCEDI120 - Object &1 &2 is blocked

SAP Error Message - Details

• Message type: E = Error

• Message class: ECCEDI - IS-U Deregulation: IDoc Processing

• Message number: 120

• Message text: Object &1 &2 is blocked

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 ECCEDI120 - Object &1 &2 is blocked ?

  The SAP error message ECCEDI120 indicates that a specific object (identified by the parameters &1 and &2) is blocked. This typically occurs in the context of data processing or integration scenarios, such as when working with Electronic Data Interchange (EDI) or other data transfer processes.
  Cause:
  The error can be caused by several factors, including:
  
  
  Locking Mechanism: The object may be locked by another process or user. This is common in scenarios where multiple users or processes are trying to access or modify the same data simultaneously.
  
  
  Incomplete Processing: If a previous process that was supposed to release the lock did not complete successfully, it may leave the object in a blocked state.
  
  
  Configuration Issues: There may be configuration settings in the EDI or data processing setup that are causing the object to be blocked.
  
  
  Authorization Issues: The user or process attempting to access the object may not have the necessary permissions, leading to a block.
  
  
  Solution:
  To resolve the ECCEDI120 error, you can take the following steps:
  
  
  Check Lock Entries: Use transaction code SM12 to check for lock entries related to the object. You can identify the user or process that is holding the lock and take appropriate action, such as waiting for the process to complete or contacting the user.
  
  
  Release Locks: If you determine that a lock is no longer needed, you can manually delete the lock entry in SM12. Be cautious when doing this, as it may affect other users or processes.
  
  
  Review Process Logs: Check the logs of the processes that interact with the object to identify any errors or issues that may have caused the block.
  
  
  Check Configuration: Review the configuration settings related to the object in question. Ensure that all settings are correct and that there are no conflicts.
  
  
  User Authorizations: Verify that the user or process has the necessary authorizations to access the object. You can use transaction code SU53 to analyze authorization issues.
  
  
  Restart Processes: If the issue persists, consider restarting the relevant processes or jobs that interact with the object.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (Lock Entries), SM21 (System Log), SLG1 (Application Log), and SU53 (Authorization Check).
  SAP Notes: Check SAP Notes for any known issues or patches related to the ECCEDI120 error. SAP frequently updates its knowledge base with solutions for common errors.
  Documentation: Review SAP documentation related to EDI and data processing for best practices and troubleshooting tips.
  
  If the issue continues after following these steps, it may be beneficial to consult with your SAP Basis or technical team for further investigation.