Search Results salary_type_meaning

Overview

APPS.PSB_PAY_ELEMENTS_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Public Sector Budgeting (PSB) product family, which supports position, salary, and budget modeling for public-sector and government implementations. The view is registered under FND Design Data as PSB.PSB_PAY_ELEMENTS_V and is classified as a "supplementary view used to simplify forms coding," meaning it exists primarily to support Oracle Forms-based user interfaces rather than as a public integration interface.

The view presents configuration rows for pay elements used in budgeting and salary calculations: element value types, processing types, period types, salary types, formula bindings, and related descriptive flexfield attributes. Oracle explicitly warns that this view is not intended for ad-hoc query or modification and that its structure may change dramatically in a subsequent minor or major release. It should therefore be treated as an internal object that technically-savvy consultants may inspect, but not as a stable API.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for PSB_PAY_ELEMENTS_V, which is consistent with a form-supporting view whose definition joins or selects from underlying PSB transaction tables such as those holding pay elements, budget sets, and data extracts. The columns exposed—PAY_ELEMENT_ID, BUSINESS_GROUP_ID, DATA_EXTRACT_ID, BUDGET_SET_ID, and HR_ELEMENT_TYPE_ID—indicate the view correlates PSB budgeting data with HR element types from the Oracle HRMS pay element model. Without documented base objects, the authoritative source of truth remains the view's own live definition in the database (ALL_VIEWS.TEXT or DBA_VIEWS), which should be inspected with DBMS_METADATA.GET_DDL rather than assumed from documentation.

Key Columns

• PAY_ELEMENT_ID, BUSINESS_GROUP_ID — primary key of the pay element and its owning business group.
• DATA_EXTRACT_ID / DATA_EXTRACT_NAME, BUDGET_SET_ID / BUDGET_SET_NAME — context of the extract and budget set to which the element belongs.
• NAME, DESCRIPTION — element identifier and description.
• ELEMENT_VALUE_TYPE / ELEMENT_VALUE_TYPE_MEANING — value type of the element (for example amount or percentage), with its decoded meaning.
• FORMULA_ID — the formula attached to the element for calculation.
• OVERWRITE_FLAG, REQUIRED_FLAG, FOLLOW_SALARY, SALARY_FLAG, OPTION_FLAG — behavioral control flags.
• PAY_BASIS, SALARY_TYPE / SALARY_TYPE_MEANING — salary and pay basis classifications.
• PROCESSING_TYPE, PERIOD_TYPE, PROCESS_PERIOD_TYPE and their decoded _MEANING columns — processing and period semantics.
• MAX_ELEMENT_VALUE_TYPE / MAX_ELEMENT_VALUE_TYPE_MEANING and MAX_ELEMENT_VALUE — the user's search term maps here: the value type used to cap the element (for example absolute amount or percentage) and the cap value itself.
• START_DATE, END_DATE — effective dating of the element configuration.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE10 — descriptive flexfield (DFF) segments.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical use is diagnostic: confirming how a pay element's maximum cap is configured during budget or salary validation. A representative query is:

SELECT pay_element_id,
       name,
       element_value_type_meaning,
       max_element_value_type,
       max_element_value_type_meaning,
       max_element_value,
       start_date,
       end_date
FROM   apps.psb_pay_elements_v
WHERE  business_group_id = :p_business_group_id
AND    TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);

Because the view is supplementary and unsupported, production code should not join to it or reference it in interfaces; instead, identify the underlying PSB base tables and use documented APIs or extraction tables for integration. Any query should be executed with read-only privileges, and results should be re-validated after patching or upgrading between 12.1.1 and 12.2.2, since Oracle reserves the right to restructure this view.