Show TOC

 Processing Multi-Level Budget Structures Locate this document in the navigation structure

Use

If the existing multi-level budget structure does not satisfy your business requirements, you can make changes to it.

When you run this program (transaction FMHIE_CHANGE), you can process a multi-level budget structure or a part of it, for a hierarchy ID, FM area, fiscal year, budget category and budget structure.

You can do the following using this program:

  • Move a node within the multi-level budget structure using drag and drop
  • Add a single node, a list of nodes or a sub-tree to a selected node
  • Set a node as the top node of a multi-level budget structure
  • Delete a sub-tree starting from the selected node

This graphic is explained in the accompanying text.

You need to enter a hierarchy ID, even where no FM account assignment element has the role ‘constant’ for the given FM area and budget structure, in which case there is just a single hierarchy ID.

When you add a sub-tree from master data group, each non-leaf sub-group in the specified group must correspond to exactly one single master data element. The hierarchy relationships among sub-groups in the specified group form hierarchy relationships for the master data in the different sub-groups.

It is possible for different users to process different parts of the multi-level budget structure for the same hierarchy ID simultaneously, provided the parts being processed do not overlap.

Prerequisites

You have generated multi-level budget structure for a hierarchy ID, FM area, fiscal year, budget category and budget structure (transaction FMHIE_GENERATION) or copied a multi-level budget structure (transaction FMHIE_COPY).

Procedure

Proceed as follows:

In the Accounting part of the Easy Access menu, choose Public Sector Management ® Funds Management ® Master Data ® Use of Account Assignment Elements ® Budgeting ® Budget Control System (BCS)  Structure ® Multi-Level Budget Structure ® Change

Enter the FM area and a multi-level budget structure.

Enter the fiscal year, the budget category and if necessary the hierarchy ID.

Restriction on multi-level budget structure: you can restrict the selection by entering the access objects to the multi-level structure with a list and the number of steps below the access objects.

This graphic is explained in the accompanying text.

If two or more selected branches (combination of an access object and number of steps) are on the same branch of the structure, the entire branch (containing all the selected branches without gaps) is selected for processing.

If necessary, select aLayout Variantto be used when you display the multi-level budget structure.

Execute the transaction.

Result

The selected multi-level budget structure is displayed in aSAPList Viewer tree structure where you can:

  • Expand the structure below the selected node
  • Collapse the structure below the selected node
  • Find a node
  • Set a node as the top node
  • Print a multi-level budget structure
  • Select a layout
  • Change layout
  • Save layout
  • Manage layout
  • Delete a subtree
  • Add a new node manually on the same level
  • Add a list of nodes on the same level
  • Add a subtree of nodes on the same level (the root node of the sub-tree will be on the same level as the selected node)
  • Add a new node manually as a subnode
  • Add a list of nodes as subnodes
  • Add a subtree of nodes as subnodes (the root node of the subtree will be a subnode of the selected node)
Checking for consistency when processing a multi-level budget structure:

When you use transactionFMHIE_CHANGE to process a pre-existing multi-level budget structure, the changes you make could lead to inconsistencies. You can activate checks which will alert you to any such inconsistencies in Customizing. For more information, see Using Consistency Checks with Multi-Level Budget Structures .