Defining the Organization by Using Trees

This chapter provides an overview of the organizational unit tree structure and discusses how to:

• Create and share an organizational unit tree.

• Configure nondepartment organizational units.

See Also

PeopleTools PeopleBook: PeopleSoft Tree Manager

Understanding the Organizational Unit Tree Structure

Among the first decisions that you make when implementing 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 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.

Resource Management permits the use of an existing HRMS tree as the organizational unit tree if you integrate with PeopleSoft Human Resources Management (PeopleSoft HRMS). Alternatively, you can create a new organizational unit tree that reflects only the units within the organization that contain resources that you manage with 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 if you must create a new tree.

5. Create a new organizational unit tree.

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

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

See Also

Working with Resource Pools

Department Organizational Unit Trees

If you use departments as the organizational unit, and if you are using Resource Management's integration with PeopleSoft HRMS, you can use the existing PeopleSoft HRMS department tree. Use the TreeMover Application Engine process (TREEMOVER) to copy the existing HRMS department tree to the PeopleSoft Financials and Supply Chain Management (FSCM) database if it does not already exist.

In the FSCM database, you can modify the tree to support the resource management operation.

Important! If you copy an existing tree from the HRMS database to the FSCM database to use as the organizational unit tree, the Department organizational unit tree in Resource Management is not automatically updated each time that a value changes in the HRMS tree. For example, if a department is added or removed from the HRMS department tree, you must update the tree in 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 HRMS:

1. Export the tree from the HRMS database.

2. Import the tree in the FSCM database.

Nondepartment Organizational Unit Trees

If you do not use the HRMS department tree as the Resource Management organizational unit tree, you can:

• Create a tree that is not based on a tree in PeopleSoft HRMS.

• Use another tree from HRMS.

  In this case, create and maintain the tree as described above for the HRMS department tree using the TreeMover process, and then manually update the tree as necessary.

You can use an existing tree from the PeopleSoft HRMS database by using the TreeMover process to move the tree into the FSCM 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 data needed 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 HRMS data for department, location, job code, and a variety of other attributes for every employee in the organization. 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.

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)

Note. Every resource that you track in 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 Nondepartment 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 nondepartment 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.

Creating and Sharing the Organizational Unit Tree

This section discusses how to create the tree structure and define and share the tree.

Pages Used to Create and Share the Organizational Unit Tree

Creating the Tree Structure and Defining and Sharing the Tree

Follow these steps to create a new organizational tree:

1. Create the tree structure.

   The tree can be either a detail-value (summer) tree or a node-oriented (winter) tree. If the tree contains details, enter the organization unit field name as the Details field name. If the tree contains only nodes, enter the organization unit field name as the Nodes field name.

   You can select SetID Indirection as an additional key field to use the setID to share the organizational unit tree definition across business units.

2. Define the tree.

3. Specify the root node.

4. Insert the tree nodes that define the hierarchy of the tree.

5. Attach detail values as so-called leaves on the nodes for a detail-value (summer) tree.

6. Share the tree across business units.

   This step is necessary only if you use an organizational unit tree that is keyed by setID.

   Associate the organizational unit tree with the business units that require access to the tree for PeopleSoft Resource Management.

   To share the tree across business units, access the TableSet Control component and select a business unit value that uses the organizational unit tree. Access the TableSet Control - Tree page and enter the organizational unit tree name and tree setID in the Tree Controls grid.

   You do not need to attach the tree to the setID set control values for the organization—only to the business units that are affected by PeopleSoft Resource Management.

   Note. On the TableSet Control - Tree page, enter the setID before you look up the tree name. If you do not enter the setID first, only trees that are not keyed by a setID appear.

Configuring Nondepartment Organizational Units

This section discusses how to:

• Identify or create a valid Employee-Organization record.

• Modify the organization structure definition.

• Modify the organizational unit field name.

• Modify SQL definitions with the organizational unit field.

• Modify PeopleCode with the organizational unit field.

See Also

Setting Up Resource Management Installation Options

PeopleTools PeopleBook: PeopleSoft Application Designer

Page Used to Configure Nondepartment Organizational Units

Identifying or Creating a Valid Employee - Organization Record

The PeopleSoft system comes with the Employee-Organization record (RS_ORGEMPLBR_VW) to keep track of the organizational unit to which each resource belongs. The Employee-Organization record is a view of the Job record that identifies the department for every employee. The Job record is the PeopleSoft HRMS record that identifies the department, location, job code, and a variety of other attributes for every employee in the organization. If the organizational field is Department (DEPTID), you can use the Employee-Organization record as delivered.

