How To Fix FICUSTOM273 - Address &1 is no longer a leaft node after insertion

FICUSTOM273 - Overview

• Message type: E = Error

• Message class: FICUSTOM - Customizable Messages for Funds Management

• Message number: 273

• Message text: Address &1 is no longer a leaft node after insertion

What causes this issue?

Inserting account assignment &V3& can go against the rules for posting
addresses that were defined in transaction Create/Assign Subhierarchy_ID
(FMHIE_HIEID). You have defined the following posting address rule:
"Only Account Assignments at End Node Level in the BS are Valid Posting
Addresses". After making the insertion, the account assignment &V1& is
no longer an end node, but it is still in the posting address list.

System Response

Processing is terminated.

How to fix this error?

You can correct the error in one of the following ways:
Change the definition rule for budget addresses or postings addresses in
transaction Create/Assign Subhierarchy_(FMHIE_HIEID) to "All Account
Assignments in the Hierarchy are Valid Posting Addresses" or "Posting
Addresses are Hierarchy-Independent".
Delete the posting address from the posting address list using
transaction <DS:TRAS.FMBSPO>FMBSPO</>.
Set this message to a warning, information, or ignore if you want to
override this message in Customzing under <LS>Funds Management
Government -> Basic Settings -> Change Message Control</>. However, when
doing this, note that overriding the message can cause inconsistencies
to occur in the multi-level budget structure.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FICUSTOM273 - Address &1 is no longer a leaft node after insertion ?

  The SAP error message FICUSTOM273 indicates that the address you are trying to insert or modify is no longer a "leaf node" in the address hierarchy. In the context of SAP, a "leaf node" typically refers to an address that does not have any sub-addresses or child nodes associated with it. When you attempt to insert a new address or modify an existing one, the system checks the hierarchy and finds that the address you are working with has been altered in such a way that it is no longer a leaf node.
  
  Cause:
  
  Hierarchy Changes: The address you are trying to insert or modify has been changed in the hierarchy, possibly due to the addition of sub-addresses or related addresses.
  Data Integrity Issues: There may be inconsistencies in the address data that violate the expected structure of the address hierarchy.
  Concurrent Modifications: Another user or process may have modified the address structure while