How To Fix /SAPAPO/OO_TR085 - User &1 is editing quotas of selected locations in model &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/OO_TR -

• Message number: 085

• Message text: User &1 is editing quotas of selected locations in model &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 /SAPAPO/OO_TR085 - User &1 is editing quotas of selected locations in model &2 ?

  The SAP error message /SAPAPO/OO_TR085 indicates that a user is currently editing quotas for selected locations in a specific model. This message typically arises in the context of SAP Advanced Planning and Optimization (APO), particularly when multiple users are trying to access or modify the same data simultaneously.
  Cause:
  
  Concurrent Editing: The primary cause of this error is that another user (User &1) is already editing the quotas for the specified locations in the model (&2). SAP APO does not allow multiple users to edit the same data simultaneously to prevent data inconsistencies.
  Lock Mechanism: SAP uses a locking mechanism to ensure data integrity. When one user opens a quota for editing, it locks that data for other users until the first user completes their changes and saves or cancels the edit.
  
  Solution:
  
  Wait for Release: The simplest solution is to wait until the other user finishes editing the quotas. Once they save their changes or exit the editing session, you should be able to access the quotas without any issues.
  Contact the User: If you know who the user is, you can contact them to see if they can finish their work or release the lock.
  Check Lock Entries: If you have the necessary authorizations, you can check the lock entries in the system using transaction code SM12. This will allow you to see which user is holding the lock and potentially release it if necessary (though this should be done with caution and typically only by an administrator).
  Review User Permissions: Ensure that users have the appropriate permissions and understand the implications of editing quotas in a shared environment to minimize conflicts.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view and manage lock entries) and SM21 (to check system logs for any related issues).
  User Training: Consider providing training for users on how to manage quotas effectively and the importance of checking for locks before starting to edit.
  System Configuration: Review the system configuration to ensure that it is set up to handle concurrent user access appropriately, including any settings related to locking behavior.
  
  By following these steps, you should be able to resolve the error and continue working with the quotas in SAP APO.