Non-Department Organizational Unit Trees

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.