Search Results budget_group_type




Overview
Explore in AI Chat

Overview

APPS.PSBBV_BUDGET_REVISIONS is a read-only Oracle E-Business Suite view defined in the Public Sector Budgeting (PSB) module, part of the Enterprise Resource Planning budget execution and control stack. The view presents budget revision records that are visible to the responsibility currently connected to the session, filtered dynamically through Oracle's FND_GLOBAL.RESP_ID context. Its principal role is to expose budget revision definitions, their approval and submission state, freeze status, and associated GL budget set references for reporting, extensions, and integration with downstream budgeting or approval workflows. Because the view filters by responsibility, it is intended for use within a logged-in EBS session rather than for batch extraction that requires unrestricted access.

Underlying Base Objects

The view is defined almost entirely over a single base table, PSB_BUDGET_REVISIONS, aliased as BR. It correlates that table against two additional PSB dictionary tables: PSB_BUDGET_GROUPS and PSB_BUDGET_GROUP_RESP. The WHERE clause restricts rows to budget groups whose budget_group_type equals 'R' (revision groups) and whose effective date range covers the current SYSDATE using BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE). It then anchors the hierarchy at budget groups assigned to the session's responsibility via PSB_BUDGET_GROUP_RESP, and walks the group hierarchy with a CONNECT BY PRIOR budget_group_id = parent_budget_group_id clause. The access path is therefore: responsibility assignment to group, hierarchical expansion through parent_budget_group_id, and finally the revision rows themselves. No other base objects are documented in the ETRM metadata, though the view assembles lookup meanings for revision source and transaction type through Oracle Application Object Library lookup conventions (FND_LOOKUPS).

Key Columns

Common Use Cases and Queries

Typical uses include building responsibility-scoped revision status reports, feeding approval dashboards, and validating which revision groups a user can see before triggering additional logic.

SELECT budget_revision_id,
       budget_group_id,
       submission_status,
       submission_date,
       freeze_flag
FROM   apps.psbbv_budget_revisions
WHERE  submission_status = 'SUBMITTED'
ORDER BY submission_date DESC;

Because the view self-scopes by responsibility, a query run under a super-user or system administrator responsibility may return no rows unless a PSB responsibility context is established. Analysts tracing hierarchy visibility should query PSB_BUDGET_GROUPS directly on parent_budget_group_id, since that column is consumed internally by the view's CONNECT BY rather than projected to the result set. For unrestricted reporting, query PSB_BUDGET_REVISIONS directly.