Determining System Default Values

Most of the page-level defaults in the PeopleSoft HCM system are based on the primary permission list as opposed to business unit. Business unit defaulting generally only occurs on components that are driven by the business unit or that use EmplID as a high-level key.

This table lists the four most common scenarios in which the system must determine which default values to use, either the defaults that you defined on the Business Unit Options Defaults component or on the Org Defaults by Permission List component:

On the Component	How the System Determines Defaults
Select a business unit.	The system enters the default values from the Business Unit Default Options component.
Select an EmplID value, but no business unit value.	The system determines the person's business unit by checking the person's JOB record for that EmplID/ERN combination and then enters the default values from the Business Unit Default Options component.
The component does not have either the Business Unit or EmplID fields.	The system enters the default values from the Org Defaults by Permission List component.
The component uses a set ID without an associated business unit or EmplID value. (This is the situation on most setup and control components, such as the Location and Department components.)	The system enters the default values from the Org Defaults by Permission List component.

WARNING:

The paradigm above isn't strictly followed in the system and should be used as a guideline only. Actual defaulting at the page level is governed primarily by page functionality.

Note:

Some degree of flexibility has been incorporated for exceptions to those pages that don't fall into either of these categories.

For more information, see product documentation for PeopleTools: Security Administration and PeopleTools: Data Management.