How To Fix IM661 - External number & locked by other user

SAP Error Message - Details

• Message type: E = Error

• Message class: IM - Maintenance notifications

• Message number: 661

• Message text: External number & locked by other 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 IM661 - External number & locked by other user ?

  The SAP error message IM661, which states "External number & locked by other user," typically occurs when a user attempts to access or modify an external number range that is currently locked by another user. This can happen in various scenarios, such as when creating or changing documents that require a unique number from an external number range.
  Cause:
  
  Concurrent Access: Another user is currently using the external number range, which prevents other users from accessing it simultaneously.
  Number Range Lock: The number range may be locked due to a transaction that is still in progress or has not been properly completed.
  System Configuration: The configuration of the number range may not allow multiple users to access it at the same time.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to complete their transaction and then try again.
  Identify the Lock: If you have the necessary authorizations, you can check which user is currently holding the lock. This can be done using transaction code SM12 (Display and Delete Locks). Look for the relevant lock entry and see which user is holding it.
  Contact the User: If you identify the user who is holding the lock, you can contact them to see if they can complete their transaction or release the lock.
  Release the Lock: If the lock is no longer needed (for example, if the user has logged out unexpectedly), an administrator can manually delete the lock entry in transaction SM12.
  Check Configuration: If this issue occurs frequently, it may be worth reviewing the configuration of the number range to ensure it is set up correctly for concurrent access.
  
  Related Information:
  
  Transaction Codes: 
  
  SM12: To view and manage lock entries.
  SNRO: To manage number ranges.
  
  
  User Roles: Ensure that users have the appropriate roles and permissions to access the number ranges they need.
  SAP Notes: Check SAP Notes for any known issues or patches related to number range management and locking mechanisms.
  
  If the problem persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.