Results for “psb_ws_element_lines_u1”

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

Overview

PSB.PSB_WS_ELEMENT_LINES is a transactional detail table within the Oracle E-Business Suite Public Sector / Human Resources position budgeting and workforce costing model. It stores position cost by pay elements; for a given position, costs are recorded for each element and currency combination. The table is owned by the PSB schema, holds a VALID status in the ETRM dictionary, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, consistent with a transaction-oriented data table. Its FND Design Data reference is PSB.PSB_WS_ELEMENT_LINES.

Functionally, the object links budget positions to the pay elements that drive their costing, accumulating proposed element-level amounts that can be staged, distributed across element sets, and attributed to service packages and budget years. Because it carries both business relationships (to positions, pay elements, and element sets) and descriptive costing attributes, the heuristic Data Vault classification mined from its foreign-key structure is a link table — a modeling suggestion that reflects its role as an associative record connecting position lines, pay elements, element sets, and service packages rather than a standalone hub or a pure descriptive satellite.

Key Information Stored

The table contains 18 documented columns. The most significant are summarised below, distinguishing the surrogate primary key from business-key candidates.

• ELEMENT_LINE_ID (NUMBER(20)) — the surrogate primary key, enforced by the unique index PSB_ELEMENT_LINES_PK and by the unique index PSB_WS_ELEMENT_LINES_U1. This is the column behind the search term "psb_ws_element_lines_u1".
• POSITION_LINE_ID (NUMBER(20)) — the position to which the element line is assigned; the principal business join to PSB_WS_POSITION_LINES, supported by non-unique index PSB_WS_ELEMENT_LINES_N1.
• PAY_ELEMENT_ID (NUMBER(20)) — the pay element for which the line is created; the primary costing dimension, indexed by PSB_WS_ELEMENT_LINES_N2.
• BUDGET_YEAR_ID (NUMBER(15)) — the budget year against which the cost is assigned; part of composite index N2.
• CURRENCY_CODE (VARCHAR2(10)) — currency of the recorded amount, since costs are held per element and currency.
• ELEMENT_COST (NUMBER) — the pay amount proposed for the position for this element.
• ELEMENT_SET_ID (NUMBER(15)) — identifies the set of account lines to which this element line is distributed; indexed by PSB_WS_ELEMENT_LINES_N3 and referencing PAY_ELEMENT_SETS.
• SERVICE_PACKAGE_ID (NUMBER) — the service package associated with the line.
• STAGE_SET_ID, START_STAGE_SEQ, CURRENT_STAGE_SEQ, END_STAGE_SEQ — staging attributes that track the set and sequence span of the element line through its processing stages.
• FUNCTIONAL_TRANSACTION (VARCHAR2) — indicates a functional currency transaction.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE, providing audit lineage.

Common Use Cases and Queries

Typical reporting retrieves the element-level cost build-up for a position, aggregates cost by pay element or currency, or traces distribution into element sets and service packages.

• Position cost breakdown by element and currency, joining PSB_WS_ELEMENT_LINES to PSB_WS_POSITION_LINES on POSITION_LINE_ID.
• Budget-year cost rollups grouped by PAY_ELEMENT_ID and BUDGET_YEAR_ID.
• Element-set distribution analysis using ELEMENT_SET_ID.
• Staging and sequencing review using STAGE_SET_ID and the stage sequence columns.

A representative pattern is: SELECT l.position_line_id, l.pay_element_id, l.currency_code, SUM(l.element_cost) FROM psb.psb_ws_element_lines l WHERE l.budget_year_id = :year GROUP BY l.position_line_id, l.pay_element_id, l.currency_code; The unique index PSB_WS_ELEMENT_LINES_U1 on ELEMENT_LINE_ID supports single-row lookups, while the non-unique indexes N1–N3 support the joins and filters above.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign-key relationships and indexes:

• PSB_WS_POSITION_LINES — joined via POSITION_LINE_ID; the parent position record.
• PSB_PAY_ELEMENTS — joined via PAY_ELEMENT_ID; the pay element definition.
• PAY_ELEMENT_SETS — joined via ELEMENT_SET_ID; defines the account-line set for distribution.
• PSB_SERVICE_PACKAGES — joined via SERVICE_PACKAGE_ID; the associated service package.
• The indexes PSB_WS_ELEMENT_LINES_U1, _N1, _N2, and _N3, which enforce uniqueness on ELEMENT_LINE_ID and accelerate access on position, element, budget year, stage set, and element set columns.

Together these relationships establish PSB_WS_ELEMENT_LINES as the associative costing detail between positions, pay elements, element sets, and service packages within the PSB workforce and position budgeting model.