Search Results budget_revision_pos_line_id

Overview

The PSB_BUDGET_REVISION_POSITIONS table is a core transactional data store within Oracle E-Business Suite's Public Sector Budgeting (PSB) module. It is specifically designed to capture and manage position-level transactions that occur during the budget revision process. In the context of government and public sector budgeting, a "position" typically refers to a funded job or role within an organization's budget. This table acts as a child or detail table, recording the specific adjustments—such as funding increases, decreases, or reclassifications—made to individual positions as part of a broader budget revision request. Its existence is critical for maintaining a granular audit trail of how budgeted personnel costs are modified throughout the fiscal cycle.

Key Information Stored

The table's primary purpose is to link budget revision lines to the specific positions being adjusted and to associate those positions with their governing budget groups. The metadata indicates several key structural elements. The table is identified by the primary key column BUDGET_REVISION_POS_LINE_ID. Two critical foreign key relationships define its core data: the POSITION_ID column links to the PSB_POSITIONS table, identifying the specific job role being revised, and the BUDGET_GROUP_ID column links to the PSB_BUDGET_GROUPS table, classifying the position within a larger budgetary unit or category. While the exact transactional amount or adjustment type columns are not listed in the provided excerpt, this table serves as the essential junction that ties the revision document line (via PSB_BUDGET_REVISION_POS_LINES) to the master position and budget group data.

Common Use Cases and Queries

This table is central to queries that analyze the impact of budget revisions on an organization's personnel budget. Common reporting and audit scenarios include tracing all revisions affecting a particular position, summarizing revisions by budget group, or validating the integrity of a revision batch. A typical analytical query would join this table to its parent revision lines and related master data. For example:

• Identifying all positions modified in a specific budget revision: SELECT brp.* FROM psb_budget_revision_positions brp, psb_budget_revision_pos_lines brpl WHERE brp.budget_revision_pos_line_id = brpl.budget_revision_pos_line_id AND brpl.budget_revision_id = :p_rev_id;
• Reporting on revisions by budget group: SELECT bg.name budget_group, COUNT(brp.position_id) FROM psb_budget_revision_positions brp, psb_budget_groups bg WHERE brp.budget_group_id = bg.budget_group_id GROUP BY bg.name;

Related Objects

PSB_BUDGET_REVISION_POSITIONS sits at the intersection of several key PSB tables, forming a critical part of the budget revision data model. Its primary foreign key dependencies, as documented, are:

• PSB_POSITIONS: The master table for position definitions, providing descriptive details for the POSITION_ID referenced.
• PSB_BUDGET_GROUPS: The master table for budget group definitions, providing context for the BUDGET_GROUP_ID.
• PSB_BUDGET_REVISION_POS_LINES: This is the direct parent table. The BUDGET_REVISION_POS_LINE_ID in PSB_BUDGET_REVISION_POSITIONS is the primary key of PSB_BUDGET_REVISION_POS_LINES, linking each position adjustment to its higher-level revision transaction line.

This structure ensures that every position-level budget change is systematically tracked back to a formal revision document and its associated master data.