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

/PLMI/PPEENG136 - Overview

• 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