Search Results stage_set_id




Overview
Explore in AI Chat

Overview

The PSB.PSB_WS_ELEMENT_LINES table is a core data structure within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Public Sector Budgeting (PSB) module. It serves as the detailed transactional repository for position-based labor costs, broken down by individual pay elements and currencies. Its primary role is to store the proposed or budgeted compensation costs associated with a specific position for a given budget year, enabling granular financial planning, analysis, and distribution of salary expenses across funding sources or projects. This table is integral to the workforce budgeting and position control processes within PSB.

Key Information Stored

The table's columns capture the essential dimensions and amounts of position cost allocation. The primary unique identifier is the ELEMENT_LINE_ID. Critical foreign key columns establish relationships to other master data: POSITION_LINE_ID links to the specific position, PAY_ELEMENT_ID identifies the compensation element (e.g., base salary, bonus), and BUDGET_YEAR_ID defines the fiscal period. The financial data is stored in ELEMENT_COST with its associated CURRENCY_CODE. For workflow and accounting distribution, key columns include ELEMENT_SET_ID (linking to distributed account lines), STAGE_SET_ID, and the stage sequence columns (START_STAGE_SEQ, CURRENT_STAGE_SEQ, END_STAGE_SEQ) which track the budget entry and approval progression. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also present for auditability.

Common Use Cases and Queries

This table is central to reporting and validating position budgets. Common use cases include generating detailed position cost reports by element, currency, and budget year; validating total position cost against funding allocations; and supporting audit trails for budget revisions. A typical query to retrieve all cost elements for a specific position line would leverage the foreign key relationship:

  • SELECT pel.pay_element_id, pel.element_cost, pel.currency_code, pel.budget_year_id FROM psb.psb_ws_element_lines pel WHERE pel.position_line_id = :p_position_line_id ORDER BY pel.budget_year_id, pel.pay_element_id;

Another common pattern is to aggregate total proposed costs by budget year and element set for a high-level view: SELECT budget_year_id, element_set_id, SUM(element_cost) total_cost FROM psb.psb_ws_element_lines GROUP BY budget_year_id, element_set_id; Analysts also frequently join this table to PSB_WS_POSITION_LINES and PSB_PAY_ELEMENTS to include descriptive information in reports.

Related Objects

PSB_WS_ELEMENT_LINES has defined dependencies within the PSB schema, primarily through its primary and foreign key constraints. The table's primary key, PSB_ELEMENT_LINES_PK, is on the ELEMENT_LINE_ID column. It references two key master tables via foreign keys:

  • PSB.PSB_WS_POSITION_LINES: The POSITION_LINE_ID column in PSB_WS_ELEMENT_LINES references the primary key of the PSB_WS_POSITION_LINES table, establishing the link to the position definition.
  • PSB.PSB_PAY_ELEMENTS: The PAY_ELEMENT_ID column in PSB_WS_ELEMENT_LINES references the primary key of the PSB_PAY_ELEMENTS table, linking to the catalog of valid compensation elements.

These relationships ensure referential integrity, meaning every element line must be associated with a valid, existing position and pay element. The table is also indexed on these foreign key columns (POSITION_LINE_ID, PAY_ELEMENT_ID) and others (BUDGET_YEAR_ID, STAGE_SET_ID, ELEMENT_SET_ID) to optimize query performance for common access paths.