How To Fix GK217 - Old and new hierarchy level of & do not concur.

SAP Error Message - Details

• Message type: E = Error

• Message class: GK - Messages for SAP Consolidation

• Message number: 217

• Message text: Old and new hierarchy level of & do not concur.

What causes this issue?

Hierarchy levels are used in the current dimension. Therefore cons
groups are assigned to a clearly defined hierarchy level of the
dimension, which are defined in the master data of the cons group.
In the requested action, the cons group should be reassigned to another
hierarchy level, which deviates from the hierarchy level defined in the
master record. This would lead to inconsistencies (also for cons groups
under it).

System Response

Error message

How to fix this error?

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 GK217 - Old and new hierarchy level of & do not concur. ?

  The SAP error message GK217 "Old and new hierarchy level of & do not concur" typically occurs in the context of SAP's controlling (CO) module, particularly when dealing with cost center hierarchies or other organizational structures. This error indicates that there is a mismatch between the old and new hierarchy levels for a specific object, such as a cost center or internal order.
  Cause:
  
  Hierarchy Changes: The error usually arises when there is an attempt to change the hierarchy level of a cost center or another organizational unit, but the system detects that the new level does not match the expected level based on the existing hierarchy.
  Data Inconsistency: There may be inconsistencies in the data, such as incorrect assignments or missing entries in the hierarchy structure.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to make changes to the hierarchy, leading to this error.
  
  Solution:
  
  Check Hierarchy Levels: Verify the current hierarchy levels for the object in question. Ensure that the new hierarchy level you are trying to assign is valid and corresponds to the existing structure.
  Review Changes: If you are making changes to the hierarchy, review the changes to ensure they are consistent with the existing hierarchy. You may need to revert to the previous level if the new level is not valid.
  Data Consistency Check: Run consistency checks on the hierarchy data to identify any discrepancies. This can often be done through transaction codes like KSH1 (Create Cost Center) or KSH2 (Change Cost Center) to review the hierarchy structure.
  Authorization Check: Ensure that you have the necessary authorizations to make changes to the hierarchy. If not, contact your SAP administrator to obtain the required permissions.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on managing hierarchies in your version of SAP.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KSH1, KSH2, KSH3 (Display Cost Center), and others related to hierarchy management.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional context or solutions for specific scenarios.
  Support: If the issue persists, consider reaching out to SAP support or your internal IT team for further assistance.
  
  By following these steps, you should be able to resolve the GK217 error and ensure that your hierarchy levels are correctly aligned.