How To Fix KU228 - Hierarchy ID not yet generated

SAP Error Message - Details

• Message type: E = Error

• Message class: KU - Costing: Rollup

• Message number: 228

• Message text: Hierarchy ID not yet generated

What causes this issue?

The hierarchy ID for the cost object hierarchy has not yet been entered
in Customizing.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Go into Customizing for Product Cost Accounting and process the step
"Create hierarchy" under Information systems -> Repetitive
manufacturing -> Cost object summarization.

<DS:TRAN.OKRZ> Proceed </>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KU228 - Hierarchy ID not yet generated ?

  The SAP error message KU228, which states "Hierarchy ID not yet generated," typically occurs in the context of SAP Controlling (CO) when working with cost center hierarchies or other hierarchical structures. This error indicates that the system is unable to find a valid hierarchy ID for the operation you are trying to perform, often because the hierarchy has not been created or activated yet.
  Causes:
  
  Hierarchy Not Created: The hierarchy you are trying to use has not been created in the system.
  Hierarchy Not Activated: The hierarchy exists but has not been activated or generated properly.
  Missing Authorizations: The user may not have the necessary authorizations to access or view the hierarchy.
  Data Inconsistencies: There may be inconsistencies in the data that prevent the hierarchy from being generated.
  
  Solutions:
  
  
  Create the Hierarchy:
  
  Navigate to the relevant transaction (e.g., KSH1 for cost center hierarchy) and create the required hierarchy if it does not exist.
  
  
  
  Activate the Hierarchy:
  
  If the hierarchy exists but is not activated, you can activate it using the appropriate transaction (e.g., KSH2 for changing the hierarchy and activating it).
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the hierarchy. This may involve checking roles and permissions in the user profile.
  
  
  
  Review Data:
  
  Check for any inconsistencies or missing data that might prevent the hierarchy from being generated. This may involve reviewing the underlying master data or configuration settings.
  
  
  
  Re-generate the Hierarchy:
  
  If the hierarchy was previously generated but is now causing issues, you may need to re-generate it. This can often be done through the same transaction used to create or activate the hierarchy.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific steps related to your version of SAP, as the process may vary slightly depending on the system configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KSH1 (Create Hierarchy), KSH2 (Change Hierarchy), and KSH3 (Display Hierarchy).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Support: If the issue persists after trying the above solutions, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to resolve the KU228 error and successfully work with the hierarchy in SAP.