How To Fix RY118 - Hierarchy of generic trans. with int. no. &, ext. no. & is inconsistent

RY118 - Overview

• Message type: E = Error

• Message class: RY - Messages for RM Basis

• Message number: 118

• Message text: Hierarchy of generic trans. with int. no. &, ext. no. & is inconsistent

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 RY118 - Hierarchy of generic trans. with int. no. &, ext. no. & is inconsistent ?

  The SAP error message RY118 indicates that there is an inconsistency in the hierarchy of generic transactions, specifically related to internal and external numbers. This error typically arises in the context of SAP's controlling (CO) module, particularly when dealing with cost centers, internal orders, or other hierarchical structures.
  
  Cause:
  
  
  Inconsistent Hierarchy: The error usually occurs when there is a mismatch or inconsistency in the hierarchy of the generic transactions. This could be due to:
  
  Missing or incorrectly defined nodes in the hierarchy.
  Changes made to the hierarchy structure that have not been properly reflected in all related transactions.
  Data inconsistencies due to manual entries or incorrect configurations.
  
  
  
  Data Integrity Issues: If the data integrity is compromised, such as when transactions are not properly linked to their parent nodes or if there are orphaned nodes, this error can occur.
  
  
  Configuration Errors: Incorrect configuration settings in the controlling area or in the hierarchy settings can lead to this error.
  
  
  
  Solution:
  
  
  Check