Results for “psb_budget_calendars”

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

Overview

PSB_BUDGET_CALENDARS is a table within the PSB (Public Sector Budgeting) product family in Oracle EBS 12.1.1 and 12.2.2. Its documented description is "Budget calendar information," which identifies it as the master definition table for budgeting calendars used to organize budget periods and budgeting cycles. Each row in this table represents a discrete budget calendar — a named container that groups one or more budget periods under a single identifier. In the ETRM documentation this object is flagged as Obsolete and "Not implemented in this database," meaning the table is documented for reference but is not actively populated or maintained in the current environment. From a Data Vault modeling perspective, the mined relationships suggest a hub-leaning classification. The table carries a single-column surrogate primary key and is referenced by a dependent child table, consistent with a hub entity that anchors the identity of budget calendars while descriptive attributes could be split into a satellite.

Key Information Stored

The documented physical schema for PSB_BUDGET_CALENDARS contains 19 columns owned by the PSB schema. The most significant columns are:

• BUDGET_CALENDAR_ID — the surrogate primary key defined by the PSB_BUDGET_CALENDARS_PK constraint. This is the value propagated to child records as a foreign key.
• NAME — the business-key candidate enforced by the unique index PSB_BUDGET_CALENDARS_U1 is BUDGET_CALENDAR_ID, while PSB_BUDGET_CALENDARS_U2 uniquely enforces NAME. NAME therefore acts as the human-readable unique identifier for a calendar.
• DESCRIPTION — free-text elaboration of the calendar's purpose or scope.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing who last changed the record and when.
• CREATED_BY, CREATION_DATE — creation audit columns.
• ATTRIBUTE1 through ATTRIBUTE10 — ten descriptive flexfield (DFF) columns reserved for customer-specific extension of calendar metadata.
• CONTEXT — the DFF context column that determines which attribute segments are active.

The separation of a surrogate key (BUDGET_CALENDAR_ID) from two unique business keys (BUDGET_CALENDAR_ID, NAME) reflects a classic identity-versus-natural-key split suitable for a Data Vault hub with a business-key satellite.

Common Use Cases and Queries

Because the object is obsolete and not implemented, production reporting against it is unlikely. However, for historical migration analysis, documentation, or decommissioning assessments, several query patterns apply. Listing all defined calendars:

• SELECT budget_calendar_id, name, description FROM psb_budget_calendars ORDER BY name;
• Resolving a calendar by its business key: SELECT * FROM psb_budget_calendars WHERE name = :name;
• Counting periods attached to each calendar, joining down to the child table: SELECT c.name, COUNT(p.budget_period_id) FROM psb_budget_calendars c JOIN psb_budget_periods p ON p.budget_calendar_id = c.budget_calendar_id GROUP BY c.name;
• Audit trail review: SELECT budget_calendar_id, name, last_updated_by, last_update_date FROM psb_budget_calendars WHERE last_update_date > SYSDATE - 90;

Typical scenarios include validating calendar-to-period completeness before a budgeting cycle, reconciling calendar names between legacy PSB and successor modules, and documenting extension usage through the ATTRIBUTE1–10 and CONTEXT columns.

Related Objects

The documented foreign-key relationship shows one dependent object referencing this table:

• PSB_BUDGET_PERIODS — the child table whose BUDGET_CALENDAR_ID column references PSB_BUDGET_CALENDARS, forming a parent-child relationship between calendars and their constituent periods.

The primary-key constraints PSB_BUDGET_CALENDARS_PK and unique indexes PSB_BUDGET_CALENDARS_U1 and PSB_BUDGET_CALENDARS_U2 define the object's identity and enforce uniqueness on BUDGET_CALENDAR_ID and NAME. The table's DFF columns (ATTRIBUTE1–10, CONTEXT) imply dependency on Oracle EBS flexfield infrastructure. Any integration or migration touching PSB budgeting data must traverse PSB_BUDGET_CALENDARS as the root of the calendar-to-period hierarchy.