Results for “end_stage_seq”

50+ results




Overview
Explore in AI Chat

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

Overview

PSBBV_WS_ELEMENT_COST_LINES is a reporting view in the Oracle E-Business Suite (EBS) Public Sector Budgeting (PSB) module, which is classified as obsolete in release 12.1.1 and 12.2.2. The view exposes element-level cost line data associated with budgeting worksheets, presenting a read-only projection of cost distribution records tied to pay elements, budget years, and position lines. It is defined as a WITH READ ONLY construct, meaning it is intended strictly for querying and downstream integration rather than for DML operations. This design supports the Web Services (WS) layer of Public Sector Budgeting, where external systems and internal processes consume budget cost line information in a controlled, non-mutating manner.

The view's role is primarily to surface the monetary and staging information required to reconcile how an element's cost progresses through a budgeting workflow. Among its most notable columns is CURRENT_STAGE_SEQ, the field most directly implicated in the user's search. This column tracks the active workflow stage of an element line, enabling consumers to determine where a particular cost line currently resides within the multi-stage budgeting process.

Underlying Base Objects

The view is defined exclusively over a single base table: PSB_WS_ELEMENT_LINES, aliased as WEL in the view text. No other base objects are documented, and the ETRM metadata records no additional referenced objects. Consequently, PSBBV_WS_ELEMENT_COST_LINES inherits its column structure directly from PSB_WS_ELEMENT_LINES without joins, aggregations, or transformations. The view text is a simple projection:

Because the view maps one-to-one with its base table, any row-level or column-level behavior—such as workflow sequencing—originates entirely in PSB_WS_ELEMENT_LINES. The WITH READ ONLY clause prevents the view from being used as an update path, preserving the integrity of the underlying staging data.

Key Columns

The view exposes thirteen columns, several of which carry significant semantic weight in the budgeting context:

  • POSITION_LINE_ID — Identifier linking the cost line to a specific position line within the budgeting structure.
  • SERVICE_PACKAGE_ID — Reference to the service package under which the element is budgeted.
  • PAY_ELEMENT_ID — The pay element to which the cost applies; central to compensation-related budgeting.
  • BUDGET_YEAR_ID — The budget year associated with the cost line.
  • ELEMENT_COST — The monetary cost value for the element in the given budget year.
  • START_STAGE_SEQ — The starting sequence of the workflow stage for the element line.
  • CURRENT_STAGE_SEQ — The current (active) workflow stage sequence. This column is crucial for determining the in-progress state of a cost line as it moves through approval or processing stages.
  • END_STAGE_SEQ — The terminal sequence of the workflow stage, indicating the completion point.
  • ELEMENT_LINE_ID — Unique identifier for the element line record.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — Standard audit columns supporting traceability and concurrency analysis.

The triplet of START_STAGE_SEQ, CURRENT_STAGE_SEQ, and END_STAGE_SEQ collectively describes the lifecycle progression of a cost line. Querying on CURRENT_STAGE_SEQ allows analysts to isolate lines that are mid-process, which is particularly useful for identifying bottlenecks or incomplete budgeting cycles.

Common Use Cases and Queries

Typical usages of this view include budget reconciliation, workflow monitoring, and integration with external planning systems via the PSB web services layer. Because the module is obsolete, primary usage occurs in legacy reporting environments maintained on EBS 12.1.1 or 12.2.2. A representative query to retrieve active stage cost lines for a given budget year:

  • SELECT ELEMENT_LINE_ID, PAY_ELEMENT_ID, ELEMENT_COST, CURRENT_STAGE_SEQ, START_STAGE_SEQ, END_STAGE_SEQ FROM PSBBV_WS_ELEMENT_COST_LINES WHERE BUDGET_YEAR_ID = :p_budget_year AND CURRENT_STAGE_SEQ < END_STAGE_SEQ ORDER BY CURRENT_STAGE_SEQ;

This query identifies element cost lines that have not yet reached their terminal stage, directly leveraging CURRENT_STAGE_SEQ. Another common pattern audits cost changes by joining audit columns:

  • SELECT POSITION_LINE_ID, ELEMENT_COST, CURRENT_STAGE_SEQ, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM PSBBV_WS_ELEMENT_COST_LINES WHERE LAST_UPDATE_DATE >= SYSDATE - 30;

Because the view is read-only, all such queries are safe for concurrent reporting without risk of accidental modification to the base staging table.