Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


PeopleSoft Trees

No description

Scott Thornton

on 7 October 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of PeopleSoft Trees

PeopleSoft Trees
Tree Concepts
Types of Trees
Appropriation Budget Checking
Effective Dates
Effective dates enable you to specify changes in advance and have them take effect automatically. E.g. your organizational structure changes on January 1, 2014. The changes to a tree based on the Org code can be made in advance.

Effective dates also allow reporting based on the current, historic or future data.
Most data in system control tables is stored by SetID. In many cases the SetID will be "SHARE" indicating that the values are used enterprise-wide. The Account ChartField will be a SHARE SetID.

In other cases the SetID may be specific to an agency. For example the Org Code.
PeopleSoft trees depict hierarchical structures that represent a group of summarization rules for a particular database field. A tree can specify how detail is rolled up for reporting, categorize items in a catalog or depict your organizational hierarchy. The summarized detail are referred to as "nodes".
Levels can be strictly enforced: Level describes each node's position in tree.


Loosely enforced levels mean that the nodes at the same visual indentation do not all represent the same kind of information.

You will use levels for most trees. They are required for summary trees and cannot be added later.
Tree Levels
Tree with Levels
Business Units and SetID
The Business Unit (BU) will be the equivalent of the current "Agency". Because PeopleSoft requires this field to be 5-characters, the BU will be your agency number followed by two zeros. E.g. Public Defender (agency 550) will be 55000.

The same code will be used to indicate a specific SetID for the Business Unit. The SetID for Public Defender Org Codes will be 55000.
Tree Levels
Effective Dates
Standard Detail Trees
Dynamic Detail Trees
Node-Oriented Trees
Summary Trees
Basic type of tree (aka summer trees).

Detail values shown in the levels farthest to the right. The nodes (to the left) group the detail.

Detail trees most often used for nVision reporting from the General Ledger.
Standard Detail Trees
Detail values are determined by matching the node name with a field on the detail value table.

In this example, the tree is looking up employee IDs based on their organizational structure.
Dynamic Detail Trees
The Node-Oriented Trees (AKA winter trees) do not use the detail values. The system uses this type of tree for special purposes. E.g. the HR system uses the Departmental Security tree give access to information only about employees in their departments.

Note: "Departments" in PeopleSoft are representative of the Organization. We will be using the Department ChartField as the Org Code.
Node-Oriented Trees
Generally used for GL reporting. An alternative grouping of the nodes without duplicating the entire structure of a detail tree. It is based on an existing detail tree.

Summary trees will be used for Commitment Control (budget checking) at the Appropriation and Allotment line. They can also be used for agency operating budget checking.
Summary Trees
Account ChartField
The Account ChartField will hold values for all Balance Sheet, Expenditure and Revenue Accounts.

Fields in the Account setup indicate whether what type of code it is. You can also indicate other characteristics of the code, such as whether the code is used for Budgetary Only, or a Control Account that can only be used in a Journal Entry.

Commitment Control will use a tree to summarize by Allotment Line.
Allotment Line Tree
Full transcript