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:
Design the resource organization structure.
Select the organizational unit.
Determine the organizational unit field and record.
Determine if an existing tree can serve as the organizational unit tree, or create a new organizational unit tree.
(Optional) Provide access to the tree across business units.
Additional setup steps are required if you use an organizational unit tree other than department.
If you use departments as the organizational unit, and if you are using PeopleSoft Resource Management's integration with PeopleSoft HCM, you can use the existing HCM department tree. Use the TreeMover Application Engine process (TREEMOVER) to copy the existing PeopleSoft HCM department tree to the Financials database if it does not already exist.
In the Financials database, you can modify the tree to support the resource management operation.
Important! If you copy an existing tree from the HCM database to the Financials database to use as the organizational unit tree, the Department organizational unit tree in PeopleSoft Resource Management is not automatically updated each time that a value changes in the PeopleSoft HCM tree. For example, if a department is added or removed from the PeopleSoft HCM department tree, you must update the tree in PeopleSoft Resource Management.
Periodically complete these steps using the TreeMover process to update the organizational unit tree in PeopleSoft Resource Management with changes from the corresponding tree in PeopleSoft HCM:
Export the tree from the HCM database.
Import the tree in the Financials database.
If you do not use the PeopleSoft HCM department tree as the PeopleSoft Resource Management organizational unit tree, you can:
Create a tree that is not based on a tree in PeopleSoft HCM.
Use another tree from PeopleSoft HCM.
In this case, create and maintain the tree as described above for the PeopleSoft HCM department tree using the TreeMover process, and then manually update the tree as necessary.
You can use an existing tree from the HCM database by using the TreeMover process to move the tree into the Financials database. You can also define a new tree. To decide whether to use an existing tree or create a new one, determine whether the existing tree hierarchically displays all of the data that you need to support the resource management operation. Create a new tree if the existing tree is significantly different from the resource hierarchy.
Use one of the fields on the Job record (JOB) to map organizational units to resources. The Job record contains the PeopleSoft HCM data for department, location, job code, and a variety of other attributes for every employee in the organization.
You can select these fields in the Job record as the organizational unit field:
Department (DEPTID)
Job Code (JOBCODE)
Location Code (LOCATION)
Supervisor ID (SUPERVISOR_ID)
If none of the fields in the Job record can map organizational units to resources, you can use any record and field to organize the resources.
Note: Every resource that you track in PeopleSoft Resource Management must belong to an organizational unit that appears in the organizational tree. For example, if the Job Code field is the organizational unit, you must identify a job code for every resource.
Additional Setup Steps for Non-department Organizational Unit Trees
Complete these additional setup steps if you use an organizational unit other than department:
Identify or create a valid employee-organization record.
Modify the organization structure definition on the Installation Options - Resource Management page.
Modify the organizational unit field name label.
Modify the Structured Query Language (SQL) definition called Organizational Tree, Organizational Unit Description (RS_ORGTREE_DEPT_SQL) if the organizational unit record is not keyed by SetID.
Complete these additional setup steps if the non-department organizational unit record does not use the Description field (DESCR) to store the organizational unit's title or name:
Modify the field name that stores the organizational unit description in the Organizational Tree, Organizational Unit Description SQL definition and the Organizational Unit Description SQL definition (RS_ORGDTL_DESCR_SQL).
Modify the PeopleCode with the organizational unit field.