How To Fix /SAPAPO/OO_TR_CLASS021 - LOW and HIGH fields have different type

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/OO_TR_CLASS -

• Message number: 021

• Message text: LOW and HIGH fields have different type

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_TR_CLASS021 - LOW and HIGH fields have different type ?

  The SAP error message /SAPAPO/OO_TR_CLASS021 LOW and HIGH fields have different type typically occurs in the context of SAP Advanced Planning and Optimization (APO) when there is a mismatch in data types between the "LOW" and "HIGH" fields in a selection range or interval. This can happen in various scenarios, such as when defining characteristic values, setting up planning books, or working with key figures.
  Cause:
  
  Data Type Mismatch: The most common cause of this error is that the "LOW" and "HIGH" fields are expected to be of the same data type (e.g., both should be numeric, character, date, etc.), but they are not. For example, if "LOW" is defined as a numeric field and "HIGH" is defined as a character field, this error will occur.
  Configuration Issues: Incorrect configuration in the planning book or data view settings can lead to this error.
  Custom Code: If there is any custom ABAP code or user exit that manipulates these fields, it may inadvertently cause a type mismatch.
  
  Solution:
  
  Check Data Types: Verify the data types of the "LOW" and "HIGH" fields in the relevant configuration settings. Ensure that both fields are defined with the same data type.
  Adjust Configuration: If you find a mismatch, adjust the configuration in the planning book or data view to ensure that both fields are of the same type.
  Review Custom Code: If there is any custom code involved, review it to ensure that it correctly handles the data types of the "LOW" and "HIGH" fields.
  Testing: After making changes, test the configuration to ensure that the error no longer occurs.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SAPAPO/MC62 (for planning book configuration) or /SAPAPO/MC73 (for data view configuration) to check and modify the settings.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance.
  Documentation: Refer to SAP documentation on APO configuration and planning books for more detailed information on how to set up and troubleshoot these settings.
  
  If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.