How To Fix GK620 - The hierarchy name could not be derived for the item hierarchy

SAP Error Message - Details

• Message type: E = Error

• Message class: GK - Messages for SAP Consolidation

• Message number: 620

• Message text: The hierarchy name could not be derived for the item hierarchy

What causes this issue?

You used the globale hierarchy variable <ZH><(>&<)>0FROMITM</> for the
characteristic <DS:GLOS.3526B792AFAB52B9E10000009B38F974>financial
statement item</> in the report. The system was unable to derive the
hierarchy name for this characteristic from the characteristics
<DS:GLOS.3526B795AFAB52B9E10000009B38F974>consolidation chart of
accounts</> and <DS:DE.FC_DDSUMIT>totals item</>.

System Response

No hierarchy will be displayed.

How to fix this error?

Try to make sure that the value for the characteristic Cons Chart of
Accounts is unambiguous in the report. You can achieve this by defining
the characteristic in the report via the characteristic selection, or
in the layout by creating exactly <ZH>one</> variable for the
characteristic as the variable for the "from" value. If this condition
is met, all item hierarchies for this cons chart of accounts are
displayed.
Similarly, if the value for the Totals Item is unambiguous, then the
sub-hierarchy belonging to this totals item is displayed.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message GK620 - The hierarchy name could not be derived for the item hierarchy ?

  The SAP error message GK620, which states "The hierarchy name could not be derived for the item hierarchy," typically occurs in the context of SAP's controlling (CO) module, particularly when dealing with item hierarchies in Profit Center Accounting or similar areas.
  Cause:
  The error can arise due to several reasons, including:
  
  
  Missing Hierarchy Definition: The item hierarchy you are trying to use may not be defined in the system. This could happen if the hierarchy was not created or if it was deleted.
  
  
  Incorrect Configuration: There may be issues with the configuration settings related to the hierarchy. This includes incorrect assignment of the hierarchy to the relevant controlling area or other organizational units.
  
  
  Data Inconsistencies: There could be inconsistencies in the master data or transactional data that prevent the system from deriving the hierarchy name.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the hierarchy, leading to this error.
  
  
  Solution:
  To resolve the GK620 error, you can take the following steps:
  
  
  Check Hierarchy Definition:
  
  Go to the transaction code KSH1 (Create Hierarchy) or KSH2 (Change Hierarchy) to verify if the item hierarchy exists.
  If it does not exist, create the necessary hierarchy.
  
  
  
  Review Configuration:
  
  Use transaction code OKA0 to check the configuration settings for the controlling area and ensure that the hierarchy is correctly assigned.
  Ensure that the hierarchy is active and properly configured.
  
  
  
  Validate Master Data:
  
  Check the master data related to the item hierarchy. Ensure that all necessary data is correctly maintained and that there are no inconsistencies.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the hierarchy. You may need to consult with your SAP security team to verify this.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the process to identify where the hierarchy name derivation is failing. This may require assistance from a technical consultant.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KSH1, KSH2, OKA0, and KSH3 (Display Hierarchy).
  Documentation: Review SAP documentation related to Profit Center Accounting and item hierarchies for a deeper understanding of how hierarchies are structured and utilized.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing insights or solutions from other users' experiences.
  
  By following these steps, you should be able to identify the root cause of the GK620 error and implement a suitable solution.