Using Default Hierarchies

This chapter discusses how to:

• Understanding transaction defaults.

• Understand service requester defaults.

• Understand service coordinator defaults.

• Define the region hierarchy.

Understanding PeopleSoft Services Procurement Default Hierarchy

PeopleSoft Services Procurement enables you to setup several default hierarchy structures to use throughout your transaction processing. By setting up defaults, data entry is more consistent, saves time, and cuts down on redundancy and user error. Default values enable an Enterprise to pre-define key values that automatically default onto requisitions and work orders.

The most common defaults for requisitions and work orders come from the requester or service coordinator user defaults or from the service type and the business unit. When requesters or service coordinators create requisitions or work orders, the system first determines whether there is default information available for requester, then the service coordinator, then the service type, in that order respectively. If there are no default values defined at the service type level, the system then uses defaults that are defined at the business unit level.

PeopleSoft Services Procurement provides default capability for those values that are relatively static in nature (values that remain the same in everyday operations and would become repetitive to enter for every transaction). For example, if you set up your ChartField defaults with the most appropriate values for your service request, you have little need to drill down to the requisition's distribution level to enter any values. The ChartField values at that level are set by default.

Note. Although it is possible to establish several defaults for your requisition and work orders, you can override most values at the requisition and work order component levels.

Understanding Transaction Defaults

This table details the levels in the transaction default hierarchy from which the selected transaction values can appear by default. The possible default hierarchy levels listed for each transaction field value begin with the more-specific default and end with the less-specific default.

The default values listed default onto requisitions, work orders, timesheets, and progress logs.

Requisition Defaults

The following table lists values that default onto requisitions.

See Creating and Managing Requisitions.

Sourcing Defaults

The following table list values that default onto sourcing pages.

See Managing Requisition Sourcing.

Work Order Defaults

The following tables lists values that default onto work orders.

See Managing Work Orders.

Note. If you create a work order that is linked to a requisition, many of the values that automatically default onto the requisition will also default onto the linked work order.

This table represents default values for work orders that are not lined to requisitions and are created by the service coordinator.

This table represents default values for work orders that are not lined to requisitions and are created by the requester.

Understanding Service Requester Defaults

This section discusses how to define service requester defaults.

Service Requester Defaults

Use the Service Requester Defaults page to simplify the requisition and work order data entry process for requesters. When you define service requester default values, requesters can use those values when creating multiple requisitions and work orders. This streamlines data entry for each requester, because default information appears on requisitions and work orders automatically. You can then authorize established purchasing users to enter and process requisitions for all or specific requesters.

Service requester default values include, but are not limited to the following fields:

• Project Business Unit

• Project

• Service Type

• Service (Project Role)

• Service Coordinator/Team

• Time Approver

• Invoice Approver

• Allow Time/Expense Overage %

• Requisition Notification Method

• Work Order Alerts

• Expense Approver

In addition, the following values are defaulted from the requesters Procurement User Preferences

• Location

• Ship To

See Also

Setting Up Service Requester Defaults

Understanding Service Coordinator Defaults

This section discusses how to define service coordinator defaults.

Service Coordinator Defaults

Use the Service Coordinator Defaults page to simplify the work order data entry process for service coordinators.

Service coordinator default values include, but are not limited to the following fields:

• Project Business Unit

• Project

• Service Type

• Service (Project Role)

• Time Approver

• Invoice Approver

• Authorized to Delegate

• Authorized to Change Sourcing Rules

• Alert Notification Method

• Work Order Alerts

• Expense Approver

In addition, the following values are defaulted from the service coordinators Procurement User Preferences

• Location

• Ship To

See Also

Setting Up Service Coordinator Defaults

Defining the Region Hierarchy

Use the region hierarchy to determine the best suppliers to source the requisition request. Use the Region Codes and Tree Manager pages to build the region default structure and associate locations to the regions.

Once you establish the region hierarchy, use it to define rates and valid suppliers for sourcing.

The location specified on a requisition or work order is used to determine the related region for identification of associated rates.

Note. If the Use Region Tree Structure option is not selected in the Services Procurement Installation Options, the Locations by Region page is used instead of the Region Tree to associate locations to regions for purposes of determining rates.

See Also

Building the Region Hierarchy