Message type: E = Error
Message class: FDT_CORE2 - BRFplus core functions (in addition to msg class FDT_CORE)
Message number: 031
Message text: Default setting for NUMC comparison changed, manual steps are necessary
You have changed the application default setting for the comparison
style for element data objects bound to data elements of type NUMC. The
new setting is in effect for new data elements bound to NUMC fields as
well as for existing data elements that are newly bound to a NUMC field.
As opposed to that, the comparison style used for already existing data
elements bound to a NUMC field remains unchanged. This is because both
possible comparison styles (numeric as well as alphanumeric) are valid
options, and it is up to you to decide in each single case which
comparison style is required depending on the use case.
All newly created data objects bound to a NUMC field will consider the
new setting.
Depending on the new setting there are some steps to be done to migrate
your currently existing data objects to use the new default. This
affects only data objects with a DDIC binding to a NUMC field.
Numeric comparison was turned on
All data objects bound to a NUMC field have to be rebound to use numeric
comparison.
All functions referencing such objects must be regenerated. The system
automatically takes care of this when the data objects are rebound.
Numeric comparison was turned off
All data objects with a binding to a NUMC field have to be rebound to
use alphanumeric comparison
All functions referencing such objects must be regenerated. The system
automatically takes care of this when the data objects are rebound.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
FDT_CORE2031
- Default setting for NUMC comparison changed, manual steps are necessary ?The SAP error message FDT_CORE2031 indicates that there has been a change in the default settings for NUMC (numeric character) comparison in the SAP system. This typically occurs when there are inconsistencies or changes in the data types or formats being used in your application, particularly when dealing with fields that are expected to contain numeric values.
Cause: Data Type Mismatch: The error often arises when there is a mismatch between the expected data type (NUMC) and the actual data being processed. This can happen if the data being compared is not in the correct format or if there are changes in the underlying data model. Configuration Changes: Changes in the configuration of the system or updates to the SAP system can lead to this error, especially if the changes affect how NUMC fields are handled. Custom Development: If there are custom developments or enhancements in the system that involve NUMC fields, they may
Get instant SAP help. Sign up for our Free Essentials Plan.
FDT_CORE2030
Invalid value (&1) for NUMC numeric comparison setting specified
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_CORE2024
Invalid value specified for custom attribute '&1'
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_CORE2032
Invalid value (&1) for IS_NUMC setting specified
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_CORE2050
Error during code generation (&1): Wrong filename format
What causes this issue? The system has determined that for the output file for the generated code, a filename has been specified that does not match ...
Click on this link to search all SAP messages.