Message type: E = Error
Message class: /BOFU/COMMON -
Message number: 013
Message text: Fields LOW and HIGH have different types &1(&2), &3(&4)
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.
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.
The SAP error message
/BOFU/COMMON013 Fields LOW and HIGH have different types &1(&2), &3(&4)
typically occurs in the context of data selection or filtering, particularly when working with ranges in ABAP programs or queries. This error indicates that there is a mismatch in the data types of the fields being compared or used in a range.Cause:
The error arises when you are trying to define a range (for example, in a selection screen or a report) where the
LOW
andHIGH
values of a range are of different data types. For instance, ifLOW
is defined as a character type andHIGH
is defined as a numeric type, SAP will throw this error because it cannot compare or process these two different types together.Solution:
To resolve this error, you can take the following steps:
Check Data Types: Verify the data types of the fields involved in the range. Ensure that both
LOW
andHIGH
fields are of the same type. You can do this by checking the data dictionary (SE11) for the relevant fields.Adjust Data Types: If you find that the data types are indeed different, you will need to adjust them. This could involve:
- Changing the data type of one of the fields to match the other.
- If you are using a selection screen, ensure that the parameters or select-options are defined with compatible data types.
Review Code Logic: If the error occurs in custom ABAP code, review the logic where the range is being defined. Ensure that the variables used for
LOW
andHIGH
are declared with the same data type.Use Type Conversion: If it is necessary to keep the different types for some reason, consider using type conversion functions to convert one type to another before performing the comparison.
Testing: After making the necessary changes, test the program or report to ensure that the error no longer occurs.
Related Information:
By ensuring that the LOW
and HIGH
fields are of the same type, you should be able to resolve the error and proceed with your SAP operations.
/BOFU/COMMON012 Given Table Type does not have structured line type
Self-Explanatory Message Since SAP believes that this specific error message is ...
/BOFU/COMMON011 Field &1 is not of type &2(&3) on Range Table Type
Self-Explanatory Message Since SAP believes that this specific error message is ...
/BOFU/COMMON014 Range Line Type has &1 fields instead of 4 fields (SIGN/OPTION/LOW/HIGH)
Self-Explanatory Message Since SAP believes that this specific error message is ...
/BOFU/COMMON015 Field &1 is not a simple type
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.