How To Fix /PLMI/PPEENG136 - &1 &2 still used in variants

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/PPEENG -

• Message number: 136

• Message text: &1 &2 still used in variants

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 /PLMI/PPEENG136 - &1 &2 still used in variants ?

  The SAP error message /PLMI/PPEENG136 typically indicates that a certain variant is still being used in the system, which prevents it from being deleted or modified. This error is often encountered in the context of SAP's Production Planning and Execution (PP/PE) module, particularly when dealing with planning variants.
  Cause:
  The error message /PLMI/PPEENG136 is triggered when you attempt to delete or modify a variant that is still in use. This could happen for several reasons:
  
  Active Usage: The variant is currently being referenced in a planning run or is linked to a specific process.
  Dependencies: Other objects or processes may depend on the variant, making it necessary for the variant to remain intact.
  User Authorizations: Sometimes, the user may not have the necessary authorizations to view or modify the variant, leading to confusion about its status.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Usage: 
  
  Use transaction codes like SE38 or SE80 to check where the variant is being used. You can look for references in reports, jobs, or other processes.
  You can also use transaction PPS0 to check the variants and their usage.
  
  
  
  Remove Dependencies:
  
  If the variant is being used in a job or a process, you may need to stop or modify that job/process to remove the dependency on the variant.
  Ensure that no active planning runs are using the variant.
  
  
  
  Delete or Modify:
  
  Once you have confirmed that the variant is no longer in use, you can attempt to delete or modify it again.
  If you need to keep the variant but want to make changes, consider creating a copy of the variant and modifying the copy instead.
  
  
  
  Check Authorizations:
  
  Ensure that you have the necessary authorizations to delete or modify the variant. If not, contact your SAP administrator to gain the required permissions.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific error message for any additional context or updates that may be relevant.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PPS0 (for planning variants), SE38 (for executing programs), and SE80 (for object navigator).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Support: If the issue persists, consider reaching out to SAP support for further assistance, providing them with the error message details and any steps you have already taken.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.