Search Results psb_budget_stage_set_u1

Overview

The PSB_BUDGET_STAGE_SETS table is a core data definition table within the Oracle E-Business Suite Public Sector Budgeting (PSB) module, now marked as obsolete. It serves as a master repository for defining budget stage sets and budget category sets. These sets are foundational control structures that govern the workflow and categorization of budget data throughout the budgeting lifecycle. The table enables organizations to establish standardized, reusable templates for budget preparation, review, and approval stages, ensuring consistency and control across different budgeting processes. Its role is to act as a parent definition object, which is then referenced by transactional and configuration tables to enforce business rules.

Key Information Stored

The table stores the metadata required to define and identify a unique budget stage or category set. Based on the provided metadata, the primary columns include BUDGET_STAGE_SET_ID, which is the unique system-generated identifier serving as the primary key for the table. The NAME column stores the user-defined descriptive name for the set, such as "FY2024 Capital Budget Stages" or "Operating Budget Categories." The STAGE_TYPE column indicates the classification of the set, distinguishing between different types of stages or categories. The combination of STAGE_TYPE and NAME forms a unique key (PSB_BUDGET_STAGE_SET_U1), preventing duplicate definitions. While specific descriptive columns are not listed in the excerpt, such tables typically include additional control columns like CREATION_DATE and LAST_UPDATE_DATE.

Common Use Cases and Queries

A primary use case is the administrative setup and maintenance of the budgeting framework. System administrators query this table to review or audit defined stage sets before deploying a new budget cycle. Common reporting queries involve joining this table to its child tables to list all stages belonging to a specific set. For example, to retrieve all stage sets and their associated stages, a query would join PSB_BUDGET_STAGE_SETS to PSB_BUDGET_STAGES. Another critical use case is troubleshooting integration points, such as identifying which General Ledger interface configuration (PSB_GL_INTERFACES) uses a particular budget stage set. A sample query to list all stage set definitions would be: SELECT budget_stage_set_id, stage_type, name FROM psb_budget_stage_sets ORDER BY name;.

Related Objects

The PSB_BUDGET_STAGE_SETS table has defined foreign key relationships with several other PSB tables, establishing its central role in the data model. The documented relationships are:

• PSB_BUDGET_STAGES: This child table stores the individual stages (e.g., "Department Submission," "Finance Review") that belong to a set. It joins via PSB_BUDGET_STAGES.BUDGET_STAGE_SET_ID = PSB_BUDGET_STAGE_SETS.BUDGET_STAGE_SET_ID.
• PSB_GL_INTERFACES: This configuration table links budget stages to General Ledger interfaces for posting. It references the stage set's identifier via PSB_GL_INTERFACES.BUDGET_STAGE_ID (note: the column name suggests it references a specific stage ID from PSB_BUDGET_STAGES, but the foreign key is documented as pointing to this table's primary key).
• PSB_WORKSHEETS: Budget worksheets are associated with a specific stage set, joined on PSB_WORKSHEETS.STAGE_SET_ID = PSB_BUDGET_STAGE_SETS.BUDGET_STAGE_SET_ID.

These relationships confirm that PSB_BUDGET_STAGE_SETS is a key reference entity for budgeting workflow and configuration.