How To Fix KU105 - Old branch of hierarchy read. Number of nodes = &

SAP Error Message - Details

• Message type: E = Error

• Message class: KU - Costing: Rollup

• Message number: 105

• Message text: Old branch of hierarchy read. Number of nodes = &

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message KU105 - Old branch of hierarchy read. Number of nodes = & ?

  The SAP error message KU105, which states "Old branch of hierarchy read. Number of nodes = &," typically occurs in the context of SAP's Controlling (CO) module, particularly when dealing with cost center hierarchies or other hierarchical structures.
  Cause:
  This error message usually indicates that the system is trying to access a hierarchy that is outdated or has been modified. The "Old branch of hierarchy" suggests that the hierarchy being referenced is not the current version, which can happen due to:
  
  Changes in Hierarchy Structure: If the hierarchy has been changed (nodes added, removed, or modified) and the system is still referencing an old version.
  Data Consistency Issues: There may be inconsistencies in the data, possibly due to incomplete updates or errors during data processing.
  Caching Issues: Sometimes, the system may cache old versions of the hierarchy, leading to this error when trying to access it.
  
  Solution:
  To resolve the KU105 error, you can take the following steps:
  
  
  Refresh the Hierarchy: Ensure that the hierarchy is refreshed in the system. This can often be done by reloading or reactivating the hierarchy in the relevant transaction (e.g., using transaction code OKEB for cost center hierarchies).
  
  
  Check for Changes: Verify if there have been any recent changes to the hierarchy. If changes were made, ensure that all relevant transactions and reports are updated to reflect the new structure.
  
  
  Clear Cache: If the issue is related to caching, you may need to clear the cache. This can sometimes be done through transaction codes like SE38 or SE80, depending on your system configuration.
  
  
  Consistency Check: Run consistency checks on the hierarchy to ensure that all nodes and branches are correctly defined and that there are no orphaned nodes.
  
  
  Consult Documentation: Check SAP Notes or documentation related to your specific version of SAP for any known issues or patches that might address this error.
  
  
  Contact SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance. They may provide specific guidance based on your system configuration and version.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OKEB (for cost center hierarchy) and OKEE (for cost element hierarchy).
  SAP Notes: Search for SAP Notes related to error KU105 in the SAP Support Portal for any specific fixes or updates.
  Documentation: Review the SAP Help Portal for detailed information on managing hierarchies in the Controlling module.
  
  By following these steps, you should be able to address the KU105 error effectively.