Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: UGX2 - Messages for XBRL Reporting
Message number: 021
Message text: InfoObject &1 does not exist in data basis &2
There was a check to see if InfoObjects were removed that existed in the
queries when the data basis was saved last. If an InfoObject was removed
from a query, this can have the following consequences:
The characteristic was used in a report category in Customizing. The
system determines the removal the next time the report category is
saved, and removes the characteristic from the report category in
Customizing. Customizing of the report category is then <ZH>incomplete.
</>
The InfoObject was used in a dimension in Customizing. Then this
Customizing <ZH>can no longer be used</>.
The InfoObject (characteristics only, not key figures) was used in
Customizing of a value selection. Customizing of the value selection is
then <ZH>incomplete.</>
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If it is not clear whether or not the characteristic is allowed to be
removed, then proceed as follows:
Add the characteristic to the query again.
Start the where-used list in Customizing of the data basis. It shows you
the possible uses of the InfoObject.
Check all of the possible uses and remove the InfoObject from
Customizing.
Then you can remove the InfoObject from the query.
Generate the XBRL data basis again.
Error message extract from SAP system. Copyright SAP SE.
UGX2021
- InfoObject &1 does not exist in data basis &2 ?The SAP error message UGX2021 indicates that a specific InfoObject (denoted as &1) does not exist in the specified data basis (denoted as &2). This error typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when trying to access or manipulate data related to InfoObjects that are not available in the specified data source.
Cause:
- Non-Existent InfoObject: The InfoObject you are trying to access has not been created or has been deleted from the data basis.
- Incorrect Data Basis: The data basis specified may not be the correct one where the InfoObject is defined.
- Transport Issues: If the InfoObject was recently transported from one system to another, it may not have been transported correctly or completely.
- Authorization Issues: The user may not have the necessary authorizations to view or access the InfoObject in the specified data basis.
Solution:
Check InfoObject Existence:
- Go to the SAP BW modeling tools or transaction code RSA1 and check if the InfoObject exists in the specified data basis.
- If it does not exist, you may need to create it or restore it from a backup.
Verify Data Basis:
- Ensure that you are referencing the correct data basis. Check the settings in your query or data model to confirm that the correct InfoProvider is being used.
Transport Check:
- If the InfoObject was recently transported, check the transport logs to ensure that it was successfully transported. If not, you may need to re-transport it.
Authorization Check:
- Verify that the user has the necessary authorizations to access the InfoObject. You may need to consult with your SAP security team to ensure proper access rights.
Rebuild or Activate:
- If the InfoObject exists but is inactive, you may need to activate it. This can be done in the InfoObject maintenance screen.
Check for Naming Issues:
- Ensure that there are no typographical errors in the name of the InfoObject or data basis being referenced.
Related Information:
If the issue persists after following these steps, consider reaching out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
UGX2020
InfoObject &1 is not registered in the data basis
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
UGX2019
Save data basis &1 again
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
UGX2022
Selection type of variables &1 of query &2 is not supported
What causes this issue? For variables with the type <LS>Hierarchy Node</>, only the <LS>Single Value</> selection type is sup...
UGX2023
Report category &1 cannot be used
What causes this issue? Report category &V1& is based on data basis &V2&. If the data model is changed, you are required to regenerat...
Click on this link to search all SAP messages.