Search Results budget_calendar_name




Overview
Explore in AI Chat

Overview

PSBBV_BUDGET_CALENDARS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It is registered under the FND Design Data identifier PSB.PSBBV_BUDGET_CALENDARS and holds VALID status in both the 12.1.1 and 12.2.2 releases. The view presents budget calendar definitions maintained within the Public Sector Budgeting (PSB) product family, exposing each calendar's name, description, and surrogate primary key alongside the standard Oracle WHO audit columns. Because users and integrators frequently search for the column budget_calendar_name, this view is typically the entry point for identifying which budget calendars exist in an environment before joining to period or budget line data.

The view serves a denormalization and simplification role: rather than querying the base PSB table directly, report authors, Discoverer workbooks, and interface programs can consume a stable, read-only projection. It is intended for reporting and downstream integration rather than transactional write operations, and as a BIS view it is populated from the underlying PSB entity that stores calendar definitions.

Underlying Base Objects

The view is defined over the base object APPS.PSBBV_BUDGET_CALENDARS references APPS.PSB_BUDGET_CALENDARS. PSB_BUDGET_CALENDARS is the PSB transactional table that persists the budget calendar header records, including the calendar identifier, its user-facing name, description, and WHO audit attributes. The view simply projects those columns upward without aggregation or filtering, so the row count and cardinality of the view mirror the base table.

No further schema-level dependencies are documented. The view is not referenced by any other database object, meaning it is a terminal consumer object with no upstream views, synonyms, or PL/SQL packages depending on it. This makes it safe to query in ad hoc reporting without concerns about invalidating other compiled objects, though it also means the view must be accessed directly by its fully qualified name.

Key Columns

  • BUDGET_CALENDAR_NAME (VARCHAR2(30)) — The user-assigned name of the budget calendar. This is the most frequently searched attribute and typically the value end users recognize in forms and reports.
  • BUDGET_CALENDAR_DESCRIPTION (VARCHAR2(80)) — Free-text description providing additional context about the calendar's purpose or scope.
  • BUDGET_CALENDAR_ID (NUMBER(20)) — The unique surrogate identifier for the calendar. This is the primary join key to any table that references a budget calendar.
  • LAST_UPDATE_DATE (DATE) — Standard WHO column recording the last modification timestamp.
  • LAST_UPDATED_BY (NUMBER(15)) — Standard WHO column identifying the user who last modified the record.
  • CREATED_BY (NUMBER(15)) — Standard WHO column identifying the creating user.
  • CREATION_DATE (DATE) — Standard WHO column recording the record creation timestamp.

The WHO columns allow report authors to filter by maintenance window or trace records back to a responsible user via FND_USER.

Common Use Cases and Queries

Typical scenarios include validating a budget calendar name supplied in an interface file, building a list of values for custom reports, and mapping calendar names to identifiers for downstream joins. The canonical query is:

SELECT BUDGET_CALENDAR_NAME, BUDGET_CALENDAR_DESCRIPTION, BUDGET_CALENDAR_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE FROM APPS.PSBBV_BUDGET_CALENDARS;

To locate a specific calendar by the commonly searched name, restrict with a predicate such as WHERE BUDGET_CALENDAR_NAME = :p_name. To audit recent maintenance, add WHERE LAST_UPDATE_DATE >= SYSDATE - 30 and resolve LAST_UPDATED_BY through FND_USER. For integrations, select BUDGET_CALENDAR_ID keyed on name to translate inbound values into the identifiers expected by PSB budget line tables.