Do you have any question about this error?
Message type: E = Error
Message class: FCO_AVC - Availability Control
Message number: 119
Message text: The GL account hierarchy that you have entered doesnÆt exist.
The G/L account hierarchy that you have entered doesn?t exist.
There are two possibilities for this situation.
The pre-delivered hierarchy YBA000_CE, which is included in the cloud
content, hasn?t been generated as a global accounting hierarchy of type
G/L account hierarchy. This generation activity is mandatory and must be
performed before you configure the budget availability control profile.
OR
The G/L account hierarchy that you have entered hasn?t been created in
the <LS>Manage Global Hierarchies</> app.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Ensure that you have completed the preliminary steps that are described
in in the product assistance under:
<LS>Budget Availability Control > Budget Availability Control for Cost
Centers > Maintain Account Groups</>
Ensure that the G/L account hierarchy that you have entered has been
created in the <LS>Manage Global Hierarchies</> app.
The G/L account hierarchy that you have entered hasn?t been created in
the <LS>Manage Global Hierarchies</> app.
Ensure that the G/L account hierarchy that you have entered has been
created in the <LS>Manage Global Hierarchies</> app.
Error message extract from SAP system. Copyright SAP SE.
FCO_AVC119
- The GL account hierarchy that you have entered doesnÆt exist. ?The SAP error message FCO_AVC119 indicates that the General Ledger (GL) account hierarchy you are trying to use does not exist in the system. This error typically occurs when you are attempting to perform a financial transaction or reporting that requires a specific GL account hierarchy, but the system cannot find it.
Cause:
- Incorrect Hierarchy Name: The GL account hierarchy name entered may be misspelled or incorrectly formatted.
- Hierarchy Not Created: The GL account hierarchy has not been created in the system.
- Inactive Hierarchy: The hierarchy may exist but is inactive or not available for the current fiscal year or period.
- Authorization Issues: The user may not have the necessary permissions to access the specified hierarchy.
- Configuration Issues: There may be issues with the configuration settings in the Financial Accounting (FI) module.
Solution:
- Verify Hierarchy Name: Double-check the name of the GL account hierarchy you are entering to ensure it is correct.
- Create Hierarchy: If the hierarchy does not exist, you will need to create it. This can typically be done in the SAP GUI under the appropriate configuration settings (e.g., using transaction code OKEQ for managing account hierarchies).
- Activate Hierarchy: If the hierarchy exists but is inactive, you may need to activate it. This can also be done in the configuration settings.
- Check Authorizations: Ensure that the user has the necessary authorizations to access the GL account hierarchy. This may require coordination with your SAP security team.
- Consult Configuration: Review the configuration settings in the FI module to ensure that everything is set up correctly. This may involve checking the settings for account groups, account types, and hierarchies.
Related Information:
By following these steps, you should be able to resolve the FCO_AVC119 error and successfully work with the GL account hierarchy in SAP.
Get instant SAP help. Start your 7-day free trial now.
FCO_AVC118
In profile &1, select account groups with the same chart of accounts.
What causes this issue? In budget availability control profile &v1&, there are account groups that belong to different charts of accounts. Ea...
FCO_AVC117
The warning tolerance is greater than or equal to the error tolerance.
What causes this issue? In availability control profile &v1&, hierarchy &v2&, account group &v3& , and activity group &v4...
FCO_AVC120
Account group &2 doesn't exist in hierarchy &1.
What causes this issue? Account group <(>&<)>2 doesn't exist in hierarchy <(>&<)>1. There are two possibilities...
FCO_AVC121
Assign account &2 to only one account group in profile &1.
What causes this issue? In budget availability control profile &v1&<(>,<)> account &v2& is assigned to both account group...
Click on this link to search all SAP messages.