Search Results psb_budget_calendars_u1

Overview

The PSB_BUDGET_CALENDARS table is a core data structure within the Oracle E-Business Suite (EBS) module Public Sector Budgeting (PSB), which is designated as obsolete in releases 12.1.1 and 12.2.2. This table serves as the master repository for defining budget calendars, which are fundamental frameworks for organizing the fiscal timeline of a public sector entity. A budget calendar establishes the schedule of key budgetary events, deadlines, and periods throughout a fiscal cycle, governing the workflow for budget preparation, review, approval, and execution. Its primary role is to act as a parent entity, providing a unique identifier and name for each calendar that is then referenced by subordinate tables defining specific periods and activities.

Key Information Stored

Based on the provided ETRM metadata, the table's structure centers on two key columns that form its primary keys. The BUDGET_CALENDAR_ID column is a unique system-generated identifier (likely a sequence number) serving as the primary key for relational integrity and programmatic reference. The NAME column holds the unique descriptive title of the budget calendar (e.g., "FY25 Operating Budget Calendar" or "Capital Budget Cycle 2024") and is also defined as a unique key (PSB_BUDGET_CALENDARS_U1) to prevent duplicates. While the excerpt does not list additional columns, typical attributes for such a table could include descriptive fields, status indicators, effective dates, and links to a specific ledger or set of books.

Common Use Cases and Queries

The primary use case is the setup and maintenance of the budgetary fiscal timeline. Administrators would use this table to create and name distinct calendars for different budget types or fiscal years. Common reporting and validation queries would involve joining this table to its child tables to analyze the complete calendar structure. A fundamental SQL pattern retrieves all defined calendars:

SELECT budget_calendar_id, name FROM psb_budget_calendars ORDER BY name;

To analyze the relationship with its child periods, a typical join query would be:

SELECT cal.name AS calendar_name, per.* FROM psb_budget_calendars cal, psb_budget_periods per WHERE cal.budget_calendar_id = per.budget_calendar_id;

Given the module's obsolete status, common operational use cases would be limited to supporting legacy data, historical reporting, and migration activities.

Related Objects

The ETRM documentation specifies a clear, singular foreign key relationship where PSB_BUDGET_CALENDARS is referenced as a parent table. The related object is:

• Table: PSB_BUDGET_PERIODS - This child table stores the individual time periods (e.g., "Department Submission," "Council Review," "Q1 Execution") that constitute a budget calendar. It references PSB_BUDGET_CALENDARS via the foreign key column PSB_BUDGET_PERIODS.BUDGET_CALENDAR_ID, which joins to PSB_BUDGET_CALENDARS.BUDGET_CALENDAR_ID. This relationship enforces that every budget period must be associated with a valid, pre-defined budget calendar.