Results for “budget_year_type_id”

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

Overview

PSBBV_BUDGET_YEARS is a read-only view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Public Sector Budgeting (PSB) product family, the module responsible for budget formulation, position budgeting, and budget book publishing in public sector deployments. The view exposes budget year definitions — the top-level calendrical containers under which budget periods, budget organizations, and budget lines are organized.

The view is defined with a WITH READ ONLY clause, so it is intended strictly for queries and reporting integrations, not for DML. Its principal role is to provide a clean, denormalized presentation of budget year records to forms, concurrent programs, and external reporting tools without exposing the entire transaction-oriented structure of the underlying period table. The user-facing name of the entity appears as BUDGET_YEAR_NAME, which is why searches for "budget_year_name" surface this object.

Underlying Base Objects

The view is defined over a single documented base object, PSB_BUDGET_PERIODS (aliased BP1 in the view text). No other base objects are documented. Every column returned by PSBBV_BUDGET_YEARS is derived from PSB_BUDGET_PERIODS; the view applies a single filter predicate:

• BP1.BUDGET_PERIOD_TYPE = 'Y' — restricting rows to those representing a year-level period rather than a sub-period (typically 'P' for periods).

Because PSB_BUDGET_PERIODS stores both years and the periods nested beneath them in one table, this view isolates the year hierarchy. The relationships to budget period, budget organization, and budget line tables flow through BUDGET_PERIOD_ID, which the view exposes as BUDGET_YEAR_ID. Note that the ETRM metadata does not document foreign keys or additional join objects; the association to child periods must be inferred from the BUDGET_PERIOD_ID column.

Key Columns

• BUDGET_YEAR_NAME — the descriptive identifier of the budget year (mapped from BP1.NAME). This is the primary searchable attribute.
• BUDGET_YEAR_DESCRIPTION — free-text description (from BP1.DESCRIPTION).
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — the date boundaries of the budget year (from BP1.START_DATE and BP1.END_DATE).
• BUDGET_YEAR_ID — the surrogate key of the year record (from BP1.BUDGET_PERIOD_ID), used as the join key to period and budget detail tables.
• BUDGET_YEAR_TYPE_ID — identifies the budget year type classification.
• "_LA:PERIOD_DISTRIBUTION_TYPE" and "_LA:CALCULATION_PERIOD_TYPE" — descriptive quick picks resolved from FND_LOOKUPS against PSB_PERIOD_DISTRIBUTION_TYPES and PSB_CALCULATION_PERIOD_TYPES respectively. These are value-set display columns rather than stored IDs.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, providing standard EBS who-columns.

Common Use Cases and Queries

Typical uses include budget year lookup lists in custom forms, validation of year ranges before loading budget data, and reporting extracts that require the year name alongside its effective dates.

Listing all active budget years:

• SELECT budget_year_id, budget_year_name, start_effective_date, end_effective_date FROM apps.psbbv_budget_years ORDER BY start_effective_date DESC;

Resolving a year by name:

• SELECT budget_year_id, budget_year_name FROM apps.psbbv_budget_years WHERE budget_year_name = :p_year_name;

Joining to period-level data using the exposed key:

• SELECT y.budget_year_name, p.name period_name FROM apps.psbbv_budget_years y, apps.psb_budget_periods p WHERE p.budget_period_id = y.budget_year_id AND p.budget_period_type = 'P';

Because the view is READ ONLY, integrations should direct any maintenance of budget year definitions to the PSB Public Sector Budgeting setup forms and underlying PSB_BUDGET_PERIODS API, reserving PSBBV_BUDGET_YEARS for query access only.