Results for “gl_bud_period_ranges_v”

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

Overview

GL_BUD_PERIOD_RANGES_V is a General Ledger (GL) view owned by the APPS schema and documented with a VALID status in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM description for this object is the terse notation "10SC ONLY," indicating that its functional relevance is scoped to a specific localization or deployment context rather than general availability. Despite its narrow documentation, the view surfaces budget period range data that reporting, integration, and validation logic can consume without joining the underlying budget tables directly.

The view exposes one row per budget period range defined for a budget version, combining budget-version identifiers and descriptive names with the period-year, period range boundaries, and an OPEN_FLAG indicator. Because the OPEN_FLAG column is a first-class attribute of this view, it is directly relevant to queries that need to determine whether a given budget period range is open or closed for a budget version.

Underlying Base Objects

The view is defined over two documented base objects, both exposed in the APPS schema as synonyms:

• GL_BUDGET_PERIOD_RANGES — the primary source, aliased as P, supplying the period-year, period range, open flag, and audit columns.
• GL_BUDGET_VERSIONS — aliased as V, joined on BUDGET_VERSION_ID to resolve the budget name.

The defining query joins GL_BUDGET_PERIOD_RANGES P to GL_BUDGET_VERSIONS V on V.BUDGET_VERSION_ID = P.BUDGET_VERSION_ID. The view therefore inherits its grain from GL_BUDGET_PERIOD_RANGES: each row represents a single budget version / period year / period range combination. The join is an equi-join with no outer join specified, so a period range row is returned only when its BUDGET_VERSION_ID resolves to a budget version in GL_BUDGET_VERSIONS. ROW_ID is derived from P.ROWID, preserving the physical row identity of the base period range record.

Key Columns

• ROW_ID — the ROWID of the underlying GL_BUDGET_PERIOD_RANGES row.
• BUDGET_VERSION_ID — the budget version key linking the period range to its budget.
• BUDGET_NAME — the budget name sourced from GL_BUDGET_VERSIONS.
• PERIOD_YEAR — the accounting period year to which the range applies.
• START_PERIOD_NAME / START_PERIOD_NUM — the name and numeric identifier of the range's starting period.
• END_PERIOD_NAME / END_PERIOD_NUM — the name and numeric identifier of the range's ending period.
• OPEN_FLAG — indicates whether the budget period range is open (typically Y) or closed (typically N) for maintenance.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — standard EBS audit columns for the base row.

Common Use Cases and Queries

Typical uses include determining which budget period ranges remain open for a budget version, validating period boundaries before budget entry, and feeding integration or reporting logic that must respect open periods. A representative query to list open ranges for a budget:

SELECT budget_name, period_year, start_period_name,
       end_period_name, open_flag
FROM   apps.gl_bud_period_ranges_v
WHERE  open_flag = 'Y'
ORDER  BY budget_name, period_year, start_period_num;

To inspect the full range definition for a specific budget version:

SELECT budget_name, period_year, start_period_num,
       end_period_num, last_update_date, last_updated_by
FROM   apps.gl_bud_period_ranges_v
WHERE  budget_version_id = :budget_version_id;

As a read-only, APPS-owned view, GL_BUD_PERIOD_RANGES_V should not be used for direct updates; modifications to period ranges and open flags must be performed against the underlying budget maintenance functionality. Because the ETRM description is limited to "10SC ONLY," implementers should confirm applicability in their specific deployment before relying on the object in production integrations.