Creating Trees

Trees are used in Global Consolidations to describe your consolidation structure, for reporting, and for defining ChartField value sets. For detailed information about creating trees, see the PeopleTools Tree Manager documentation.

See PeopleTools Documentaion: PeopleSoft Tree Manager

You create consolidation trees to depict the hierarchical relationship of the entities within a consolidation. You must define a different consolidation tree for each unique dimension by which you consolidate. For example, to create two consolidation models—one that consolidates by business unit and one that consolidates by department—you would need a separate tree for each. You assign one consolidation tree per consolidation model. When you process consolidations, you specify which node of the tree (and its descendents) to consolidate. Consolidation trees are node-oriented trees.

Each branch or parent node in your consolidation tree must include one, and only one, elimination entity. Journal entries created during consolidation processing are booked to the elimination entity. This is a "logical" object that must be defined within the dimension table of the consolidation dimension. For example, if your consolidation dimension is department, then you need to create a "logical" elimination department at each node of the consolidation tree. If you are consolidating by business unit, you need to create a business unit definition for the elimination entity. Typically the root node of a business unit consolidation tree is the common consolidation business unit, but that is not a requirement.

When processing eliminations, equitization, and non-controlling interest, the system uses the tree structure to determine where to book the resulting journal entries. Elimination and non-controlling interest book the entries for each entity in the consolidation tree at the corresponding elimination node. Equitization records the reversing entries in the elimination node; the equitization entries are booked to the parent. In cases where transactions occur between business units (or other consolidation dimension) located at different levels of the tree, the application engines use the lowest common elimination entity between parent and subsidiary to book the entries.

Besides the consolidation tree, there are other trees that you need to define. For example, you use an account tree when establishing ChartField value sets to specify a group of particular accounts. You must create a business unit tree for the consolidation model even when you are consolidating by a dimension other than business unit. In addition, trees are used for some inquiry pages as reporting trees, and control the level at which information is grouped. Trees used as inquiry page reporting trees must be defined with the Use of Levels field set to strictly enforced.

You must establish metadata for each tree that you define. Within the PeopleSoft Performance Warehouse framework, the metadata is used when running processes and using inquiry pages. Refer to the PeopleSoft Enterprise Performance Management Fundamentals 9.1 Documentaion for information about setting up metadata.

See Setting Up and Flattening Tree Metadata.

For detailed information about creating trees, see the PeopleSoft Tree Manager documentation in PeopleTools Documentaion: PeopleSoft Tree Manager.

For detailed information about establishing tree metadata, see PeopleSoft Enterprise Performance Management Fundamentals 9.1 Documentaion.

See Setting Up and Flattening Tree Metadata.