Results for “psb_budget_revisions_u1”

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

Overview

PSB_BUDGET_REVISIONS is the budget revision header table within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. The table resides in the PSB schema and functions as the central transactional anchor for the budget revision process, capturing the defining attributes of each revision event initiated against a budget group or general ledger budget set. Every revision workflow—whether it revises position data, account line data, or a combination of both—originates with a row in this header table, from which downstream detail records are generated and tracked.

From a dimensional modeling perspective, the metadata's Data Vault classification is hub-leaning. This reflects the table's role as a durable, uniquely identified business entity (the budget revision) referenced by multiple dependent satellites and link structures rather than serving as a pure transactional detail store. Modelers constructing a Data Vault or dimensional layer should consider treating PSB_BUDGET_REVISIONS as a hub keyed on BUDGET_REVISION_ID, with the descriptive and status columns distributed across one or more satellite tables organized by change frequency and source.

Key Information Stored

The table contains 63 documented columns. The surrogate primary key, enforced by PSB_BUDGET_REVISIONS_PK and the unique index PSB_BUDGET_REVISIONS_U1, is BUDGET_REVISION_ID. The most significant columns include:

• BUDGET_REVISION_ID — the system-generated unique identifier for the revision header, and the primary key propagated to all dependent detail tables.
• BUDGET_GROUP_ID — foreign key to PSB_BUDGET_GROUPS, identifying the budget group context for the revision.
• GL_BUDGET_SET_ID — foreign key to PSB_GL_BUDGET_SETS, linking the revision to the underlying GL budget set.
• BUDGET_REVISION_TYPE and TRANSACTION_TYPE — classify the nature and category of the revision.
• FROM_GL_PERIOD_NAME and TO_GL_PERIOD_NAME — define the GL period range affected by the revision.
• CURRENCY_CODE — the currency in which revision amounts are expressed.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the validity window for the revision.
• SUBMISSION_DATE and SUBMISSION_STATUS — track workflow submission and approval state.
• PERMANENT_REVISION and REVISE_BY_POSITION — flags governing how the revision is applied.
• BASE_LINE_REVISION, GLOBAL_BUDGET_REVISION, and GLOBAL_BUDGET_REVISION_ID — support baseline and global revision scenarios.
• REQUEST_ID — associates the record with a concurrent program submission.
• FREEZE_FLAG and APPROVAL_OVERRIDE_BY — control locking and override behavior during approval.
• Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and 30 descriptive ATTRIBUTE columns with CONTEXT support flexfield extension.

Common Use Cases and Queries

Typical usage centers on budget revision inquiry, workflow status reporting, and reconciliation between revision headers and their detailed lines or position allocations.

• Retrieving all revisions for a given budget group: SELECT * FROM PSB_BUDGET_REVISIONS WHERE BUDGET_GROUP_ID = :p_group_id;
• Identifying revisions pending approval: SELECT BUDGET_REVISION_ID, SUBMISSION_DATE, SUBMISSION_STATUS FROM PSB_BUDGET_REVISIONS WHERE SUBMISSION_STATUS = 'SUBMITTED';
• Joining header to detail for line-level reporting: SELECT h.BUDGET_REVISION_ID, l.* FROM PSB_BUDGET_REVISIONS h, PSB_BUDGET_REVISION_LINES l WHERE h.BUDGET_REVISION_ID = l.BUDGET_REVISION_ACCT_LINE_ID;
• Linking revisions to GL budget sets and periods to analyze impact by fiscal range.
• Auditing who initiated or overrode approvals using REQUESTOR and APPROVAL_OVERRIDE_BY.

Related Objects

The following tables are the most significant references to PSB_BUDGET_REVISIONS, based on the documented foreign key relationships:

• PSB_BUDGET_GROUPS — referenced via BUDGET_GROUP_ID.
• PSB_GL_BUDGET_SETS — referenced via GL_BUDGET_SET_ID.
• PSB_BUDGET_REVISION_LINES — references this table via BUDGET_REVISION_ACCT_LINE_ID.
• PSB_BUDGET_REVISION_POS_LINES — references this table via BUDGET_REVISION_ID.
• PSB_POSITION_ACCOUNTS — references this table via BUDGET_REVISION_ID.
• PSB_POSITION_COSTS — references this table via BUDGET_REVISION_ID.
• PSB_POSITION_FTE — references this table via BUDGET_REVISION_ID.

These relationships confirm PSB_BUDGET_REVISIONS as the transactional hub of the Public Sector Budgeting revision model, with the position-oriented tables (accounts, costs, and FTE) and the account line table all dependent on the header record for referential integrity.