How To Fix /PLMI/ESD_BO021 - Constraint numbers of constraint &1 and constraint &2 are redundant.

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/ESD_BO -

• Message number: 021

• Message text: Constraint numbers of constraint &1 and constraint &2 are redundant.

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/ESD_BO021 - Constraint numbers of constraint &1 and constraint &2 are redundant. ?

  The SAP error message /PLMI/ESD_BO021 indicates that there are redundant constraint numbers in the context of a constraint-based planning scenario, typically within the SAP Advanced Planning and Optimization (APO) module or similar environments. This error arises when two constraints are defined in such a way that they do not provide additional value or differentiation in the planning process.
  Cause:
  The error is caused by the following scenarios:
  
  Redundant Constraints: Two or more constraints are defined that essentially enforce the same limitation or requirement on the planning process. This can happen if constraints are copied or if similar constraints are created without proper differentiation.
  Incorrect Configuration: The constraints may have been incorrectly configured, leading to overlaps in their definitions.
  Data Integrity Issues: There may be issues with the data integrity in the planning model, leading to the system recognizing constraints as redundant.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review Constraints: Check the definitions of the constraints mentioned in the error message (constraint &1 and constraint &2). Look for similarities in their conditions, limits, or parameters.
  
  
  Remove Redundancies: If you identify that the constraints are indeed redundant, you can remove or modify one of them to ensure that each constraint serves a unique purpose.
  
  
  Adjust Configuration: If the constraints are part of a larger configuration, ensure that the overall setup is correct and that constraints are not overlapping unnecessarily.
  
  
  Test Changes: After making adjustments, test the planning process again to ensure that the error is resolved and that the planning results are as expected.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on defining constraints in your version of SAP.
  
  
  Seek Expert Help: If you are unable to resolve the issue, consider reaching out to your SAP support team or a consultant with expertise in SAP APO or the specific module you are working with.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional context.
  Transaction Codes: Familiarize yourself with transaction codes related to constraint management in SAP, such as /SAPAPO/SDP94 for planning book maintenance.
  Training and Documentation: Consider training resources or documentation on constraint-based planning to better understand how to define and manage constraints effectively.
  
  By following these steps, you should be able to identify and resolve the redundancy issue causing the error message /PLMI/ESD_BO021.