Message type: E = Error
Message class: UGX1 - Messages for XML Processing
Message number: 018
Message text: Type &1 of dimension &2 is not defined
The taxonomy uses a typed dimension. However, the type has no
definition. The taxonomy contains an error.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Validate the taxonomy.
Error message extract from SAP system. Copyright SAP SE.
UGX1018
- Type &1 of dimension &2 is not defined ?The SAP error message UGX1018, which states "Type &1 of dimension &2 is not defined," typically occurs in the context of SAP BW (Business Warehouse) or SAP HANA when there is an issue with the data model, particularly with dimensions in InfoObjects or data models.
Cause: Undefined Dimension Type: The error indicates that a specific type of dimension (e.g., characteristic, key figure) is referenced in your data model but has not been defined in the system. Incorrect Configuration: There may be a misconfiguration in the InfoObject or the data model where the dimension type is expected but not available. Transport Issues: If the data model or InfoObject was transported from one system to another, it’s possible that the transport did not include all necessary components. Version Mismatch: If there are different versions of the data model or InfoObjects in different environments (development, testing, production), this error can occur.
Solution: Check Dimension Definitions: Go to the SAP BW
Get instant SAP help. Sign up for our Free Essentials Plan.
UGX1017
Type &1 cannot be traced back to a basic type
What causes this issue? You can define new types in XSD files. The system analyzes the type definitions as to whether a key figure or characteristic ...
UGX1016
Definition of type &1 does not comply with XBRL specifications
What causes this issue? XBRL poses restrictions on how to define the types on which tuples, dimensions, and taxonomy elements are based.System Respon...
UGX1019
Type of tuple &1 does not adhere to XBRL specifications
What causes this issue? XBRL poses restrictions on how to define the types on which tuples are based.System Response The system issues an error mess...
UGX1020
Element &1 of tuple &2 is not defined
What causes this issue? The XML schema determines whether a tuple is defined as a <LS>sequence </>, <LS>choice</>, or <LS&...
Click on this link to search all SAP messages.