Results for “budget_revision_id”

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

Overview

PSBFV_POSITION_FTE is an APPS-owned, read-only view in the Oracle E-Business Suite product PSB (Public Sector Budgeting), documented as VALID in both 12.1.1 and 12.2.2. Its stated purpose is to provide details about position full-time equivalent (FTE) values sourced from the Position Control tables. In practice, the view consolidates position FTE line data with the associated budget revision context and the key flexfield-derived position name, so that budgeting reports, concurrent programs, and integration extracts can resolve the descriptive values without performing the joins themselves.

The view is defined with the WITH READ ONLY clause, confirming that it is intended strictly for query and reporting. Because it exposes POSITION_FTE_LINE_ID as its leading column, it is the canonical access path for consumers searching on that identifier — the term most frequently associated with this object.

Underlying Base Objects

The view text joins four PSB tables:

• PSB_POSITION_FTE (aliased PPF) — the driving table holding the FTE line records, including POSITION_FTE_LINE_ID, POSITION_ID, BUDGET_REVISION_ID, BASE_LINE_VERSION, START_DATE, END_DATE, and FTE. The view is thin over this table; nearly all exposed columns originate here.
• PSB_BUDGET_REVISIONS (aliased BR) — joined on BUDGET_REVISION_ID using an outer join (BR.BUDGET_REVISION_ID(+)), supplying the budget revision justification text. Because the join is outer, position FTE lines without a matching revision are still returned.
• PSB_POSITIONS (aliased POS) — joined on POSITION_ID, mapping each FTE line to its position record and, in turn, to the position definition.
• PSB_POSITION_DEFINITIONS_KFV (aliased PKFV) — the key flexfield view for position definitions, joined on POSITION_DEFINITION_ID, which resolves the concatenated position name exposed as "_KF:POSITION_NAME".

The join chain is therefore PPF → POS (on POSITION_ID) → PKFV (on POSITION_DEFINITION_ID), with PPF → BR (on BUDGET_REVISION_ID) as a non-mandatory lookup. The ETRM metadata records no separately documented referenced base objects, but the view text establishes the dependencies above.

Key Columns

• POSITION_FTE_LINE_ID — Primary identifier of the FTE line; the column most commonly used for direct lookups.
• POSITION_ID — Foreign key to PSB_POSITIONS, linking the FTE record to its parent position.
• "_KF:POSITION_NAME" — The key flexfield-derived descriptive name of the position, projected via a literal descriptor selector ('_KF:PSB:BPS:PKFV:_CO') over PSB_POSITION_DEFINITIONS_KFV. Note that the column name contains a colon and must be quoted in SQL.
• BUDGET_REVISION_ID — The budget revision to which the FTE line belongs.
• BUDGET_REVISION_JUSTIFICATION — Justification text from PSB_BUDGET_REVISIONS; null where no revision row matches.
• BASE_LINE_VERSION — Identifies the base line version associated with the FTE record, used to distinguish baseline from revision data.
• START_DATE / END_DATE — Effective date range for the FTE line.
• FTE — The full-time equivalent value itself, the core quantitative measure of the view.

Common Use Cases and Queries

Typical uses include position control budget reporting, FTE reconciliation against budget revisions, and integration extracts requiring position name resolution. A lookup by the searched identifier is straightforward:

• SELECT position_fte_line_id, position_id, fte, start_date, end_date FROM apps.psbfv_position_fte WHERE position_fte_line_id = :line_id;
• SELECT position_id, "_KF:POSITION_NAME", budget_revision_id, budget_revision_justification, fte FROM apps.psbfv_position_fte WHERE budget_revision_id = :rev_id ORDER BY position_id;
• SELECT p.position_fte_line_id, p.fte, p.start_date, p.end_date FROM apps.psbfv_position_fte p WHERE TRUNC(SYSDATE) BETWEEN p.start_date AND p.end_date;

Because the view is read-only and joins the position flexfield view, queries should always qualify the application schema (APPS) and quote the flexfield-derived column name. For performance, filter on POSITION_FTE_LINE_ID, POSITION_ID, or BUDGET_REVISION_ID, which align with the underlying join keys.