Understanding the Organizational Unit Tree Structure

Among the first decisions that you make when implementing PeopleSoft Resource Management is the determination of how to represent the organizational structure in the application. The organizational unit that you use reflects the organization's structure.

Your resource pool structure can be an exact mirror of how you define the organizational unit structure, or it can be more flexible, enabling you to organize by skill set or by "virtual teams."

You use the organizational unit tree to show that structure and:

  • To select a service order owning organization.

  • To define resource groups that you can use to selectively search for resources in different parts of the organization.

  • To define the groups of resources who appear on the Staffing Workbench - Manage Utilization page.

  • To indicate which organizational unit to analyze on reports for scheduled utilization, unassigned resources, assignments ending, assignment listing, resource schedules, and average staffing time.

Select an organizational unit that contains categories for all resources that you manage using PeopleSoft Resource Management. Then design the company's resource structure on the organizational unit tree from the top down using the simple, graphical PeopleSoft Tree Manager. For example, the business structure may include a set of departments, regions, or business functions. The organizational unit tree illustrates the hierarchy.

PeopleSoft Resource Management permits the use of an existing PeopleSoft HCM tree as the organizational unit tree if you integrate with PeopleSoft Human Capital Management (PeopleSoft HCM). Alternatively, you can create a new organizational unit tree that reflects only the units within the organization that contain resources that you manage with PeopleSoft Resource Management.

The steps to select or create a new organizational unit tree are:

  1. Design the resource organization structure.

  2. Select the organizational unit.

  3. Determine the organizational unit field and record.

  4. Determine if an existing tree can serve as the organizational unit tree, or create a new organizational unit tree.

  5. (Optional) Provide access to the tree across business units.

Additional setup steps are required if you use an organizational unit tree other than department.