Results for “psb_pay_elements”

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

Overview

PSB_PAY_ELEMENTS is a pay element definition table belonging to the Public Sector Budgeting (PSB) module of Oracle E-Business Suite. The PSB module has been classified as obsolete in the ETRM documentation, and this table is listed with the implementation note "Not implemented in this database." It should therefore be treated as a legacy or dormant object rather than an active transactional table in the 12.1.1 / 12.2.2 environments covered by the reference metadata.

Functionally, PSB_PAY_ELEMENTS stores the definitions of pay elements used during public sector budgeting and position cost modelling. Each row describes a named element — for example a salary component, allowance, or benefit — together with the calculation basis, formula reference, and validity dates required to project the cost of positions and assignments.

The documented physical schema for 12.1.1 specifies the owner as PSB, with 40 columns. From a Data Vault modelling perspective, the heuristic classification is hub-leaning. The single-column primary key PAY_ELEMENT_ID is a surrogate identifier, and the table is heavily referenced by downstream PSB child tables, which is consistent with a hub entity acting as the stable business key anchor for related satellites and links.

Key Information Stored

The table separates identity, descriptive, and calculation-control attributes. The most significant columns are:

• PAY_ELEMENT_ID — the surrogate primary key defined by the PSB_PAY_ELEMENTS_PK constraint; also the sole business-key candidate via the unique index PSB_PAY_ELEMENTS_U1.
• NAME and DESCRIPTION — the piece of human-readable identification for the pay element.
• BUSINESS_GROUP_ID — the business group / operating unit context for the definition.
• DATA_EXTRACT_ID — foreign key to PSB_DATA_EXTRACTS, linking the element to the extracted HR or payroll dataset it was derived from.
• FORMULA_ID — foreign key to PSB_FORMULAS, identifying the calculation formula applied to the element.
• ELEMENT_VALUE_TYPE, MAX_ELEMENT_VALUE_TYPE, and MAX_ELEMENT_VALUE — control how the element value is derived and capped.
• PAY_BASIS and PERIOD_TYPE / PROCESS_PERIOD_TYPE — define the pay frequency and processing cadence for cost projection.
• OVERWRITE_FLAG, REQUIRED_FLAG, FOLLOW_SALARY, SALARY_FLAG, and SALARY_TYPE — behavioural flags governing editability, mandatory entry, and salary linkage.
• START_DATE and END_DATE — the effective dating window for the element definition.
• HR_ELEMENT_TYPE_ID — reference to the corresponding Oracle HR element type.
• BUDGET_SET_ID — ties the definition to a specific budget set.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and the ATTRIBUTE1–10 / CONTEXT descriptive flexfield.

Common Use Cases and Queries

Because the module is obsolete and the table is not implemented in the reference database, queries are typically limited to historical analysis, migration assessment, or impact analysis before retirement. A definition lookup by identifier follows the standard pattern:

• SELECT pay_element_id, name, element_value_type, formula_id, pay_basis FROM psb.psb_pay_elements WHERE pay_element_id = :id;
• Extracting all elements for a business group with effective-date filtering: ... WHERE business_group_id = :bg AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);
• Joining to PSB_FORMULAS to review the calculation logic attached to each element: ... FROM psb_pay_elements e, psb_formulas f WHERE e.formula_id = f.formula_id;
• Counting dependent child rows to gauge the blast radius of any data cleanup, using the foreign keys listed below.

Reporting use cases centre on reconciling budgeted position costs back to element definitions and confirming which elements were driven by a formula versus a fixed rate.

Related Objects

PSB_PAY_ELEMENTS sits at the centre of a hub-and-child network. It references:

• PSB_FORMULAS via FORMULA_ID — the calculation definition for the element.
• PSB_DATA_EXTRACTS via DATA_EXTRACT_ID — the source extract feeding the element.

Conversely, the following tables reference PSB_PAY_ELEMENTS through PAY_ELEMENT_ID:

• PSB_DEFAULT_ASSIGNMENTS — default element assignments.
• PSB_ELEMENT_POS_SET_GROUPS — position set group mappings.
• PSB_PARAMETER_FORMULAS and PSB_CONSTRAINT_FORMULAS — formula parameterisation and constraint logic.
• PSB_PAY_ELEMENT_OPTIONS and PSB_PAY_ELEMENT_RATES — element options and rate schedules.
• PSB_POSITION_ASSIGNMENTS and PSB_POSITION_COSTS — position cost projection.
• PSB_WS_ELEMENT_LINES and PSB_WS_LINE_BALANCES_I — worksheet element lines and balances.

These relationships confirm the hub-leaning classification and illustrate why any retirement or migration of PSB must account for the full dependent set before PSB_PAY_ELEMENTS can be dropped.