Results for “gl_budget_range_interim”

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

Overview

GL.GL_BUDGET_RANGE_INTERIM is a General Ledger interim (temporary staging) table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold budget balances entered through the Enter Budget Amounts and Enter Budget Journals forms before those entries are validated, processed, and ultimately posted to the definitive budget balances and journal tables. Because the object serves purely as a working area for an in-progress data entry session, rows are transient in nature and are not intended to represent the durable, historical record of budget activity.

The table is owned by the GL schema and is classified as VALID. From a Data Vault modeling perspective, the heuristic derived from its foreign key structure suggests a link classification: the object is anchored by multiple foreign keys that reference surrounding dimensions and parent entities (ledger, account, budget version, budget entity, period type, and currency), so it behaves less like a standalone hub or descriptive satellite and more like an associative staging structure joining those references. This is a modeling suggestion only; the physical object is a classic Oracle EBS interface table.

Key Information Stored

The table contains 100 documented columns. The most significant fall into four groups: identifying keys, period/amount buckets, account (flexfield) segments, and audit columns.

• LEDGER_ID — identifies the ledger against which the budget entry is being made; a business-key candidate in combination with the account and budget version.
• CODE_COMBINATION_ID — the account combination being budgeted; foreign key to GL_CODE_COMBINATIONS.
• BUDGET_VERSION_ID and BUDGET_ENTITY_ID — the budget version and budget entity (organization) governing the entry; foreign keys to GL_BUDGET_VERSIONS and GL_BUDGET_ENTITIES.
• CURRENCY_CODE — the entered currency; foreign key to FND_CURRENCIES.
• PERIOD_YEAR, PERIOD_TYPE, START_PERIOD_NAME, START_PERIOD_NUM — define the fiscal year, period type, and starting period of the entry range.
• PERIOD1_AMOUNT through PERIOD13_AMOUNT — the entered budget amounts distributed across up to thirteen periods.
• OLD_PERIOD1_AMOUNT through OLD_PERIOD13_AMOUNT — the pre-existing amounts, retained for change comparison and audit during entry.
• DR_FLAG and STAT_AMOUNT1 through STAT_AMOUNT13 — the debit/credit indicator and statistical amounts.
• SEGMENT1 through SEGMENT30 — the denormalized account flexfield segments captured at entry time.
• ACCOUNT_TYPE, STATUS_NUMBER, JE_DRCR_SIGN_REFERENCE, and JE_LINE_DESCRIPTION1–JE_LINE_DESCRIPTION13 — supporting attributes describing account classification, processing status, journal sign, and line descriptions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

No separate surrogate primary key is documented in the ETRM excerpt; the effective unique business key is the combination of ledger, account combination, budget version/entity, and period range.

Common Use Cases and Queries

Because this is an interim table, its primary production use case is diagnostic: investigating rows left behind by a failed or abandoned budget-entry session, or reconciling what a user entered against what was posted. Typical queries include:

• Listing all staged entries for a ledger and budget version, summing the period amounts, to confirm a bulk upload before posting.
• Comparing PERIODn_AMOUNT against OLD_PERIODn_AMOUNT to identify changed periods in a re-entry scenario.
• Checking for orphaned or stuck rows by joining back to the parent entities to validate referential integrity before cleanup.

A representative pattern compares staged amounts to the stored balances:

• SELECT ledger_id, code_combination_id, budget_version_id, budget_entity_id, period1_amount, old_period1_amount FROM gl_budget_range_interim WHERE ledger_id = :ledger_id;

Reporting should never depend on this table for historical figures; verified budget data belongs in the permanent budget balance tables.

Related Objects

The documented foreign keys reveal the objects on which this table depends:

• GL_CODE_COMBINATIONS — joined via CODE_COMBINATION_ID; supplies the account.
• GL_BUDGET_VERSIONS — joined via BUDGET_VERSION_ID; the active budget version.
• GL_BUDGET_ENTITIES — joined via BUDGET_ENTITY_ID; the budget organization.
• GL_PERIOD_TYPES — joined via PERIOD_TYPE; the calendar period type used for entry.
• FND_CURRENCIES — joined via CURRENCY_CODE; the entered currency.

The LEDGER_ID reference points to the ledger definition (for example GL_LEDGERS). In practice, the Enter Budget Amounts and Enter Budget Journals forms and their associated budget-entry concurrent programs are the primary consumers that populate and consume these interim rows.