How To Fix EIT_IMPORT073 - Removed lock of Template &1(&2).

SAP Error Message - Details

• Message type: E = Error

• Message class: EIT_IMPORT - Extensibility Template: Import

• Message number: 073

• Message text: Removed lock of Template &1(&2).

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 EIT_IMPORT073 - Removed lock of Template &1(&2). ?

  The SAP error message EIT_IMPORT073 indicates that a lock on a template (identified by the template name and ID) has been removed. This typically occurs in the context of the SAP system's import process, particularly when dealing with transport requests or template management.
  Cause:
  
  Lock Removal: The lock on the template was removed, possibly due to a timeout or because another process or user has released the lock.
  Concurrent Access: Multiple users or processes may be trying to access or modify the same template simultaneously, leading to conflicts.
  System Configuration: There may be system settings or configurations that dictate how locks are managed and released.
  
  Solution:
  
  Check Lock Status: Use transaction code SM12 to check for existing locks on the template. If you find any locks that should not be there, you can manually delete them if you have the necessary authorizations.
  Retry the Operation: If the lock was removed due to a timeout, simply retrying the operation may resolve the issue.
  Review User Access: Ensure that users who need to access the template have the appropriate authorizations and that there are no conflicting processes.
  System Logs: Check the system logs (transaction code SM21) for any related messages that might provide more context on why the lock was removed.
  Consult Documentation: Review SAP documentation or notes related to template management and locking mechanisms for any specific guidance or known issues.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM21: To check system logs for errors and warnings.
  SE09/SE10: To manage transport requests.
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  User Authorizations: Ensure that users have the necessary roles and permissions to access and modify templates.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to your SAP Basis team or SAP support for further assistance.