Search Results psbfv_budget_revision_position




Overview
Explore in AI Chat

Overview

The view PSBFV_BUDGET_REVISION_POSITION is a read-only database object owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PSB – Public Sector Budgeting product family. Its status is VALID in the ETRM reference for releases 12.1.1 and 12.2.2. The object is a reporting and integration façade that consolidates budget revision data at the position level, joining transaction detail from the budget revision position tables with descriptive attributes such as revision justification, position name, budget group identifiers, and associated notes. In the Public Sector Budgeting flow, budget analysts create revisions against position lines, assign revision types and value types, and attach notes; this view assembles those fragments into a single denormalized row per revision position line for downstream inquiry, reporting, and interface extraction. Because the view is defined WITH READ ONLY, it is intended strictly for querying — no DML is permitted against it. It is exposed through the standard Oracle Forms-based inquiry screens, Oracle Reports/BI Publisher layouts, and custom SQL used by implementers for integrations to general ledger, position control, or third-party budgeting tools.

Underlying Base Objects

The view text references seven PSB tables and one key-flexfield view. The central detail table is PSB_BUDGET_REVISION_POSITIONS (aliased BRP), which holds the revision position records — revision type, revision value type, revision value, effective dates, budget group, note reference, and position reference. It joins to PSB_BUDGET_REVISION_POS_LINES (BRL) on BUDGET_REVISION_POS_LINE_ID, and to PSB_BUDGET_REVISIONS (BR) on BUDGET_REVISION_ID, from which the revision justification is drawn. PSB_POSITIONS (POS) supplies the position identity and links the position to PSB_POSITION_DEFINITIONS_KFV (PKFV), a key flexfield view that resolves the descriptive position name. PSB_BUDGET_GROUPS (BG) provides the budget group short name, and PSB_WS_ACCOUNT_LINE_NOTES (WALN) supplies the free-text note through an outer join on NOTE_ID (indicated by the (+) operator), so rows without notes are still returned. The view therefore sits one join layer above the core PSB revision position schema, purpose-built for consumption rather than maintenance.

Key Columns

  • BUDGET_REVISION_ID — Identifier of the parent budget revision.
  • BUDGET_REVISION_JUSTIFICATION — Justification text describing the reason for the revision.
  • BUDGET_REVISION_POS_LINE_ID — Identifier of the revision position line.
  • POSITION_ID — Identifier of the position being revised.
  • "_KF:POSITION_NAME" — Key flexfield-resolved descriptive name of the position definition.
  • BUDGET_GROUP_ID / BUDGET_GROUP_SHORT_NAME — Budget group identifier and its short name.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date range during which the revision position is effective.
  • REVISION_TYPE — Classification of the revision applied to the position.
  • REVISION_VALUE_TYPE — Qualifier indicating how the revision value is expressed.
  • REVISION_VALUE — Numeric or defined value of the revision line.
  • NOTE_ID / NOTE — Identifier and resolved free-text note attached to the line.

Common Use Cases and Queries

Typical use cases include producing position-level revision registers, exporting budget revision activity for audit or position control reconciliation, and feeding downstream integrations that require justification and note context. A representative query lists all revision values effective within a fiscal window:

SELECT budget_revision_id, position_id, "_KF:POSITION_NAME",
       revision_type, revision_value_type, revision_value,
       effective_start_date, effective_end_date
FROM   apps.psbfv_budget_revision_position
WHERE  effective_start_date BETWEEN :p_from AND :p_to
ORDER BY budget_revision_id, position_id;

A second pattern aggregates revisions by budget group for reporting: SELECT budget_group_short_name, revision_type, SUM(revision_value) FROM apps.psbfv_budget_revision_position GROUP BY budget_group_short_name, revision_type;. Because the object is read only and exposes only the columns listed above, custom extracts should join back to the base PSB tables if additional attributes or DML are required.