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: FAGL_FSV_MAINTENANCE - Maintenance of Financial Statement Versions
Message number: 112
Message text: Unknown dimension &1 used in the taxonomy
An unknown dimension is used in an <ZH>arcrole</> with the type <ZH>
dimension-domain</>. There is an inconsistency in the taxonomy.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Validate the taxonomy.
If validation fails to identify the error, contact SAP support.
Error message extract from SAP system. Copyright SAP SE.
FAGL_FSV_MAINTENANCE112
- Unknown dimension &1 used in the taxonomy ?The SAP error message FAGL_FSV_MAINTENANCE112, which states "Unknown dimension &1 used in the taxonomy," typically occurs in the context of Financial Statement Versions (FSV) when there is an issue with the dimensions defined in the taxonomy for financial reporting.
Cause:
Invalid Dimension: The error indicates that a dimension referenced in the financial statement version (FSV) is not recognized by the system. This could happen if:
- The dimension has been deleted or is not defined in the system.
- There is a typo or incorrect reference in the configuration.
- The dimension is not activated or is not available in the current context.
Configuration Issues: If the taxonomy or the financial statement version has been recently modified, it may reference dimensions that are no longer valid.
Transport Issues: If changes were transported from one system to another (e.g., from development to production), there may be inconsistencies in the dimensions available in the target system.
Solution:
Check Dimension Definition:
- Go to the transaction code OB58 (for Financial Statement Versions) and verify the dimensions defined in your FSV.
- Ensure that the dimension referenced in the error message is correctly defined and active.
Correct the FSV Configuration:
- If you find that the dimension is indeed invalid, you will need to either remove it from the FSV or replace it with a valid dimension.
- Make sure that all dimensions used in the FSV are correctly configured and available.
Review Recent Changes:
- If the error occurred after recent changes, review those changes to identify any modifications that may have led to the issue.
- If necessary, revert the changes or correct the configuration.
Transport Consistency:
- If the issue arose after a transport, check the transport logs and ensure that all necessary objects were transported correctly.
- You may need to re-transport the missing dimensions or configurations.
Consult Documentation:
- Refer to SAP documentation or notes related to financial statement versions and dimensions for additional guidance.
Related Information:
Transaction Codes:
SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
Support: If the issue persists after following the above steps, consider reaching out to SAP support or your internal SAP team for further assistance.
By following these steps, you should be able to identify and resolve the cause of the FAGL_FSV_MAINTENANCE112 error in your SAP system.
Get instant SAP help. Sign up for our Free Essentials Plan.
FAGL_FSV_MAINTENANCE110
File &1: Locator element &2 is unknown
What causes this issue? An unknown locator element is used in the presentation or the definition of the element hierarchy. There can be several cause...
FAGL_FSV_MAINTENANCE109
File &2 does not exist in ZIP file &1
What causes this issue? When the taxonomies are processed, the system first converts the entry schema (the leading taxonomy). This contains a list of...
FAGL_FSV_MAINTENANCE116
Type &1 is not defined in accordance with XBRL specification
What causes this issue? For tuples, dimensions, and taxonomy elements, XBRL restricts how the underlying types can be defined.System Response The sy...
FAGL_FSV_MAINTENANCE117
Type &1 cannot be traced back to a basic type
What causes this issue? New types can be defined in the xsd files. The system analyzes the type definitions. In the present case, the analysis of the...
Click on this link to search all SAP messages.