Message type: E = Error
Message class: UGX2 - Messages for XBRL Reporting
Message number: 211
Message text: Tuple &1 no longer exists
Tuple &V1& is referenced in the report category. However, it is no
longer in taxonomy &V2& or in the taxonomy view that is defined by entry
schema &V3&.
The reference to tuple &V1& is neither displayed when maintaining the
report category nor considered when generating instance documents.
To delete the reference to the tuple automatically, save the report
category.
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.
UGX2211
- Tuple &1 no longer exists ?The SAP error message UGX2211, which states "Tuple &1 no longer exists," typically occurs in the context of SAP BW (Business Warehouse) or SAP HANA when dealing with data models, queries, or InfoProviders. This error indicates that a specific tuple (a combination of dimensions) that the system is trying to access or manipulate is no longer available in the database or data model. Causes: Data Model Changes: The tuple may have been deleted or modified due to changes in the underlying data model, such as the removal of a characteristic or dimension. Data Deletion: The data associated with the tuple may have been deleted from the InfoProvider or the underlying database. Inconsistent Data: There may be inconsistencies in the data due to failed data loads or issues during data extraction. Query Changes: If a query has been modified to include or exclude certain characteristics, it may lead to references to non-existent tuples. Solutions: Check Data Model: Review
Get instant SAP help. Sign up for our Free Essentials Plan.
UGX2210
Tuple element &1 no longer exists
What causes this issue? Element &V1& of tuple &V2& is referenced in the report category. However, it is no longer in taxonomy &V3...
UGX2209
Taxonomy element &1 no longer exists
What causes this issue? Taxonomy element &V1& is referenced in the report category. However, it is no longer in taxonomy &V2& or in t...
UGX2212
Taxonomy element &1: Field &2 is not restricted
What causes this issue? Due to the data type of taxonomy element, &V1& the system derives a textual representation from the assigned selectio...
UGX2213
Element &1 and field &2 have different data types
What causes this issue? Due to the data type of element &V1&, a textual representation is derived from the assigned selection conditions. ABA...
Click on this link to search all SAP messages.