Search Results psb_pay_element_options




Overview
Explore in AI Chat

Overview

The PSB_PAY_ELEMENT_OPTIONS table is a core data structure within the Oracle E-Business Suite (EBS) Public Sector Budgeting (PSB) module, specifically in versions 12.1.1 and 12.2.2. As indicated by its description, it stores the distinct options available for a given pay element. A pay element typically represents a component of compensation, such as a specific type of allowance, differential, or bonus. This table allows for the definition of multiple configurable variants or choices (options) associated with a single pay element, enabling granular budgeting and assignment. It is critical to note that the PSB module is marked as obsolete in the provided metadata, indicating it may be in a state of maintenance or sunset, with potential migration paths to newer Oracle solutions. The table's primary key is PAY_ELEMENT_OPTION_ID, which uniquely identifies each option record.

Key Information Stored

The central column in this table is the PAY_ELEMENT_OPTION_ID, a unique system-generated identifier serving as the primary key. While the full column list is not detailed in the excerpt, the foreign key relationships imply the existence of several other critical columns. The PAY_ELEMENT_ID column is a foreign key linking the option back to its parent definition in the PSB_PAY_ELEMENTS table. Additional columns likely define the specific characteristics of the option, which could include descriptive fields (e.g., NAME, DESCRIPTION), financial or rate modifiers, effective dates (EFFECTIVE_START_DATE, EFFECTIVE_END_DATE), and flags controlling its applicability and calculation logic within the budgeting process.

Common Use Cases and Queries

The primary use case for this table is to support the configuration and assignment of detailed compensation components during position budgeting. For instance, a "Vehicle Allowance" pay element (in PSB_PAY_ELEMENTS) might have options defined in this table for "Standard Mileage," "Car Allowance," and "No Allowance." Budget analysts can then assign the appropriate option to specific positions. A common reporting query would join this table to its parent to list all available options. A typical SQL pattern to find all options for a specific pay element would be:

  • SELECT peo.* FROM psb_pay_element_options peo, psb_pay_elements pe WHERE peo.pay_element_id = pe.pay_element_id AND pe.element_name = '<Element_Name>';

Another critical query involves validating assignments by joining to the PSB_POSITION_ASSIGNMENTS table to see which positions use a particular pay element option.

Related Objects

Based on the documented foreign key relationships, PSB_PAY_ELEMENT_OPTIONS is centrally connected to several other PSB tables:

  • PSB_PAY_ELEMENTS: The parent table. Joined via PSB_PAY_ELEMENT_OPTIONS.PAY_ELEMENT_ID to PSB_PAY_ELEMENTS (key column not specified, but likely PAY_ELEMENT_ID). This defines the base pay element for which the option exists.
  • PSB_PAY_ELEMENT_RATES: A child table. Joined via PSB_PAY_ELEMENT_RATES.PAY_ELEMENT_OPTION_ID to PSB_PAY_ELEMENT_OPTIONS.PAY_ELEMENT_OPTION_ID. This stores specific rate or amount details associated with each pay element option.
  • PSB_POSITION_ASSIGNMENTS: A referencing table. Joined via PSB_POSITION_ASSIGNMENTS.PAY_ELEMENT_OPTION_ID to PSB_PAY_ELEMENT_OPTIONS.PAY_ELEMENT_OPTION_ID. This indicates which budgeted positions are assigned a specific pay element option.