How To Fix LM128 - Selected limit &1 must be released by a different user

SAP Error Message - Details

• Message type: E = Error

• Message class: LM - Treasury: Limit Management

• Message number: 128

• Message text: Selected limit &1 must be released by a different 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 LM128 - Selected limit &1 must be released by a different user ?

  The SAP error message LM128, which states "Selected limit &1 must be released by a different user," typically occurs in the context of the SAP Logistics module, particularly when dealing with release strategies for purchase requisitions, purchase orders, or other documents that require approval.
  Cause:
  This error message indicates that the document you are trying to release (e.g., a purchase requisition or purchase order) is currently locked for release by another user. In SAP, certain documents can have release strategies that require approval from multiple users. If a document is set up in such a way that it requires a release from a specific user or group of users, and you attempt to release it while it is still pending approval from the designated user, you will encounter this error.
  Solution:
  To resolve the LM128 error, you can take the following steps:
  
  
  Check Document Status: Verify the status of the document you are trying to release. You can do this by checking the release status in the relevant transaction (e.g., ME53N for purchase requisitions or ME23N for purchase orders).
  
  
  Identify the Releasing User: Determine which user is currently responsible for releasing the document. This information can usually be found in the document's release strategy details.
  
  
  Contact the Releasing User: If you have access to the user who is responsible for the release, you can ask them to release the document. This is often the quickest way to resolve the issue.
  
  
  Check Release Strategy Configuration: If you are an SAP administrator or have access to configuration settings, review the release strategy settings to ensure they are set up correctly. You may need to adjust the configuration if there are issues with the release process.
  
  
  Wait for Release: If the document is in the process of being released by another user, you may need to wait until that user completes the release before you can proceed.
  
  
  Use Transaction Codes: Use transaction codes like ME28 (Release Purchase Orders) or ME54N (Release Purchase Requisitions) to manage the release process effectively.
  
  
  Related Information:
  
  Release Strategy: Understand how release strategies work in SAP, including the roles and responsibilities of users involved in the approval process.
  User Roles: Ensure that users have the appropriate roles and authorizations to release documents as per the defined release strategy.
  SAP Notes: Check for any relevant SAP Notes or documentation that may provide additional insights or solutions related to this error message.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further troubleshooting.