Search Results root_budget_group

Overview

APPS.PSBBV_BUDGET_GROUPS is a Business Intelligence System (BIS) view in the Oracle EBS Applications schema, registered under FND Design Data PSB.PSBBV_BUDGET_GROUPS with a status of VALID. The view presents budget group definitions maintained within the Oracle Public Sector Budgeting (PSB) module, exposing one row per configured budget group. Budget groups in PSB serve as the organizing construct for a set of budget organizations, determining which organizations participate in a budgeting cycle and how their budget data is aggregated, calculated, and versioned.

Because it is exposed under the APPS schema, the view is directly queryable by reporting tools, concurrent programs, and integration interfaces without requiring grants on the underlying PSB tables. It is commonly consumed by discoverer workbooks, Oracle Reports, OBIEE/BIP extracts, and custom PL/SQL that needs read-only visibility into budget group configuration. The view is principally a reporting and reference object; the documentation states that it is not referenced by any other database object, confirming that it has no inbound dependency chain of its own.

Underlying Base Objects

The view is defined over the base table APPS.PSB_BUDGET_GROUPS. The ETRM dependency listing identifies PSB_BUDGET_GROUPS as the sole referenced object; no additional tables, views, or synonyms are documented as contributing to the view definition. Practically, this means PSBBV_BUDGET_GROUPS is a projecting view that surfaces the columns of PSB_BUDGET_GROUPS without materializing derived or joined data.

PSB_BUDGET_GROUPS stores the budget group hierarchy and its effective-dating attributes. The view does not include the standard WHO columns of the base table beyond LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, and CREATION_DATE, and it does not expose the security or multi-organization columns that may exist on the table. Because the view performs no joins, row counts and data types map directly to the base table, and any filtering, effective-date resolution, or hierarchical expansion must be applied by the calling query.

Key Columns

• BUDGET_GROUP_SHORT_NAME (VARCHAR2, 20) — the user-visible short identifier for the budget group; this is the column returned when a user searches for "budget_group_short_name" and is typically the primary filter or display key in reports.
• ROOT_SHORT_NAME (VARCHAR2, 20) — the short name of the top-level (root) budget group in the hierarchy to which this row belongs.
• BUDGET_GROUP_NAME (VARCHAR2, 80) — the descriptive name of the budget group.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE (DATE) — the effective dating window during which the budget group is valid for use.
• BUDGET_GROUP_NUM_PROPOSED_YRS (NUMBER) — the number of years the budget group calculation spans.
• ROOT_BUDGET_GROUP (VARCHAR2) — flag indicating whether the row represents a root budget group.
• FREEZE_HIERARCHY_FLAG (VARCHAR2) — flag indicating whether the budget group hierarchy is frozen and therefore not modifiable.
• BUDGET_GROUP_DESCRIPTION (VARCHAR2, 240) and NARRATIVE_DESCRIPTION (VARCHAR2, 2000) — short and extended descriptive text.
• BUDGET_GROUP_ID (NUMBER, 20) — the unique primary key for the budget group.
• ROOT_BUDGET_GROUP_ID (NUMBER, 20) — the unique identifier of the root budget group, enabling hierarchical joins without resolving names.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard Who audit columns.

Common Use Cases and Queries

The most frequent use is resolving a short name entered by a user into its internal identifier. The following query retrieves the primary configuration attributes for a given budget group:

SELECT BUDGET_GROUP_ID, BUDGET_GROUP_SHORT_NAME, BUDGET_GROUP_NAME,
  START_EFFECTIVE_DATE, END_EFFECTIVE_DATE,
  BUDGET_GROUP_NUM_PROPOSED_YRS, ROOT_BUDGET_GROUP,
  FREEZE_HIERARCHY_FLAG
FROM APPS.PSBBV_BUDGET_GROUPS
WHERE BUDGET_GROUP_SHORT_NAME = :p_short_name;

To list all currently effective root budget groups, filter on the effective dates and the root flag:

SELECT BUDGET_GROUP_SHORT_NAME, BUDGET_GROUP_NAME, BUDGET_GROUP_ID
FROM APPS.PSBBV_BUDGET_GROUPS
WHERE ROOT_BUDGET_GROUP = 'Y'
  AND SYSDATE BETWEEN START_EFFECTIVE_DATE AND NVL(END_EFFECTIVE_DATE, SYSDATE);

To enumerate every budget group under a given root, join on the root identifier rather than the name:

SELECT B.BUDGET_GROUP_SHORT_NAME, B.BUDGET_GROUP_NAME
FROM APPS.PSBBV_BUDGET_GROUPS B
WHERE B.ROOT_BUDGET_GROUP_ID = (SELECT BUDGET_GROUP_ID
  FROM APPS.PSBBV_BUDGET_GROUPS
  WHERE BUDGET_GROUP_SHORT_NAME = :p_root_short_name);

Because the view is not referenced by other database objects, it is safe to query directly for validation and reconciliation reporting, including comparisons of freeze status across groups or audits of effective-date windows. Queries should always constrain on effective dates where the consumer requires only the currently active definition, since the view imposes no such filter itself.