Search Results revision_value




Overview
Explore in AI Chat

Overview

APPS.PSBBV_BUDGET_REVISION_POSITION is a Business Intelligence System (BIS) view owned by the APPS schema within Oracle E-Business Suite. It is registered in FND Design Data under the PSB product (Public Sector Budgeting) as PSB.PSBBV_BUDGET_REVISION_POSITION, and holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The view exposes position-level budget revision data, presenting the detail rows that record how individual budget revisions affect specific positions within a budget group. Its columns include the primary identifier column BUDGET_REVISION_POS_LINE_ID, which is the field most commonly searched by developers and analysts building reports or interfaces against budget revision data.

Because it is a BIS view, PSBBV_BUDGET_REVISION_POSITION is intended primarily for reporting, extraction, and integration purposes rather than for direct transactional data entry. It provides a denormalized, read-only read path over the underlying PSB budget revision tables, allowing external tools, custom concurrent programs, and third-party reporting engines to consume budget revision position data without navigating the normalized base schema directly.

Underlying Base Objects

The view is defined over two documented base objects: APPS.PSB_BUDGET_REVISION_POSITIONS and APPS.PSB_BUDGET_REVISION_POS_LINES. PSB_BUDGET_REVISION_POSITIONS carries the header-level revision attributes, such as the revision type, revision value type, revision value, effective dates, and the associated note identifier. PSB_BUDGET_REVISION_POS_LINES supplies the line-level detail, including BUDGET_REVISION_POS_LINE_ID, the position reference, and the link back to the parent revision. The view joins these two objects to present a single flattened result set.

According to the documented metadata, PSBBV_BUDGET_REVISION_POSITION is not referenced by any other database object. It therefore functions as a terminal, leaf-level dependency in the object graph — a consumer of base tables rather than a source for further view or synonym definitions. This characteristic makes it safe to query without concern for downstream impact, and it reinforces its role as a reporting-only construct.

Key Columns

  • BUDGET_REVISION_ID (NUMBER, 20) — Identifier of the parent budget revision header record from PSB_BUDGET_REVISION_POSITIONS.
  • BUDGET_REVISION_POS_LINE_ID (NUMBER, 20) — The line-level primary key for the position revision row; the field most frequently used to link the view to related position revision details.
  • POSITION_ID (NUMBER, 20) — Reference to the position affected by the revision.
  • BUDGET_GROUP_ID (NUMBER, 20) — The budget group context in which the revision applies.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE (DATE) — The date range during which the revision is in effect, enabling date-effective reporting.
  • REVISION_TYPE (VARCHAR2) — Classifies the nature of the revision.
  • REVISION_VALUE_TYPE (VARCHAR2) — Indicates whether the revision value is expressed as an amount or a percentage.
  • REVISION_VALUE (NUMBER) — The numeric magnitude of the revision.
  • NOTE_ID (NUMBER, 20) — Reference to an associated descriptive note.

Common Use Cases and Queries

Typical use cases include budget revision reporting by position and budget group, reconciliation of position-level revision amounts, and extraction feeds for downstream budgeting or analytics systems. The view is frequently queried by BUDGET_REVISION_POS_LINE_ID when tracing a specific revision line, or by POSITION_ID and BUDGET_GROUP_ID when auditing all revisions affecting a position.

A standard retrieval pattern is a full projection as documented in the ETRM source:

  • SELECT BUDGET_REVISION_ID, BUDGET_REVISION_POS_LINE_ID, POSITION_ID, BUDGET_GROUP_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, REVISION_TYPE, REVISION_VALUE_TYPE, REVISION_VALUE, NOTE_ID FROM APPS.PSBBV_BUDGET_REVISION_POSITION;
  • Filtering by position: add WHERE POSITION_ID = :p_position_id to isolate revisions for a single position.
  • Filtering by line: add WHERE BUDGET_REVISION_POS_LINE_ID = :p_line_id to retrieve a specific revision line.
  • Date-effective analysis: add WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE to return only currently effective revisions.

Because the view is read-only and not referenced by other objects, it can be queried directly in custom reports and concurrent programs without risk of affecting the base PSB schema.