How To Fix /GSINS/INSH_MSG072 - External transfers &1, &2, &3 locked by other users

SAP Error Message - Details

• Message type: E = Error

• Message class: /GSINS/INSH_MSG -

• Message number: 072

• Message text: External transfers &1, &2, &3 locked by other users

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 /GSINS/INSH_MSG072 - External transfers &1, &2, &3 locked by other users ?

  The SAP error message /GSINS/INSH_MSG072 indicates that an external transfer is locked by other users. This typically occurs in scenarios where multiple users are trying to access or modify the same data simultaneously, leading to a lock situation to maintain data integrity.
  Cause:
  
  Concurrent Access: Another user or process is currently accessing the same external transfer data, which prevents you from making changes.
  Long-running Transactions: A transaction that takes a long time to complete may hold the lock longer than expected.
  System Configuration: Certain configurations in the SAP system may lead to more frequent locking situations, especially in high-transaction environments.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for a few moments and then try to access the data again. Locks are usually temporary.
  Identify the Lock: Use transaction code SM12 to check for active locks. You can see which user or process is holding the lock and decide if you need to contact them.
  Release the Lock: If you have the necessary authorizations, you can manually release the lock from SM12. However, be cautious with this approach as it may lead to data inconsistencies if the other user is still working on the data.
  Check for Long-running Processes: If you notice that locks are persisting, investigate if there are any long-running processes that need to be optimized or terminated.
  Communicate with Users: If you are in a collaborative environment, communicate with other users to coordinate access to the data.
  
  Related Information:
  
  Lock Management: Understanding how SAP handles locks can help in troubleshooting. SAP uses a locking mechanism to prevent data inconsistencies.
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view locks), SM21 (to check system logs), and ST22 (to check dumps) for further investigation.
  Performance Tuning: If locking issues are frequent, consider reviewing system performance and tuning database queries or processes that may be causing delays.
  
  If the problem persists or if you are unsure about taking any actions, it may be best to consult with your SAP Basis team or system administrator for further assistance.