How To Fix /GSINS/INSH_MSG071 - External transfer &1, &2, &3, &4 locked by another user

SAP Error Message - Details

• Message type: E = Error

• Message class: /GSINS/INSH_MSG -

• Message number: 071

• Message text: External transfer &1, &2, &3, &4 locked by another user

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_MSG071 - External transfer &1, &2, &3, &4 locked by another user ?

  The SAP error message /GSINS/INSH_MSG071 indicates that an external transfer is locked by another user. 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 is currently processing the same external transfer, which locks the record to prevent conflicting changes.
  Long-running Transactions: A transaction may be taking longer than expected, causing the lock to persist.
  System Configuration: Certain configurations in the SAP system may lead to more frequent locking scenarios, especially in high-transaction environments.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to complete their transaction. After a short period, try to access the external transfer again.
  Identify the Lock: Use transaction codes like SM12 (to view and manage locks) to identify which user or session is holding the lock. You can then communicate with that user to understand their progress.
  Release the Lock: If you have the necessary authorizations, you can manually release the lock from SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still processing the data.
  Optimize Processes: If this issue occurs frequently, consider reviewing and optimizing the processes that lead to locking. This may involve:
  
  Reducing the time taken for transactions.
  Implementing better user training to avoid simultaneous access.
  Adjusting system settings to handle locks more efficiently.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (lock entries), SM21 (system log), and ST22 (dump analysis) for troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or patches related to locking mechanisms in your version of SAP.
  User Training: Ensure that users are trained on how to handle locks and the importance of not accessing the same records simultaneously.
  
  If the problem persists or if you encounter additional issues, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.