How To Fix RH226 - Node characteristic &1 is not entered as hierarchy characteristic for &2

RH226 - Overview

• Message type: E = Error

• Message class: RH - BW: Hierarchies ( basic functions )

• Message number: 226

• Message text: Node characteristic &1 is not entered as hierarchy characteristic for &2

What causes this issue?

Characteristic &V1& is not permitted as an <ZK>external characteristic
in hierarchies</> for characteristic &V2&. Therefore the node with node
name &V4& and the InfoObject &V1& are not permitted. A characteristic
can be used as an external characteristic in hierarchies if it is
entered as an <ZK>external characteristic in hierarchies</> in
InfoObject maintenance for the characteristic.

System Response

Hierarchy &V3& cannot be activated.

How to fix this error?

Change the hierarchy "&V3&". Enter the characteristic &V1& as an
external characteristic in InfoObject maintenance of characteristic &V2&
. To do this, choose <LS>Hierarchy Tab Page -> External Characteristics
in Hierarchies</> or modify the hierarchy.

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.

RH226 - Details

• The SAP error message RH226 indicates that a node characteristic (in this case, represented by &1) is not entered as a hierarchy characteristic for a specific hierarchy (represented by &2). This typically occurs in the context of SAP's Organizational Management (OM) or similar modules where hierarchical structures are defined.
  
  Cause:
  
  Missing Configuration: The node characteristic that is being referenced has not been configured as a hierarchy characteristic in the relevant hierarchy definition.
  Incorrect Hierarchy Setup: The hierarchy itself may not be set up correctly, or the node characteristic may not be included in the hierarchy definition.
  Data Entry Error: There may be a mistake in the data entry where the node characteristic is expected but not provided.
  
  
  Solution:
  
  
  Check Hierarchy Configuration:
  
  Go to the transaction code for maintaining the hierarchy (e.g., PPOME for Organizational Management).
  Verify that the node characteristic (&1) is included in the hierarchy definition for the specified hierarchy (&2).
  If it is missing, you will need