Search Results psb_ws_element_line_names_v

Overview

The PSB_WS_ELEMENT_LINE_NAMES_V view is a public-sector budgeting (PSB) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified as a VALID database VIEW and belongs to the PSB – Public Sector Budgeting product family. The primary purpose of the view is to present position element lines—the costed line items that make up a budget worksheet position—joined to the descriptive name of the associated pay element, so that reports and integrations can display human-readable element labels rather than numeric identifiers.

Because standard ETRM reports and Web Services integrations frequently require the pay element description alongside salary and element cost data, this view acts as a convenient single-source projection. It resolves the foreign key from PSB_WS_ELEMENT_LINES.PAY_ELEMENT_ID to PSB_PAY_ELEMENTS.PAY_ELEMENT_ID and exposes the resulting NAME attribute (aliased for reporting as the pay element name) together with the FOLLOW_SALARY indicator. This allows downstream logic to determine whether an element inherits salary-based costing.

Underlying Base Objects

The view is defined over two documented base tables in the PSB schema:

• PSB_WS_ELEMENT_LINES (WEL) – the primary transaction table holding budget worksheet element lines, including element line, position line, budget year, pay element, currency, element cost, element set, service package, and stage information.
• PSB_PAY_ELEMENTS (PE) – the pay element definition table supplying the element name (NAME) and the FOLLOW_SALARY flag.

The join is an inner join on WEL.PAY_ELEMENT_ID = PE.PAY_ELEMENT_ID, meaning only element lines with a valid, matching pay element definition are returned. The view's text applies a DECODE on NVL(PE.FOLLOW_SALARY,'N'): when FOLLOW_SALARY is 'Y', ELEMENT_SET_ID is returned as NULL; when 'N' (the default), the underlying WEL.ELEMENT_SET_ID value is returned. This conditional projection is important because salary-following elements derive their cost from the position's salary rather than from an explicit element set.

Key Columns

• ELEMENT_LINE_ID – unique identifier for the worksheet element line; primary key of the source line.
• POSITION_LINE_ID – identifies the position line to which the element line belongs.
• BUDGET_YEAR_ID – the budget year context for the line.
• PAY_ELEMENT_ID – foreign key to the pay element definition.
• CURRENCY_CODE – currency in which ELEMENT_COST is expressed.
• ELEMENT_COST – the costed amount for the element line.
• ELEMENT_SET_ID – conditionally returned; NULL when the pay element follows salary.
• SERVICE_PACKAGE_ID, STAGE_SET_ID, START_STAGE_SEQ, CURRENT_STAGE_SEQ, END_STAGE_SEQ – supporting attributes that describe the service package and the staging progression of the element line.
• PAY_ELEMENT_NAME – the descriptive name of the pay element, sourced from PSB_PAY_ELEMENTS.NAME.
• FOLLOW_SALARY – flag indicating whether the element's cost follows the position salary (Y/N).

Common Use Cases and Queries

Typical uses include budget worksheet reporting, integration extracts, and validation of costed element lines by budget year or position. A representative query lists element lines with their readable element names for a given budget year:

• SELECT element_line_id, position_line_id, pay_element_name, element_cost, currency_code, follow_salary FROM apps.psb_ws_element_line_names_v WHERE budget_year_id = :p_budget_year_id ORDER BY position_line_id, element_line_id;
• SELECT position_line_id, pay_element_name, SUM(element_cost) FROM apps.psb_ws_element_line_names_v WHERE budget_year_id = :p_budget_year_id GROUP BY position_line_id, pay_element_name;
• SELECT element_line_id, position_line_id, pay_element_name FROM apps.psb_ws_element_line_names_v WHERE follow_salary = 'Y';

Because only two base tables are involved and no complex aggregation is applied, the view performs efficiently and is well suited to joins with position, budget year, and organization tables in public-sector budgeting reports.