How To Fix FMHIE_CHGCHK_CUST026 - Address &1 is no longer a leaf node after its subordinate was moved

SAP Error Message - Details

• Message type: E = Error

• Message class: FMHIE_CHGCHK_CUST - Customizable Messages for BCS Hierarchy Change

• Message number: 026

• Message text: Address &1 is no longer a leaf node after its subordinate was moved

What causes this issue?

Moving a node to a new parent address &V1& may violate Budget Address or
Posting Address definition rules maintained in <LS>Create and Assign
Hierarchy ID</> (transaction FMHIE_HIEID). The Budget Address list or
Posting Address list may become invalid by reason of return code &V2&.

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

System Response

The system recognizes the following return codes for the Budget Address
and Posting Address list checks:
<ZH>Return code 1:</>
BA rule: "All addresses in MBS are valid budget addresses"
PA rule: "All addresses in MBS are valid posting addresses"
No inconsistency for the current Budget Address or Posting Address
lists.
<ZH>Return code 2:</>
BA rule: "All addresses in MBS are valid budget addresses"
PA rule: "Only leaf addresses in MBS are valid posting address"
The moving of nodes has no impact on the current Budget Address list.
The moving of the node results in Posting Address list inconsistency,
because the new parent node &V1& was a leaf node and has actual
postings. The new parent address &V1& of the moved node is no longer a
valid posting address.
<ZH>Return code 3:</>
BA rule: "All addresses except leaf addresses are valid budget
addresses"
PA rule: "All addresses in MBS are valid posting addresses"
The move results in Budget Address list inconsistency, because the new
parent address &V1& is no longer a leaf node and a valid budget address
after the move.
<ZH>Return code 4:</>
BA rule: "All addresses except leaf addresses are valid budget
addresses"
PA rule: "Only leaf addresses in MBS are valid posting addresses"
The move results in Budget Address list inconsistency, because the old
parent address &V1& becomes a leaf node after the move. The parent
address &V1& is no longer a valid budget address.
The move results in Posting Address list inconsistency, because the new
parent address &V1& was a leaf node and has actual postings. The new
parent address &V1& of the moved node is no longer a posting address.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FMHIE_CHGCHK_CUST026 - Address &1 is no longer a leaf node after its subordinate was moved ?

  The SAP error message FMHIE_CHGCHK_CUST026 indicates that there is an issue with the hierarchical structure of addresses in the system. Specifically, it means that the address you are trying to modify or work with (denoted as &1) is no longer a "leaf node" because one of its subordinate addresses has been moved. In hierarchical data structures, a leaf node is a node that does not have any children (subordinate nodes).
  Cause:
  The error typically occurs in the following scenarios:
  
  Hierarchical Changes: A subordinate address (child node) has been moved to a different parent address, which affects the original parent address's status as a leaf node.
  Data Integrity Issues: There may be inconsistencies in the address hierarchy due to manual changes or data imports that did not maintain the hierarchical structure.
  System Configuration: Changes in the configuration of address management or related modules may lead to this error if the hierarchy is not properly maintained.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Hierarchy: Review the address hierarchy in the system to understand the current structure. Identify the subordinate addresses and their new parent nodes.
  
  
  Reassign Subordinate Addresses: If necessary, reassign the subordinate addresses back to the original parent address or to a new appropriate parent address to restore the hierarchy.
  
  
  Update the Address: If you are trying to update the address that is causing the error, ensure that the changes you are making do not violate the hierarchical structure. You may need to adjust your changes based on the current hierarchy.
  
  
  Data Consistency Check: Run any available data consistency checks or reports in SAP to identify and correct any inconsistencies in the address data.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on managing address hierarchies and resolving related errors.
  
  
  Contact Support: If the issue persists and you are unable to resolve it, consider reaching out to SAP support or your internal IT team for further assistance.
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like BP (Business Partner) or SUC01 (for address management) to view and manage addresses.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Custom Development: If your organization has custom developments related to address management, review those for potential issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.