Project Tree Structures

PeopleSoft Tree Manager supports business unit trees. SetIDs are not coupled with the project business unit or used as a key in Project Costing and its related activity and transaction tables. The SET_OVERRIDE field links the general ledger business unit to Project Costing. This streamlines the data structure without the loss of any features.

Project Costing delivers three tree structures. This table lists the key differences between these tree structures.

Structure	Node Table	Detail Table	Page Access from PeopleSoft Tree Manager
PROJECT_BU	PROJECT	None	PROJECT_GEN_01A page
PROJECTS_ALL	PROJECT	PROJ_ACTIVITY	PROJECT_GL page
PROJECT_GL	TREE_NODE_TBL	PROJECT	PROJECT_GL page

You can use project trees for:

• Row-level security.

• Reporting, particularly nVision reports.

• Analysis.

• Allocations.

• Report summarization options.

• Combination editing.

This table can serve as a reference when you decide which structure best meets your needs, based on your use of project trees:

Structure	Security	Tree API	Allocation	Report Summary Option	Project Level nVision Report	Activity Level nVision Report	Combo Editing	Tree Loader
PROJECT_BU	Yes	Yes	Yes	Yes	Yes	No	No	Yes
PROJECTS_ALL	No	No	Yes	No	Yes	Yes	Yes	Yes
PROJECT_GL	No	No	Yes	No	Yes	No	Yes	Yes

The nVision reports use project trees extensively. The PROJECT_BU tree is a node-oriented (winter) tree, so there are no details. The PROJECTS_ALL tree (which is a dynamic detail tree) has ACTIVITY as details, and consequently it is the best choice for nVision reports to nPlode to the activity level.

Because the SET_OVERRIDE field is used as the link in the PROJECT_FS record and because the project ID is unique across the system, projects can be added from different business units to a single tree based on the PROJECTS_ALL tree structure.

When you create a new project from PeopleSoft Tree Manager for a PROJECTS_ALL tree, the project business unit is the same as the SetID of the tree. (This is similar to the functionality that exists in the PROJECT_GL page.) Existing projects, however, can be added from different business units as nodes if the set override of those projects matches the SetID of the tree.

For example, if BUILDING E is a project within business unit US003, BUILDING F is a project within business unit US004, and both projects have the same set override of SHARE, then you can add both projects to an existing PROJECTS_ALL tree with the SetID of SHARE (even though they are from different business units).

Note:

The PROJECT tree structure is no longer used. All previous and existing PROJECT functionality is included in the PROJECT_BU tree structure.