Understanding Organizational Units

During implementation you must define your organizational units and insert them into a hierarchical structure known as a tree by using the PeopleSoft Tree Manager. For example, an organization can consist of 12 different companies grouped into three lines of business or subsidiaries, each represented by a business unit, along with a separate corporate business unit. All of these units—12 companies in three business units and a corporate business unit—roll up into the organization at the top of the hierarchy. Between the tree manager and your business unit structure, PeopleSoft Resource Management provides a powerful and flexible mechanism for defining reporting parameters.

Many organizations are composed of departments that fit hierarchically into a treelike structure. However, with PeopleSoft Resource Management you are not required to base your organizational structure on departments. For example, your structure can be based on geographical locations or job codes.

This table contains the primary areas in the application that depend on the organizational unit. Based on this information, and knowledge of your organization's business practices, choose the most appropriate organizational unit such as department, job code, location, or another unit.

Application Feature	Description
Owning organizations	The owning organization owns a service order, which is most likely the organization that sold the business to the customer and is responsible for ensuring that the requested services are delivered. The combination of owning business unit and owning organization are specified on each service order. Resources are tracked by organizational units. Resource Matching uses owning organizations to match resources with service orders. Users can search for resources in specific owning organizations to fulfill orders.
Resource groups	Resource groups are collections of resources grouped by organizational unit or supervisor ID. Resource groups can be defined and saved by a user, and serve two main purposes. They can be used to selectively limit, broaden, or redirect the search for resources to different parts of the organization. They also enable a resource manager to define the group of resources who appear on the Staffing Workbench - Manage Utilization page.
Reports	The Chart Resource Schedules, Scheduled Utilization, Unassigned Resources, Assignments Ending, Assignment Listing, and Average Staffing Time reports enable a user to indicate which organizational unit to analyze. For example, the Scheduled Utilization interactive report calculates resource utilization for the specified organizational unit, and has the capability to drill down to the utilization of each individual in the unit.

Application Feature

Description

Owning organizations

The owning organization owns a service order, which is most likely the organization that sold the business to the customer and is responsible for ensuring that the requested services are delivered. The combination of owning business unit and owning organization are specified on each service order.

Resources are tracked by organizational units. Resource Matching uses owning organizations to match resources with service orders. Users can search for resources in specific owning organizations to fulfill orders.

Resource groups

Resource groups are collections of resources grouped by organizational unit or supervisor ID. Resource groups can be defined and saved by a user, and serve two main purposes. They can be used to selectively limit, broaden, or redirect the search for resources to different parts of the organization. They also enable a resource manager to define the group of resources who appear on the Staffing Workbench - Manage Utilization page.

Reports

The Chart Resource Schedules, Scheduled Utilization, Unassigned Resources, Assignments Ending, Assignment Listing, and Average Staffing Time reports enable a user to indicate which organizational unit to analyze. For example, the Scheduled Utilization interactive report calculates resource utilization for the specified organizational unit, and has the capability to drill down to the utilization of each individual in the unit.

After you identify the organizational unit, identify the field and record associated with that unit. This field is the organizational unit field. For example, if the organizational unit is Department, the organizational unit field is the Department ID field (DEPTID). The organizational unit record is the table that contains the valid values of the organizational unit field. For example, if the organizational unit field is DEPTID, the organizational unit record is the Departments table (DEPT_TBL).

Note: Every resource that PeopleSoft Resource Management tracks must belong to an organizational unit that is included on the organizational tree.