Results for “obsolete_consolidation_flag”

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

Overview

GL_CONSOLIDATION_HISTORY is a General Ledger (GL) application table that stores the historical record of consolidation runs performed within Oracle E-Business Suite. Each row captures a discrete consolidation execution, recording the source and target periods, currencies, budget context, method flags, and the operational status of the run. It is the primary audit and traceability object for enterprises that consolidate multiple ledgers or balance sheet accounts into a single reporting entity, and it is essential for reconstructing what was consolidated, when, and under which parameters across both Release 12.1.1 and 12.2.2.

The table is owned by the GL schema and is marked VALID. Its documented physical schema in Release 12.2.2 contains 31 columns. Under a heuristic Data Vault classification mined from its foreign key structure, GL_CONSOLIDATION_HISTORY is best modeled as a link table. This is a modeling suggestion rather than an Oracle-imposed design: the table sits at the intersection of consolidation definitions, consolidation sets, currencies, and budget versions, and each row associates those reference entities with a point-in-time run event. It should not be treated as a pure hub, since it does not carry a single immutable business key distinct from its relationships, nor as a satellite, because it records the run event itself rather than descriptive attributes of one parent.

Key Information Stored

The table carries a composite surrogate primary key defined by GL_CONSOLIDATION_HISTORY_PK over CONSOLIDATION_RUN_ID and TO_PERIOD_NAME. A documented unique index, GL_CONSOLIDATION_HISTORY_U1, is defined on the inverse column order (TO_PERIOD_NAME, CONSOLIDATION_RUN_ID), making these two columns the effective business-key candidates for the consolidation run. The most significant columns include:

• CONSOLIDATION_RUN_ID — Surrogate identifier for a single consolidation execution; part of the primary key.
• TO_PERIOD_NAME — Target accounting period of the run; part of the primary key and unique index.
• FROM_PERIOD_NAME — Source accounting period from which balances are drawn.
• CONSOLIDATION_ID — Foreign key to GL_CONSOLIDATION, identifying the consolidation definition used.
• CONSOLIDATION_SET_ID — Foreign key to GL_CONSOLIDATION_SETS, identifying the grouping of ledgers or accounts consolidated.
• TO_CURRENCY_CODE — Foreign key to FND_CURRENCIES, defining the target reporting currency.
• FROM_BUDGET_NAME / FROM_BUDGET_VERSION_ID — Source budget context, with the version referencing GL_BUDGET_VERSIONS.
• TO_BUDGET_NAME / TO_BUDGET_VERSION_ID — Target budget context, likewise referencing GL_BUDGET_VERSIONS.
• ACTUAL_FLAG — Indicates whether the run consolidated actual balances or budget balances.
• METHOD_FLAG — The consolidation method applied to the run.
• RUN_EASYLINK_FLAG — Whether the run triggered the EasyLink consolidation transmission.
• AVERAGE_CONSOLIDATION_FLAG / AVERAGE_TO_PERIOD_NAME — Indicate and name the averaging period where average balance consolidation is used.
• STATUS — Outcome state of the consolidation run.
• REQUEST_ID, GROUP_ID, JE_BATCH_ID — Concurrency request, grouping, and journal batch linkage for downstream processing.
• OBSOLETE_CONSOLIDATION_FLAG — Marks runs that have been superseded and should be ignored in reporting.

Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present, along with technique columns such as RUN_POSTING_FLAG, AMOUNT_TYPE, FROM_DATE, TARGET_USER_NAME, TARGET_RESP_NAME, and TARGET_DATABASE_NAME.

Common Use Cases and Queries

The table supports audit reporting, consolidation reconciliation, and troubleshooting of failed or repeated runs. A typical query retrieves the most recent runs for a target period:

• List run history for a period: SELECT consolidation_run_id, consolidation_id, from_period_name, to_period_name, to_currency_code, status FROM gl_consolidation_history WHERE to_period_name = :period ORDER BY creation_date DESC;
• Exclude superseded runs: add AND NVL(obsolete_consolidation_flag,'N') = 'N' to reporting predicates.
• Join to the consolidation definition: SELECT h.*, c.name FROM gl_consolidation_history h, gl_consolidation c WHERE h.consolidation_id = c.consolidation_id;
• Trace the concurrent request: filter on request_id to correlate a run with its concurrent program log.
• Budget-based comparisons: join FROM_BUDGET_VERSION_ID and TO_BUDGET_VERSION_ID to GL_BUDGET_VERSIONS to label source and target budget versions.

Related Objects

The following objects are the most significant relationally or functionally tied to GL_CONSOLIDATION_HISTORY, per the documented foreign keys:

• GL_CONSOLIDATION — joined on CONSOLIDATION_ID; defines the consolidation used for each run.
• GL_CONSOLIDATION_SETS — joined on CONSOLIDATION_SET_ID; supplies the consolidated set definition.
• FND_CURRENCIES — joined on TO_CURRENCY_CODE; resolves the target currency.
• GL_BUDGET_VERSIONS — referenced twice via FROM_BUDGET_VERSION_ID and TO_BUDGET_VERSION_ID; supplies source and target budget versions.
• GL_JE_BATCHES — functionally linked through JE_BATCH_ID for journal batch output of a run.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID for concurrent program status and logs.
• GL_LEDGERS / GL_BALANCES — the balance sources consolidated and reported against the periods recorded here.

Together these relationships position GL_CONSOLIDATION_HISTORY as the central link recording every consolidation event and its supporting reference data.