Results for “budget_calendar_id”

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

Overview

PSBFV_BUDGET_YEARS is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PSB (Public Sector Budgeting) product family. The view presents the budget year definitions maintained within Oracle Public Sector Budgeting, exposing each year-level record together with its parent budget calendar and its assigned budget year type. Because the view is defined WITH READ ONLY, it supports query and reporting access only; all maintenance of the underlying data must be performed through the base PSB tables or the application forms that populate them.

Functionally, the view answers the question of which budget years exist within a given budget calendar, along with descriptive and effective-dating attributes for each year. It is commonly used in reporting, concurrent program queries, and integration extract logic where a denormalized, human-readable budget year listing is required without joining the calendar and year type tables manually. The presence of descriptive flexfield and lookup columns embedded in the SELECT list indicates that the view was designed for use with an Oracle Forms or OA Framework "lov" style query, as the underscore-prefixed columns supply lookup metadata and flexfield context to the runtime.

Underlying Base Objects

The view is defined over three PSB tables:

• PSB_BUDGET_PERIODS (BP1) — the driving table, aliased BP1. The view restricts this table to rows where BUDGET_PERIOD_TYPE = 'Y', meaning only period records that represent a full budget year are included; period-level and other period type rows are excluded.
• PSB_BUDGET_CALENDARS (BC) — joined on BP1.BUDGET_CALENDAR_ID = BC.BUDGET_CALENDAR_ID, supplying the budget calendar name.
• PSB_BUDGET_YEAR_TYPES (BYTP1) — joined on BYTP1.BUDGET_YEAR_TYPE_ID = BP1.BUDGET_YEAR_TYPE_ID, supplying the year category type and the year type name.

The join structure is an inner join across all three tables, so a budget year appears in the view only when a valid budget calendar and a valid budget year type are resolvable. The ETRM metadata lists no additional referenced base objects beyond these three PSB tables.

Key Columns

• BUDGET_YEAR_ID — maps to BP1.BUDGET_PERIOD_ID; the primary identifier of the budget year record within PSB_BUDGET_PERIODS.
• BUDGET_CALENDAR_ID — the foreign key linking the budget year to its owning budget calendar. This column is the direct target of the search term "budget_calendar_id" and is the standard predicate for filtering budget years by calendar.
• BUDGET_CALENDAR_NAME — the descriptive name of the calendar from PSB_BUDGET_CALENDARS.
• BUDGET_YEAR_TYPE_ID and BUDGET_YEAR_TYPE_NAME — the identifier and name of the year type assigned to the year.
• BUDGET_YEAR_TYPE — maps to BYTP1.YEAR_CATEGORY_TYPE, categorizing the year type.
• BUDGET_YEAR_NAME and BUDGET_YEAR_DESCRIPTION — mapped from BP1.NAME and BP1.DESCRIPTION.
• START_EFFECTIVE_DATE and END_EFFECTIVE_DATE — mapped from BP1.START_DATE and BP1.END_DATE, defining the active window of the budget year.
• _LA:PERIOD_DISTRIBUTION_TYPE and _LA:CALCULATION_PERIOD_TYPE — lookup attribute columns resolving values from FND_LOOKUPS using the PSB_PERIOD_DISTRIBUTION_TYPES and PSB_CALCULATION_PERIOD_TYPES lookup types respectively.
• _DF — descriptive flexfield context marker referencing PSB_BUDGET_PERIODS:BP1.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard audit columns inherited from PSB_BUDGET_PERIODS.

Common Use Cases and Queries

The most frequent use is retrieving all budget years that belong to a particular budget calendar, typically when a form or report must restrict a list of values to the calendar currently selected by the user.

SELECT budget_year_id,
       budget_year_name,
       budget_calendar_id,
       budget_calendar_name,
       budget_year_type_name,
       start_effective_date,
       end_effective_date
  FROM apps.psbfv_budget_years
 WHERE budget_calendar_id = :p_budget_calendar_id
 ORDER BY start_effective_date;

A second scenario returns the distinct calendars that have at least one active budget year defined, which is useful when validating calendar setup or presenting calendar selection lists.

SELECT DISTINCT budget_calendar_id, budget_calendar_name
  FROM apps.psbfv_budget_years
 ORDER BY budget_calendar_name;

A third scenario filters budget years by year type category, for example to isolate operating versus capital years, or to report years whose effective date range covers a supplied date.

SELECT budget_year_name, budget_year_type_name
  FROM apps.psbfv_budget_years
 WHERE budget_calendar_id = :p_budget_calendar_id
   AND TRUNC(:p_as_of_date) BETWEEN start_effective_date
                                AND end_effective_date;

Because the view is read-only and carries no bind variables or security predicates of its own, callers should apply the appropriate operating unit or responsibility-level filtering in their own SQL where required.