Understanding Load Item - Segment Hierarchies for Define Overall Rule Settings

Hierarchy Type: Select Main Hierarchy unless you are loading data to an Alternate Hierarchy.

Member

• Allow Move: Select to allow parent changes for existing members.

• Allow Property Change: Select to allow Property Changes (i.e. name, currency, or other system properties) for existing members.

Roll-Up Operator Behavior for Segment Hierarchy Loads

By default, when uploading a leaf member of a segment hierarchy via a DLR input file with Allow Property Change enabled, the system updates the properties, including the parent’s roll-up operator, based on the value specified for the leaf node.

This feature is especially useful when you want to update the properties of leaf nodes during a DLR upload without affecting parent node roll-up operators.

Notes:

• This feature is opt-in and applies only to the Main Hierarchy.

• Contact Planful Support to enable this functionality.

• This impact applies to both new and existing leaf nodes loaded via DLRs.

How It Works

To update only the Leaf Node roll-up operator and not the parent node roll-up operator, the following conditions must be met:

Note:

If any required condition is not met (e.g., an entry set to No in the leaf node column), the system reverts to default behavior where parent roll-up operators are updated based on the uploaded file.

Example:

You upload a segment hierarchy file where the leaf node Account_4000 has a roll-up operator of "~". It rolls up to a parent node Account_3000, which currently uses a "+" roll-up operator.

You upload a segment hierarchy file where the leaf node Account_4000 has a roll-up operator of "~". It rolls up to a parent node Account_3000, which currently uses a "+" roll-up operator.

• With the feature enabled and all conditions met:  

  • Only Account_4000 is updated to "~".

  • Account_3000 retains its existing "+" operator.

• Without the feature, or if any condition is not met:  

  • Both Account_4000 and its parent Account_3000 are updated to "~".

Note:

This feature is supported only for the Main Hierarchy. It does not apply to Alternate Hierarchies.

Build

• Level: Build a hierarchical level.

  • Select Number of Levels: Available if you select the Level option. Select the number of levels you want your hierarchy to consist of.

• Parent Child: Build a parent child based hierarchy.

Parent Child Versus Level Based Hierarchies

A Parent Child hierarchy is one where you have a child field and a parent field. For example, let's say you have a table with employee department details and associated sub-ordinates.

Matt is the ultimate boss of the department. Matt has 2 sub-ordinates: Brian and Jim. Brian's sub-ordinate is Katy.

A Level Based hierarchy has the following structure.

MattBrianKaty

Ragged hierarchies is supported (hierarchies with varying levels of tree depth) while loading Level based segment hierarchies using a Data Load Rule.

Parameter

The parameters listed are those available to be included in the data file. If an elimination company was set up in Hierarchy Management, you may have a default Elim Attribute parameter (as shown below). Select Yes for Include in Data File for the Elim Attribute to obtain the value from the data you are loading to Planful. This Parameter is available for Segment Hierarchy and Alternate Hierarchy data loads.

Include in Clear Data

Select segments to clear or retain data for. For example, if you load data for Company A and then want to use the same data load rule to load data for Company B, the data loaded for Company A will not be deleted if you do not choose to clear the data.

Include in Data File

Select Yes if a dimension is not defined within the data file and there is a common member for all records.

Select No if you do not want the listed parameters in the data file.

Select

Available if you select No for a parameter. Search for other dimensions to associate with the data file.