Results for “psb_budget_year_types_vl”

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

Overview

The view PSB_BUDGET_YEAR_TYPES_VL is an Oracle E-Business Suite public database object owned by the APPS schema and defined within the Public Sector Budgeting (PSB) product family. It presents the set of budget year type definitions that govern how budgeting periods are categorized, sequenced, and labeled within the PSB application. In Oracle EBS Release 12.1.1 and 12.2.2, the _VL suffix denotes a "translated" or language-aware view that joins a base (non-translated) entity table to its corresponding translation table, returning descriptive attributes in the session's current language. The view is documented as VALID in the ETRM repository and is classified as a VIEW object type.

Its role in reporting and integration is to expose denormalized, user-readable budget year type data alongside the stable primary key and audit columns needed for downstream processing. Because PSB budgeting structures rely on year types to classify budget years (for example, appropriation, fiscal, or project-based categories), this view is a convenient source for concurrent programs, BI Publisher reports, and custom integrations that must resolve descriptive names and descriptions without manually joining the translation table.

Underlying Base Objects

As documented, the view is defined over two PSB tables:

• PSB_BUDGET_YEAR_TYPES (aliased BYTP) — the base entity table holding the unique BUDGET_YEAR_TYPE_ID, the YEAR_CATEGORY_TYPE, SEQUENCE_NUMBER, and the standard audit columns (creation and last-update information).
• PSB_BUDGET_YEAR_TYPES_TL (aliased BTL) — the translation table storing the language-specific NAME and DESCRIPTION, keyed by BUDGET_YEAR_TYPE_ID and LANGUAGE.

The two tables are joined on BUDGET_YEAR_TYPE_ID, restricted to the row whose LANGUAGE matches USERENV('LANG'), ensuring descriptions are returned in the session language. The view also projects BYTP.ROWID as ROW_ID. Note that while the ETRM 12.2.2 metadata lists no explicitly documented referenced base objects, the view text itself confirms the relationship above, and this pattern is standard for PSB translated views. The view is effectively a many-to-one projection: each base year type row is combined with exactly one translation row for the active language.

Key Columns

• ROW_ID — the ROWID of the underlying PSB_BUDGET_YEAR_TYPES row, useful for row-level addressing or updates.
• BUDGET_YEAR_TYPE_ID — the surrogate primary key uniquely identifying each budget year type; the primary join and reference key.
• NAME — the translated display name of the budget year type (from the _TL table).
• DESCRIPTION — the translated descriptive text for the year type.
• YEAR_CATEGORY_TYPE — the category classification assigned to the year type, used by PSB logic to group or filter budget years.
• SEQUENCE_NUMBER — controls the display or processing order of year types.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording the most recent modification.
• CREATED_BY, CREATION_DATE — standard audit columns recording row creation.

The absence of _TL-specific columns such as LANGUAGE or SOURCE_LANG reflects that the view filters to a single language rather than exposing multi-language rows.

Common Use Cases and Queries

Typical uses include validating year type setup during PSB configuration, populating LOVs or report parameters with descriptive names, and joining year type identifiers to budget transaction data for reporting. A standard query returns all defined year types in the session language, ordered for presentation:

• SELECT budget_year_type_id, name, description, year_category_type, sequence_number FROM apps.psb_budget_year_types_vl ORDER BY sequence_number;
• SELECT budget_year_type_id, name FROM apps.psb_budget_year_types_vl WHERE year_category_type = :p_category;
• SELECT name, last_update_date, last_updated_by FROM apps.psb_budget_year_types_vl WHERE budget_year_type_id = :p_id;

Because the view enforces the USERENV('LANG') restriction, queries automatically return descriptions in the user's language, which simplifies localization for reports and integrations. When referencing the view from custom code, always qualify it with the APPS schema and grant appropriate privileges, as the object resides in the APPS schema in both 12.1.1 and 12.2.2.