How To Fix FICUSTOM264 - Budget address &1 cannot be a leaf node in the hierarchy

FICUSTOM264 - Overview

• Message type: E = Error

• Message class: FICUSTOM - Customizable Messages for Funds Management

• Message number: 264

• Message text: Budget address &1 cannot be a leaf node in the hierarchy

What causes this issue?

The definition of budget addresses defined in subhierarchy (transaction
FMHIE_HIEID) is "All Account Assignments Except End Nodes are Valid
Budget Addresses". However, Budget address &V1& is not en end node in
the hierarchy.

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 the budget address in transaction
<LS>Edit Hierarchy</> (transaction FMHIE_HIEID) from All Account
Assignments Except End Nodes are Valid Budget Addresses? to "All Account
Assignments are Valid Budget Addresses?.
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 FICUSTOM264 - Budget address &1 cannot be a leaf node in the hierarchy ?

  The SAP error message FICUSTOM264 indicates that the budget address specified cannot be a leaf node in the hierarchy. This typically occurs in the context of budget management within SAP, particularly when dealing with budget structures and hierarchies.
  
  Cause:
  
  Hierarchy Structure: The error arises when you attempt to assign a budget to a node in the hierarchy that is not a leaf node. A leaf node is a node that does not have any child nodes. In budget hierarchies, only leaf nodes can have budgets assigned to them.
  Incorrect Node Selection: You may have selected a node that is intended to be a parent or intermediate node rather than a final node where budget allocations are made.
  
  Configuration Issues: There may be issues with how the budget hierarchy is configured in the system, leading to incorrect node classifications.
  
  
  Solution:
  
  Check Node Type: Verify that the budget address you are trying to use is indeed a leaf