Results for “psb_budget_groups”

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

Overview

PSB_BUDGET_GROUPS is a table in the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, present in the 12.1.1 and 12.2.2 releases but classified as obsolete within the ETRM documentation. The table stores budget group information and functions as a central organizational construct for the PSB budgeting process, grouping related budget entities, worksheets, positions, and revisions under a single identifier. Based on the foreign-key topology documented in the ETRM metadata, PSB_BUDGET_GROUPS behaves as a data hub: it references GL_SETS_OF_BOOKS_11I and is itself referenced by more than twenty dependent tables that carry BUDGET_GROUP_ID or REVIEW_BUDGET_GROUP_ID.

Because the module is obsolete, the table may not be implemented in all databases. The ETRM record explicitly notes "Not implemented in this database," confirming that environments vary and that the object should be verified before being queried or referenced in custom code.

Key Information Stored

The table holds 66 documented columns, of which the following are most significant for understanding and querying budget group data.

• BUDGET_GROUP_ID — the surrogate primary key defined by PSB_BUDGET_GROUPS_PK and the single-column unique index PSB_BUDGET_GROUPS_U1.
• NAME — the descriptive name of the budget group; forms part of business-key candidate PSB_BUDGET_GROUPS_U2 together with BUDGET_GROUP_TYPE.
• SHORT_NAME — an abbreviated identifier; forms part of business-key candidate PSB_BUDGET_GROUPS_U3 together with BUDGET_GROUP_TYPE.
• BUDGET_GROUP_TYPE — classifies the budget group and participates in both U2 and U3, indicating it is a mandatory business discriminator.
• SET_OF_BOOKS_ID — foreign key to GL_SETS_OF_BOOKS_11I, anchoring the budget group to a specific ledger or set of books.
• PARENT_BUDGET_GROUP_ID and ROOT_BUDGET_GROUP_ID — self-referencing hierarchy columns supporting parent/root relationships among budget groups.
• ROOT_BUDGET_GROUP — additional flag or identifier for the hierarchy root.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — date-range control for the budget group's validity.
• FREEZE_HIERARCHY_FLAG — indicates whether the associated hierarchy is locked.
• NUM_PROPOSED_YEARS — number of proposed budget years associated with the group.
• PS_ACCOUNT_POSITION_SET_ID and NPS_ACCOUNT_POSITION_SET_ID — references to account position sets for personal services and non-personal services.
• BUDGET_GROUP_CATEGORY_SET_ID — links the group to its category set definition.
• BUSINESS_GROUP_ID and ORGANIZATION_ID — standard multi-org and business group context columns.
• SEGMENT1_TYPE through SEGMENT30_TYPE — thirty segment-type columns describing the accounting flexfield structure applied to the group.

Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE) and ATTRIBUTE1–ATTRIBUTE10 plus CONTEXT provide audit and extension support.

Common Use Cases and Queries

The primary use case is identifying and reporting on the budget groups defined for a set of books, including their hierarchical relationships and effective dates. A representative query joining to the ledger is:

• SELECT bg.budget_group_id, bg.name, bg.short_name, bg.budget_group_type, bg.effective_start_date, bg.effective_end_date FROM psb_budget_groups bg WHERE bg.set_of_books_id = :ledger_id AND SYSDATE BETWEEN bg.effective_start_date AND bg.effective_end_date;

Hierarchy traversal uses the self-referencing columns:

• SELECT budget_group_id, name, parent_budget_group_id, root_budget_group_id FROM psb_budget_groups START WITH parent_budget_group_id IS NULL CONNECT BY PRIOR budget_group_id = parent_budget_group_id;

Reporting and integration scenarios commonly resolve budget group names for downstream objects such as worksheets, positions, and revisions by joining on BUDGET_GROUP_ID. Because the module is obsolete, extraction and archival queries are also common — particularly joining PSB_DATA_EXTRACTS and PSB_WS_LINE_BALANCES_I to persist historical budgeting data outside the legacy module.

Related Objects

The FK metadata documents the most significant dependencies. PSB_BUDGET_GROUPS references GL_SETS_OF_BOOKS_11I via SET_OF_BOOKS_ID. The following dependents reference BUDGET_GROUP_ID and represent the principal related objects:

• PSB_BUDGET_GROUP_CATEGORIES — category definitions per budget group (BUDGET_GROUP_ID).
• PSB_BUDGET_GROUP_RESP — responsibility assignments for budget groups (BUDGET_GROUP_ID).
• PSB_BUDGET_REVISIONS and PSB_BUDGET_REVISION_POSITIONS — revision cycles and their positions (BUDGET_GROUP_ID).
• PSB_BUDGET_WORKFLOW_RULES — workflow rules, referencing BUDGET_GROUP_ID and REVIEW_BUDGET_GROUP_ID.
• PSB_WORKSHEETS — budget worksheets belonging to the group (BUDGET_GROUP_ID).
• PSB_POSITION_ACCOUNTS and PSB_POSITIONS — position and account data scoped to the budget group.
• PSB_WS_DISTRIBUTION_RULES, PSB_WS_DISTRIBUTION_DETAILS, and PSB_WS_DISTRIBUTION_RULE_LINES — worksheet distribution rules and details, including distribution to a child group via CHILD_BUDGET_GROUP_ID.
• PSB_SET_RELATIONS and PSB_ACCOUNT_POSITION_SETS — set relationship and account position set definitions (BUDGET_GROUP_ID).
• PSB_DATA_EXTRACTS — extraction records linked to a budget group.

These relationships confirm PSB_BUDGET_GROUPS as the anchoring hub for the obsolete PSB schema and as the preferred entry point for any reporting or migration activity involving legacy public sector budgeting data.