Search Results revision_value_type




Overview

APPS.PSB_BUDGET_REVISION_POSITION_V is a supplementary view in the Oracle E-Business Suite Public Sector Budgeting (PSB) module. It exposes budget revision lines defined at the position level, joining revision header information with position and employee attributes. The view is classified in ETRM as a "supplementary view used to simplify forms coding," meaning it exists primarily to collapse multi-table retrieval logic into a single queryable object for the PSB budget revision forms rather than to serve as a stable integration interface. Oracle explicitly warns that the view is not recommended for direct querying or data alteration and may change dramatically in subsequent minor or major releases. This caveat is significant for the user searching on revision_value_type, because that column drives the interpretation of two sibling columns and is therefore central to any downstream reporting built on the view.

Underlying Base Objects

The documented metadata records no referenced base objects and leaves the Owner field blank in the ETRM 12.2.2 extract, although the view source indicates the object is deployed in the APPS schema under the FND Design Data designation PSB.PSB_BUDGET_REVISION_POSITION_V. The column list itself identifies the principal lineage: BUDGET_REVISION_ID is a foreign key to PSB_BUDGET_REVISIONS, and BUDGET_REVISION_POS_LINE_ID is described as the system-generated primary key of the position revision line. POSITION_ID, BUDGET_GROUP_ID, and HR_EMPLOYEE_ID imply joins to the PSB position and budget group entities and to Oracle HRMS for employee attributes such as EMPLOYEE_NUMBER and FULL_NAME. The view therefore functions as a denormalized projection over the budget revision header, the position revision line, and HR person records.

Key Columns

  • BUDGET_REVISION_ID — foreign key to PSB_BUDGET_REVISIONS, linking the line to its parent revision.
  • BUDGET_REVISION_POS_LINE_ID — system-generated primary key for the position revision line.
  • POSITION_ID / NAME — unique identifier and descriptive name of the position being revised.
  • HR_EMPLOYEE_ID, EMPLOYEE_NUMBER, FULL_NAME — employee identifiers sourced from Human Resource Management Systems.
  • BUDGET_GROUP_ID — associates the line with its budgeting group.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date range governing the revision line's validity.
  • REVISION_TYPE — 'I' indicates an increased revision; 'D' indicates a decreased revision.
  • REVISION_VALUE_TYPE — discriminates between percentage-based and amount-based revisions; this is the column the user searched for.
  • REVISION_VALUE — the numeric revision quantity as entered.
  • PERCENT_REVISED — reflects the percentage of increase or decrease when REVISION_VALUE_TYPE is '%'.
  • AMOUNT_REVISED — reflects the amount of increase or decrease when REVISION_VALUE_TYPE is 'A'.
  • FREEZE_FLAG — indicates whether the revision may undergo further changes.
  • VIEW_LINE_FLAG — form-level display control flag.
  • Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY).

The mutual exclusivity of PERCENT_REVISED and AMOUNT_REVISED, governed by REVISION_VALUE_TYPE, is the single most important semantic rule in this view. A revision recorded as type 'A' will carry an amount in AMOUNT_REVISED and typically a null PERCENT_REVISED, while a '%' revision behaves inversely. Queries that aggregate revised values without first filtering on REVISION_VALUE_TYPE will produce misleading totals.

Common Use Cases and Queries

Typical scenarios include auditing position-level budget changes within a revision, reconciling percentage versus amount revisions, and extracting blocked (frozen) revision lines prior to posting. The following query isolates amount-based revisions for a given budget group:

SELECT budget_revision_id, position_id, name, revision_type,
       revision_value_type, amount_revised, freeze_flag
  FROM apps.psb_budget_revision_position_v
 WHERE revision_value_type = 'A'
   AND budget_group_id = :p_group_id
   AND NVL(freeze_flag,'N') = 'N';

A companion query substituting revision_value_type = '%' and selecting PERCENT_REVISED supports percentage-based analysis. Because the view is unfrozen and documented as unstable, production reporting should be validated against the base PSB tables after any patch or upgrade.