Results for “fte_line_id”

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

Overview

PSBBV_WS_FTE_LINES is an APPS-owned, read-only view within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite. It exposes full-time equivalent (FTE) line data used by the budgeting worksheet and Web Services (WS) integration layer. In the ETRM 12.2.2 reference the object is registered as a VALID view in the APPS schema, and its underlying definition is a straight projection over the single base table PSB_WS_FTE_LINES, restricted by the WITH READ ONLY clause.

Its principal role is to provide a controlled, query-safe interface for reporting and integration consumers that need to read position line FTE figures without touching the base table directly. Because the view is read-only, any attempt to insert, update, or delete through it raises ORA-01733, protecting the underlying budgeting data from unintended modification. This makes the object suitable for concurrent programs, BI Publisher data sources, OAF pages, and external web service calls that need a stable read contract.

Underlying Base Objects

The view is defined entirely over PSB_WS_FTE_LINES (aliased WFL). The documented view text selects every relevant column from that table; no joins, unions, subqueries, or additional base objects are present. In effect, PSBBV_WS_FTE_LINES is a column-pass-through wrapper with a read-only constraint rather than a denormalization or aggregation layer.

Because there is a one-to-one relationship with PSB_WS_FTE_LINES, row counts and key values are identical to the base table. The FTE_LINE_ID column functions as the primary key of the underlying row, while POSITION_LINE_ID, SERVICE_PACKAGE_ID, and BUDGET_YEAR_ID serve as the primary foreign-key context linking each FTE record to a position line, a service package, and a budget year respectively. The START_STAGE_SEQ, CURRENT_STAGE_SEQ, and END_STAGE_SEQ columns indicate that the base table participates in a workflow or stage-based approval process typical of budget preparation cycles.

Key Columns

• FTE_LINE_ID — Unique identifier for the FTE line; the surrogate key of the underlying record.
• POSITION_LINE_ID — Reference to the position line whose staffing level this FTE row describes.
• SERVICE_PACKAGE_ID — Identifier of the service package that groups the budgeted activity.
• BUDGET_YEAR_ID — The budget year against which the FTE figures are recorded.
• ANNUAL_FTE — Total annualized full-time equivalent value for the line.
• PERIOD1_FTE … PERIOD12_FTE — Twelve period-level FTE amounts, supporting periodic budget distribution and spread analysis.
• START_STAGE_SEQ / CURRENT_STAGE_SEQ / END_STAGE_SEQ — Workflow sequencing that records the entry, active, and terminal stages of the FTE line within the budgeting process.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — Standard EBS audit columns, useful for change tracking and data lineage reporting.

Common Use Cases and Queries

Typical use cases include budget FTE reporting by position and service package, reconciliation of annual versus periodic FTE totals, and workflow stage analysis showing which FTE lines remain pending in the budgeting cycle. A representative query lists FTE lines for a given budget year:

SELECT fte_line_id, position_line_id, service_package_id, annual_fte, current_stage_seq FROM apps.psbbv_ws_fte_lines WHERE budget_year_id = :p_budget_year_id ORDER BY position_line_id;

A second pattern sums periodic columns to compare against the annual figure, flagging discrepancies:

SELECT fte_line_id, annual_fte, (period1_fte + period2_fte + period3_fte + period4_fte + period5_fte + period6_fte + period7_fte + period8_fte + period9_fte + period10_fte + period11_fte + period12_fte) AS periodic_total FROM apps.psbbv_ws_fte_lines WHERE budget_year_id = :p_budget_year_id;

Integration consumers should always qualify the view with APPS and bind BUDGET_YEAR_ID or POSITION_LINE_ID to limit result sets, as the underlying table can grow considerably across budgeting cycles. Because the object is documented as read-only, it should be treated strictly as a reporting and integration surface; all maintenance must be performed against PSB_WS_FTE_LINES through supported PSB application flows.