Project Hierarchies

You can create a project hierarchy by associating a project with a parent project using the Parent Project field, in the same way that you create regionClosedA level of hierarchy used in PSA to which other objects belong such as resources, opportunities and projects., practiceClosedA level of hierarchy used in PSA to which other objects belong such as resources, opportunities and projects., and groupClosedA level of hierarchy used in PSA to which other objects belong such as resources, opportunities and projects. (RPGClosedAbbreviation of region, practice, group.) hierarchies. Data from project business records can roll-upClosedTerm used to describe how a lower level figure or transaction is included in a higher level transaction or calculation. to the project's RPG and up the RPG hierarchy. The same data can also roll-up the projectClosedA collection of activities and related items to be managed over a defined time range, such as timecards, expenses, milestones and budgets. hierarchy.

Most projects do not have a parent project, so there is no hierarchy. In this case, the project stands alone. Business records for the project may affect the RPG actuals for the project's RPGs and RPG hierarchies. Business records for a project with no parent project only contribute to that project's actualsClosedTotals for a given time period. and not to any other project's actuals.

If a project has a parent project, there is a project hierarchy. This is similar to a RPG hierarchy except that you can create more than one top-level parent project. A top-level parent project, which has the Master Project checkbox selected, is known as the master project. All child projects roll-up to their parent project in the hierarchy. A parent project therefore includes its own amounts and times plus the amounts and times from all child projects down the hierarchy. The master project includes its own amounts and times plus those from all the child projects in that project hierarchy. For information about creating a project hierarchy, see Creating a Child Project and Project Hierarchy.

Scheduled Backlog

Scheduled backlog behaves in a similar way, rolling-up the RPG hierarchies of projects, but also rolling separately up the project hierarchy if one exists.

For instance, if project 1 in the US East region has parent project 2 in the US West region, and both regions have the same parent region United States, the following happens regardless of project hierarchies:

The following happens due to the project hierarchy:

Why Use a Project Hierarchy?

You can use project hierarchies to analyze a project's roll-ups as a whole and break up projects based on different attributes.

For example: