Message type: E = Error
Message class: RSODP - Operational Data Provider: Messages
Message number: 103
Message text: Field &1 ignored: Data type &2 not allowed for characteristic
Characteristics can be used in Analytics in the Group By and for
filtering. The Analytic Engine can only map fields to a characteristic
if the data type is none of the following: binary, a string/blob, a
figure like DEC or FLOAT.
Field &V1& is therefore ignored and is not part of the analytical model.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Usually fields which represent a figure should be mapped to a key
figure. Key figures need a defined default aggregation. You should
therefore add the CDS annotation "@Aggregation.default". Standard
default aggregations are #SUM, #MAX, or #MIN. If the field can't be
aggregated, for example because it is a price in an analytic dimension,
aggregation #NOP can be used. This means that the aggregate is equal to
the value of the record if the aggregate contains just one record. It is
the exceptional value "NOP" if the aggregate contains more than one
record.
If the field shouldn't be used in the analytic model or can't be used
because of an unsupported data type, it can be suppressed with the CDS
annotation "@Analytics.hidden. true".
Error message extract from SAP system. Copyright SAP SE.
RSODP103
- Field &1 ignored: Data type &2 not allowed for characteristic ?The SAP error message RSODP103 indicates that there is an issue with the data type of a characteristic in a data source or InfoObject. Specifically, it means that the system has encountered a characteristic (field) that has a data type that is not allowed for the operation being performed. This typically occurs in the context of data extraction, transformation, or loading processes, particularly in SAP BW (Business Warehouse) or SAP HANA environments.
Cause: Incompatible Data Type: The characteristic in question has a data type that is not compatible with the expected data type for the operation. For example, if a characteristic is defined as a numeric type but is being treated as a string, this error may occur. Incorrect Configuration: The configuration of the InfoObject or data source may be incorrect, leading to mismatches in expected data types. Data Source Issues: If the data source is not properly defined or if there are changes
Get instant SAP help. Sign up for our Free Essentials Plan.
RSODP102
Empty join conditions are not supported in ESH ODP on SAP HANA
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSODP101
Logical conjunction ANALYTICSFILTER not supported in ESH ODP on SAP HANA
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSODP104
Field &1 ignored: Data type &2 not allowed for measures
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSODP105
Characteristic &1 not allowed in value help
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.