Results for “psb_budget_revision_position_v”

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

Overview

The PSB_BUDGET_REVISION_POSITION_V view belongs to the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It is a reporting and integration view that consolidates budget revision information at the position level, joining revision header data, revision position lines, and employee assignment details into a single queryable structure. Rather than forcing report developers and integrators to navigate the normalized PSB revision schema manually, the view presents a denormalized projection that is convenient for budget analysis, salary and position planning extracts, and custom concurrent programs.

Because the object is a view and not a table, it holds no data of its own; all content is derived at runtime from the underlying Public Sector Budgeting base tables. The view is owned by the APPS schema and is documented as VALID in the ETRM metadata. Its principal value lies in the fact that budget revisions are frequently performed against positions and assignments, and this view exposes that relationship directly, including the revision measure itself through the REVISION_VALUE column and its accompanying type indicator.

Underlying Base Objects

The view is defined with an outer-join query over five base objects:

• PSB_BUDGET_REVISION_POSITIONS (BRP) — the primary driver, holding the position-level revision rows including REVISION_TYPE, REVISION_VALUE_TYPE, and REVISION_VALUE.
• PSB_BUDGET_REVISION_POS_LINES (BRPL) — the parent line record joined on BUDGET_REVISION_POS_LINE_ID, supplying FREEZE_FLAG and VIEW_LINE_FLAG.
• PSB_POSITIONS (PP) — the position definition, providing the position NAME.
• PSB_POSITION_ASSIGNMENTS (PPE) — the assignment linkage, joined with an outer join constrained to ASSIGNMENT_TYPE = 'EMPLOYEE'.
• PSB_EMPLOYEES (PE) — employee detail (EMPLOYEE_NUMBER, FULL_NAME), joined with an outer join so that unassigned positions still return rows.

The outer joins on PPE and PE are significant: they ensure that revisions for vacant or unassigned positions are still reported, with employee columns returning NULL.

Key Columns

• BUDGET_REVISION_ID — identifier of the parent budget revision.
• BUDGET_REVISION_POS_LINE_ID — the revision line to which the position row belongs.
• POSITION_ID / NAME — the position being revised and its descriptive name.
• HR_EMPLOYEE_ID, EMPLOYEE_NUMBER, FULL_NAME — assigned employee attributes (NULL when unassigned).
• REVISION_TYPE — categorizes the nature of the revision.
• REVISION_VALUE_TYPE — indicates how the revision is expressed (for example, amount or percentage).
• REVISION_VALUE — the revision measure itself; the primary column users search for. Note that in the documented view text REVISION_VALUE is selected more than once, effectively exposing the same underlying column under aliased names such as PERCENT_REVISED and AMOUNT_REVISED.
• PERCENT_REVISED / AMOUNT_REVISED — aliases of the revision value, intended for percentage- and amount-based contexts respectively.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the effective period of the revision row.
• FREEZE_FLAG / VIEW_LINE_FLAG — line-level control flags originating from the revision lines table.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on extracting revisions for a given budget group or position and reconciling amounts against percentages. The following example returns all employee-assigned position revisions for a budget group:

SELECT budget_revision_id, name, full_name, revision_type,
       revision_value_type, revision_value
  FROM apps.psb_budget_revision_position_v
 WHERE budget_group_id = :p_group
    AND view_line_flag = 'Y';

Another common pattern identifies positions with no employee assignment, using the outer-joined employee columns:

SELECT position_id, name, revision_value
  FROM apps.psb_budget_revision_position_v
 WHERE hr_employee_id IS NULL;

The view supports budget development reports, position control extracts, and integration feeds into downstream planning systems. Because it is a view, developers should expect no row-level security beyond what the base PSB tables enforce, and should apply appropriate business group and budget group predicates in custom SQL.