If you cannot use the delivered Employee-Organization record, you must either modify the definition and SQL text of the Employee-Organization record, or you must use a different record. The Employee-Organization record does not need to be a view. The minimum requirements for a valid Employee-Organization record are:

• The record is keyed by the employee ID (EMPLID) of the resource.

• The record includes the resource’s organization unit in the appropriate organization unit field, such as Department or Location Code (LOCATION).

• (Optional) The record includes the setID of the resource’s organization unit in the Set Control field (SETCNTRLVALUE).

  This is required if the organizational unit record is keyed by setID, such as the Departments record (DEPT_TBL). Some organizational units, such as supervisor ID, may not have an organizational unit record that is keyed by setID.

• The record contains rows for all resources.

The Employee-Organization record can have more than one row per resource, provided that the correct row to use can be identified at any given time. You can use multiple rows per resource by using additional key fields in the record. Resource Management supports the use of the following additional key fields:

• Employee Record Number field (EMPL_RCD).

  If there are multiple rows in the Employee-Organization table for a given resource, each with a different employee record number, you use only the row with the employee record number that is defined for the resource in Resource Management.

• Effective Date (EFFDT).

  If there are multiple rows in the Employee-Organization table for a given resource, each with a different effective date, you typically use only the row that is current. The effective date companion status field—Employee Status (EMPL_STATUS)—is also supported. This field is used to indicate active or inactive employees.

• Effective Sequence Number (EFFSEQ).

  If there are multiple rows in the Employee-Organization table for a given resource, each with a different effective sequence number, you use only the row with the maximum effective sequence number. If effective dating is used, you use only the row with the maximum effective sequence number within the same effective date row.

The record must not contain any other key fields.

Modifying the Organization Structure Definition

If you change the organizational unit field, record, or tree, you must modify the values in the Organizational Structure definition on the Installation Options - Resource Management page.

This table lists the fields and delivered values in the Organizational Structure definition:

Modifying the Organizational Unit Field Name

Use PeopleSoft Application Designer to modify the Organization Field Name (ORG_FIELDNAME) if required. Change the Long Name field and the Short Name field of the label ID (ORG_LABEL) to reflect the new label (for example, Location and Loc).

Modifying SQL Definitions with the Organizational Unit Field

The Organizational Tree, Organizational Unit Description SQL definition (RS_ORGTREE_DEPT_SQL) joins the organizational unit record to the Employee-Organization record. The Organization Tree Detail SQL definition (RS_ORGDTL_DESCR_SQL) retrieves the organizational unit description.

Use PeopleSoft Application Designer to make these changes to the SQL definition if required:

• If the organizational unit record is not keyed by setID, remove the A.SETID = :4 portion of the Organizational Tree, Organizational Unit Description SQL definition.

  For example, if you select the Supervisor ID field as the organizational unit, remove A.SETID = :4 from the Organizational Tree, Organizational Unit Description SQL definition. The Supervisor ID field is not contained in a record that is also keyed by setID.

• If the Description field is not used to store the organizational unit’s title or name, modify the A.DESCR portion of the Organizational Tree, Organizational Unit Description SQL definition and the Organization Tree Detail SQL definition.

  For example, if the Supervisor ID field is selected as the organizational unit, manager names can be stored in the Name field (NAME) on the Personal Data record (PERSONAL_DATA). Therefore, change the value A.DESCR to the value A.NAME.

Modifying PeopleCode with the Organizational Unit Field

If the Description field is not used to store the organizational unit’s title or name, use PeopleSoft Application Designer to make these changes to the PeopleCode if required:

• Modify the RS_INSTALL_WRK.FIND_OBJECTS_PB.FieldChange PeopleCode program. Change the first parameter in the function call resolve_wildcard( ) from Field.DESCR to the field name that stores the organizational unit's title, description, or name.

• Modify the function ManageTree( ) function in the FUNCLIB_RS.TREE_NAME.FieldFormula PeopleCode program. Change the field name in this line of code—&NodeDescr = &DtlDescrRec.DESCR.Value;—from DESCR to the field name that stores organizational unit name values. For example, if the NAME field is used to store organizational unit names—because the organizational unit is Supervisor ID, the code is &NodeDescr = &DtlDescrRec.GetField(Field.NAME).value.