Concept: Project Hierarchies
Project hierarchies define the parent and child relationships within hierarchies and
categorize your projects.
Workday has 2 types of project hierarchies:
- Primary
- Optional
Primary project hierarchies pass their configurations onto their child hierarchies and
associated projects. Use these hierarchies to streamline project creation and to group
projects for roll-up reports.
You can use primary project hierarchies to:
- Group similar projects and child hierarchies for roll-up reporting.
- Make related projects more accessible.
- Configure resource plans for use on similar projects.
- Configure business process definitions, common settings, and project roles for similar projects.
Optional project hierarchies don't have configuration options for other hierarchies or
projects to inherit. Use optional hierarchies to add additional report categories for
more granularity in your roll-up reports.
All projects must belong to a primary project hierarchy and can belong to 1 or more
optional project hierarchies. Assign projects to hierarchies at the time of project
creation, or by adding and removing them from the hierarchy definitions. Don't assign a
project to more than 1 node in the hierarchy tree.
Hierarchy Considerations
- After you submit a hierarchy for approval, you can't change its type.
- Child project hierarchies must be the same type as their parent.
- Use custom business processes, including any specific project roles, for only 1 hierarchy.