Results for “pay_element_option_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PSBFV_PAY_ELEMENT_RATES is a read-only reporting view within the Oracle E-Business Suite Public Sector Budgeting (PSB) module. The module is documented as obsolete in ETRM 12.1.1 and 12.2.2, meaning the underlying functionality is retained primarily for historical reporting and data migration rather than active transaction processing. The view exposes pay element rate definitions — the maximum, mid, and minimum values assigned to a pay element option for a given effective date range — in a denormalized, user-friendly form suitable for budgeting, salary modeling, and pay structure analysis.

The view joins three PSB tables and applies Oracle's FND (_LA) attribute tags on two descriptive columns, allowing localization of lookup meanings at the report layer. All three source tables are queried with the WITH READ ONLY clause, which prohibits DML through the view and signals that it is intended purely for query access. The mid_value column, which is the basis of this search, represents the midpoint rate of the pay element option and is a typical anchor for salary range analysis.

Underlying Base Objects

Although ETRM documents no referenced base objects for this view in the 12.2.2 metadata, the view text identifies three PSB tables explicitly:

• PSB_PAY_ELEMENTS (PE) — the parent pay element definition, supplying the element name joined via PAY_ELEMENT_ID.
• PSB_PAY_ELEMENT_OPTIONS (PEO) — option-level detail for a pay element, joined via PAY_ELEMENT_OPTION_ID using an outer join (+), so rates persist even when no option name is defined.
• PSB_PAY_ELEMENT_RATES (PER) — the driving table holding effective-dated rate records, including maximum, mid, and minimum values and currency.

The one-to-many relationship between options and rates produces multiple rows per element/option combination across effective dates.

Key Columns

• PAY_ELEMENT_NAME / PAY_ELEMENT_OPTION_NAME — descriptive identifiers from PSB_PAY_ELEMENTS and PSB_PAY_ELEMENT_OPTIONS.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — validity window of the rate record; essential for date-effective reporting.
• ELEMENT_VALUE / ELEMENT_VALUE_TYPE — the value assigned to the element and its type (exposed via FND_LOOKUPS using lookup type PSB_ELEMENT_VALUE_TYPE).
• MID_VALUE — the midpoint of the pay range; commonly used as the comparator against an employee's current salary for range penetration or compa-ratio analysis.
• MINIMUM_VALUE / MAXIMUM_VALUE — lower and upper bounds of the range.
• CURRENCY_CODE — the currency in which rate values are expressed.
• PAY_BASIS — the basis on which the pay element is calculated (FND lookup PSB_PAY_BASIS).
• PAY_ELEMENT_RATE_ID, PAY_ELEMENT_ID, PAY_ELEMENT_OPTION_ID, WORKSHEET_ID — keys linking back to PSB entities and budget worksheets.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard audit columns.

Common Use Cases and Queries

Typical uses include validating pay range definitions, comparing employee salaries against midpoints, and migrating PSB rate data into downstream systems. Because the module is obsolete, these queries are most often run for historical reconciliation.

Example: current mid-values by element and option

SELECT pay_element_name, pay_element_option_name, mid_value, currency_code
FROM psbfv_pay_element_rates
WHERE SYSDATE BETWEEN start_effective_date AND NVL(end_effective_date, SYSDATE)
ORDER BY pay_element_name, mid_value;

Example: range spread and midpoint deviation

SELECT pay_element_name, mid_value, minimum_value, maximum_value,
ROUND(mid_value - minimum_value, 2) AS lower_spread
FROM psbfv_pay_element_rates
WHERE mid_value IS NOT NULL;

Because PAY_ELEMENT_OPTION_ID is outer-joined, consumers should not assume an option name is always present; use NVL or filter accordingly when the option name is required for grouping.