Results for “budget_period_description”

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

Overview

PSBBV_BUDGET_PERIODS is a read-only Oracle EBS view owned by the APPS schema and associated with the Public Sector Budgeting (PSB) product family. It exposes budget period definitions used by budgetary control and budget preparation flows, presenting a denormalized, human-readable projection of the underlying budget period records. Rather than requiring reports and integrations to join the base table and translate internal identifiers, this view surfaces descriptive attributes such as the period name and description alongside the surrogate key and effective date range.

The view is defined with a WITH READ ONLY clause, so it is intended strictly for query and reporting purposes. The budget_period_name column is the primary searchable descriptor for consumers who need to resolve a period label into its identifier, or to enumerate valid budget periods for a given budget year. The view plays a supporting role in reporting layers, extracts, and custom concurrent programs that must reference budget periods by name rather than by internal ID.

Underlying Base Objects

The documented view metadata identifies no referenced base objects, but the view text reveals the dependency explicitly: it selects from PSB_BUDGET_PERIODS BP. That single base table is the sole source of columns exposed by the view. The projection maps base columns to view columns, with BP.NAME becoming BUDGET_PERIOD_NAME, BP.DESCRIPTION becoming BUDGET_PERIOD_DESCRIPTION, and the effective date fields corresponding to START_DATE and END_DATE in the base table.

Identifiers such as BUDGET_PERIOD_ID and PARENT_BUDGET_PERIOD_ID are carried through unchanged, supporting hierarchical relationships between budget periods. Standard EBS audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, and CREATION_DATE — are also exposed. Because the view is a straight projection over one table, it inherits the base table's row-level access and does not itself apply additional filtering.

Key Columns

• BUDGET_PERIOD_NAME — the descriptive name of the budget period; the primary column of interest for searches such as "budget_period_name".
• BUDGET_PERIOD_DESCRIPTION — a longer textual description of the period.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — the effective date boundaries of the period.
• BUDGET_PERIOD_ID — the unique surrogate key for the period, used as a foreign key reference elsewhere.
• BUDGET_YEAR_ID — the associated budget year identifier.
• BUDGET_YEAR_ID, PARENT_BUDGET_PERIOD_ID — support hierarchical relationships between budget periods.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard audit columns.

Common Use Cases and Queries

Typical uses include resolving a period name to its identifier for budget entry programs, validating period names in custom uploads, and populating LOV-style lists in custom forms or reports.

Enumerate all budget periods:

SELECT budget_period_name, budget_period_id, budget_year_id
FROM   apps.psbbv_budget_periods
ORDER BY budget_period_name;

Resolve a specific period by name:

SELECT budget_period_id, budget_year_id, start_effective_date, end_effective_date
FROM   apps.psbbv_budget_periods
WHERE  budget_period_name = :p_period_name;

Incremental extraction using audit columns:

SELECT budget_period_name, budget_period_id, last_update_date
FROM   apps.psbbv_budget_periods
WHERE  last_update_date >= :p_since;

Because the view is read-only, all maintenance must target the base table through supported PSB APIs. Queries should be schema-qualified against APPS and filtered where possible to limit full scans in large implementations.