Search Results pay_element_name




Overview
Explore in AI Chat

Overview

APPS.PSB_WS_ELEMENT_LINE_NAMES_V is a supplementary view in the Oracle E-Business Suite HR/Payroll product family, owned by the APPS schema and registered under FND Design Data as PSB.PSB_WS_ELEMENT_LINE_NAMES_V. It belongs to the PSB module, which supports budgetary and compensation planning structures such as position lines, element lines, service packages and stage sets. The view is classified as a supplementary view used to simplify forms coding, and Oracle explicitly warns that it should not be queried or used for data modification, as its definition may change dramatically in subsequent minor or major releases.

The view presents budget element line data enriched with pay element names, allowing planners and developers to resolve numeric element identifiers into human-readable descriptions while retaining stage progression information. It does not carry the "WS" workload/planning staging semantics as a public interface, but rather serves internal form and inquiry logic.

Underlying Base Objects

The view is documented as referencing two base tables: APPS.PSB_PAY_ELEMENTS and APPS.PSB_WS_ELEMENT_LINES. The join effectively combines element line records with the pay element definition to expose the pay element name alongside the line-level attributes. It is not referenced by any database object, confirming it acts as a leaf-level convenience view rather than a dependency for further database structures. The listed join columns include ELEMENT_LINE_ID and PAY_ELEMENT_ID, which link the element line to its pay element definition.

Key Columns

  • ELEMENT_LINE_ID (NUMBER 20) — primary identifier of the budget element line.
  • POSITION_LINE_ID (NUMBER 20) — the position line to which the element line is attached.
  • BUDGET_YEAR_ID (NUMBER 15) — the budget year context for the line.
  • PAY_ELEMENT_ID (NUMBER 20) — foreign key to the pay element definition.
  • PAY_ELEMENT_NAME (VARCHAR2 30) — the descriptive pay element name resolved from PSB_PAY_ELEMENTS.
  • CURRENCY_CODE and ELEMENT_COST — the currency and monetary value associated with the element line.
  • ELEMENT_SET_ID, SERVICE_PACKAGE_ID, STAGE_SET_ID — grouping identifiers for element sets, service packages, and stage sets.
  • START_STAGE_SEQ, CURRENT_STAGE_SEQ, END_STAGE_SEQ — stage sequence values describing the progression of the element line through its defined stage set.
  • FOLLOW_SALARY (VARCHAR2) — a flag indicating whether the element follows the salary.

Common Use Cases and Queries

The view is most useful for resolving pay element names against element line rows and for examining stage progression, particularly the END_STAGE_SEQ column, which the user searched for. A typical query retrieves element lines with their pay element names and stage bounds for a given budget year:

  • SELECT element_line_id, pay_element_name, start_stage_seq, current_stage_seq, end_stage_seq, element_cost FROM apps.psb_ws_element_line_names_v WHERE budget_year_id = :p_budget_year_id;
  • Identifying element lines whose END_STAGE_SEQ has been reached: SELECT element_line_id, element_set_id, end_stage_seq FROM apps.psb_ws_element_line_names_v WHERE current_stage_seq >= end_stage_seq;
  • Joining to position lines to report element costs by currency and position: SELECT position_line_id, pay_element_name, currency_code, element_cost FROM apps.psb_ws_element_line_names_v ORDER BY position_line_id, pay_element_name;

Because Oracle documents this object as a forms-simplifying supplementary view that may change without notice, it should be used for read-only inquiry and reporting only. Persistent integrations should be built against the underlying base tables PSB_WS_ELEMENT_LINES and PSB_PAY_ELEMENTS instead.