Search Results budget_revision_type

Overview

PSB_BUDGET_REVISIONS_V is a reporting view owned by the APPS schema within the Public Sector Budgeting (PSB) product of Oracle E-Business Suite. As documented in ETRM for releases 12.1.1 and 12.2.2, the view is defined on the PSB_BUDGET_REVISIONS base table and presents information about budget revisions together with denormalized descriptive attributes drawn from associated budget groups, parameter (entity) sets, and application users. Its status is VALID, and it is intended to provide a single, read-consistent projection of revision header data that reporting tools, concurrent programs, and custom integrations can query without reproducing the necessary joins themselves.

In the PSB model, a budget revision records a controlled change to an existing budget — its scope, justification, effective period, and routing through the approval process. The view exposes that header context alongside human-readable identifiers, which makes it suitable for operational reports, approval-status dashboards, and extracts that feed external budget or grants systems.

Underlying Base Objects

The view is defined over four objects, joined as follows:

• PSB_BUDGET_REVISIONS (alias BR) — the primary base table supplying the revision header columns, including the surrogate key BUDGET_REVISION_ID and all descriptive, status, and audit attributes.
• PSB_BUDGET_GROUPS (alias BG) — joined on BUDGET_GROUP_ID = BG.BUDGET_GROUP_ID to supply the budget group short name, exposed as BUDGET_GROUP_NAME.
• PSB_ENTITY_SET (alias PES) — outer-joined on BR.PARAMETER_SET_ID = PES.ENTITY_SET_ID to supply the parameter set name.
• FND_USER (alias FU) — joined on FU.USER_ID = BR.REQUESTOR to supply the requestor's application user name.

The BUDGET_GROUP and REQUESTOR joins are inner joins, so a revision row is returned only when both a valid budget group and a valid requestor user exist. The parameter set join is an outer join, so revisions without a parameter set are still returned, with a null name.

Key Columns

• ROW_ID / BUDGET_REVISION_ID — the row identifier and the primary key of the revision, used to link to revision line or detail tables.
• JUSTIFICATION — free-text rationale recorded for the revision.
• BUDGET_GROUP_ID / BUDGET_GROUP_NAME — the owning budget group key and its short name from PSB_BUDGET_GROUPS.
• GL_BUDGET_SET_ID / HR_BUDGET_ID — references to the associated General Ledger budget set and HR budget definition.
• BUDGET_REVISION_TYPE / TRANSACTION_TYPE — classification of the revision and the transaction it represents.
• FROM_GL_PERIOD_NAME / TO_GL_PERIOD_NAME — the GL period range affected by the revision.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the effective date window of the revision.
• SUBMISSION_DATE / SUBMISSION_STATUS — when the revision was submitted and its current workflow/approval status.
• APPROVAL_ORIG_SYSTEM / APPROVAL_OVERRIDE_BY / FREEZE_FLAG — approval origin, override authority, and whether the revision is frozen from further change.
• REQUESTOR / USER_NAME — the requestor's user ID and resolved application user name.
• GL_BUDGET_SET_ID, CURRENCY_CODE, PERMANENT_REVISION, REVISE_BY_POSITION, BALANCE_TYPE — budgeting behavior controls.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE and ATTRIBUTE1–30 / CONTEXT — standard WHO audit columns and the DFF flexfield segment.

Common Use Cases and Queries

The view most commonly supports revision status reporting, pending-approval worklists, and audit extracts. A representative query lists current revisions with their group and requestor:

• SELECT budget_revision_id, budget_group_name, justification, submission_status, requestor, user_name, effective_start_date, effective_end_date FROM apps.psb_budget_revisions_v WHERE submission_status = 'SUBMITTED';
• Pending-approval counts by group: SELECT budget_group_name, COUNT(*) FROM apps.psb_budget_revisions_v WHERE submission_status <> 'APPROVED' GROUP BY budget_group_name;
• Date-bounded audit extract: SELECT budget_revision_id, requestor, user_name, submission_date FROM apps.psb_budget_revisions_v WHERE submission_date BETWEEN :from_date AND :to_date;

Because the view resolves group, parameter set, and user names, it removes the need for ad-hoc joins and is well suited to Oracle Reports, BI Publisher, and OBIEE sources within PSB.