Results for “open_flag”

50+ results




Overview
Explore in AI Chat

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

Overview

GL_BUDGET_PERIOD_RANGES is a General Ledger table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 schema, owned by the GL schema. It stores the status of budget period ranges, specifically recording whether a defined range of accounting periods within a budget version is open or not open for budget entry. In the budgeting workflow, a budget version defines the set of accounts and periods that will be budgeted; this table determines, for each budget version, which periods within a fiscal year are available for budgeting activity.

The table is referenced primarily in the context of budget entry and budget inquiry, where the open flag controls whether a user may enter or modify budget amounts for a given period. From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning. This heuristic suggests that the table functions as a satellite attached to the central business key represented by the budget version, capturing the descriptive and mutable state (open vs. not open) of period ranges over time, rather than serving as an independent hub or linking two hubs.

Key Information Stored

The table contains nine documented columns and is uniquely identified by the index GL_BUDGET_PERIOD_RANGES_U1, a business-key candidate defined over BUDGET_VERSION_ID, PERIOD_YEAR, and START_PERIOD_NUM. The primary key constraint, GL_BUDGET_PERIOD_RANGES_PK, is composed of BUDGET_VERSION_ID, PERIOD_YEAR, and START_PERIOD_NUM, so in this case the surrogate and business key coincide.

  • BUDGET_VERSION_ID — Identifies the budget version to which the period range belongs; foreign key to GL_BUDGET_VERSIONS.
  • PERIOD_YEAR — The fiscal year associated with the period range.
  • START_PERIOD_NAME / START_PERIOD_NUM — The name and numeric identifier of the first period in the range.
  • END_PERIOD_NAME / END_PERIOD_NUM — The name and numeric identifier of the last period in the range.
  • OPEN_FLAG — Indicates whether the period range is open or not open for budget entry.
  • LAST_UPDATE_DATE — The date and time of the last modification to the row.
  • LAST_UPDATED_BY — The user who last updated the row.

Common Use Cases and Queries

A frequent scenario is determining which periods are open for budget entry within a specific budget version and fiscal year. For example, a query might join GL_BUDGET_PERIOD_RANGES to GL_BUDGET_VERSIONS to report the open ranges for an active budget:

  • SELECT b.NAME, r.PERIOD_YEAR, r.START_PERIOD_NAME, r.END_PERIOD_NAME, r.OPEN_FLAG FROM GL_BUDGET_PERIOD_RANGES r JOIN GL_BUDGET_VERSIONS b ON b.BUDGET_VERSION_ID = r.BUDGET_VERSION_ID WHERE r.PERIOD_YEAR = :p_year AND r.OPEN_FLAG = 'Y'.
  • Reporting the count of open ranges per budget version to assess budgeting readiness across multiple versions.
  • Auditing changes by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent modifications to period ranges.

Related Objects

  • GL_BUDGET_VERSIONS — Referenced by the foreign key GL_BUDGET_PERIOD_RANGES.BUDGET_VERSION_ID. This is the principal parent object.
  • GL_BUDGET_ENTRIES — Contains the budget amounts entered within the periods whose open status is governed by this table.
  • GL_PERIODS — Provides the period names and numbers referenced by START_PERIOD_NAME, END_PERIOD_NAME, and their numeric counterparts.
  • GL_BUDGET_ASSIGNMENTS — Associates accounts and ranges with budget definitions, often queried alongside period range status.
  • GL_BUDGET_TYPES — Defines the budget type context in which a version and its period ranges operate.

These objects, together with the standard GL budget entry forms and concurrent programs, form the dependency chain in which GL_BUDGET_PERIOD_RANGES controls period-level budgeting availability.