Results for “to_ledger_id”

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

Overview

GL_CONSOLIDATION_HISTORY_V is an APPS-owned database view in the Oracle E-Business Suite General Ledger (GL) module, shipped VALID in both release 12.1.1 and 12.2.2. It presents a denormalized, query-ready representation of consolidation activity by joining consolidation sets, consolidation definitions, chart of accounts mappings, source and target ledgers, consolidation run history, and the resulting journal batches. Consolidation in Oracle GL is the process of combining the balances of one or more subsidiary ledgers into a parent ledger, optionally translating currencies and applying a chart of accounts mapping. The underlying GL_CONSOLIDATION_HISTORY table stores one row per consolidation execution, but it holds only internal identifiers. This view resolves those identifiers into descriptive names, currency codes, ledger names, period ranges, budget context, and journal batch attributes, so that reporting tools, custom concurrent programs, and integration extracts can consume consolidation results without writing the multi-table join logic themselves. Because the view is a read-only projection, it is safe for ad hoc querying and for use as a data source in Oracle Reports, BI Publisher, Oracle Discoverer, or OBIEE extracts. The column MAPPING_NAME, which appears in the view text as M.NAME from GL_COA_MAPPINGS, is the descriptive label of the chart of accounts mapping applied during the consolidation, and is the attribute most commonly searched for by functional users reconciling consolidation output.

Underlying Base Objects

The documented referenced objects are GL_CONSOLIDATION_SETS, GL_CONSOLIDATION, GL_COA_MAPPINGS, GL_CONSOLIDATION_HISTORY, GL_JE_BATCHES, GL_LEDGERS, GL_ACCESS_SET_LEDGERS, and FND_LOOKUP_VALUES, together with the packages GL_FC_XLATE_PKG and GL_CONS_WRK_PKG. The consolidation set, consolidation, and mapping synonyms provide the setup or definition layer. GL_CONSOLIDATION_HISTORY is the transactional core, supplying the run identifier, actual flag, status, period names, budget names and versions, journal batch identifier, and audit columns. GL_JE_BATCHES supplies journal batch detail such as control totals, running debit and credit totals, posting status, approval status, and budgetary control status. GL_LEDGERS is joined twice to resolve the from-ledger and to-ledger, delivering ledger name, currency code, and chart of accounts identifier. GL_ACCESS_SET_LEDGERS participates in the data access enforcement, restricting rows to ledgers the responsibility is permitted to see. FND_LOOKUP_VALUES resolves the obsolete consolidation flag into a user-facing meaning. GL_FC_XLATE_PKG.GET_LEDGER_NAME is invoked inline to derive the translated from-ledger name, while GL_CONS_WRK_PKG is referenced by the consolidation processing logic that populates the underlying history table.

Key Columns

The view exposes identifiers and descriptions in parallel. CONSOLIDATION_SET_ID and CONSOLIDATION_SET_NAME identify the consolidation set, while CONSOLIDATION_ID, CONSOLIDATION_NAME, and CONSOLIDATION_DESCRIPTION identify the specific consolidation definition. MAPPING_ID, MAPPING_NAME, and MAPPING_DESCRIPTION describe the chart of accounts mapping applied. FROM_LEDGER_ID, FROM_LEDGER_NAME, FROM_CURRENCY_CODE, TO_LEDGER_ID, TO_LEDGER_NAME, TO_CURRENCY_CODE, and TO_CHART_OF_ACCOUNTS_ID describe the participating ledgers. FROM_PERIOD_NAME and TO_PERIOD_NAME define the consolidation range. ACTUAL_FLAG distinguishes actual from budget balances, with SOURCE_BUDGET, TARGET_BUDGET, SOURCE_BUDGET_VERSION_ID, and TARGET_BUDGET_VERSION_ID supplying budget context. STATUS_CODE, OBSOLETE_CONSOLIDATION_FLAG, and OBSOLETE_CONSOLIDATION_STATUS convey run state. REQUEST_ID links to the concurrent request. JE_BATCH_ID and the JB_* columns expose journal batch totals, status, approval, and audit attributes. ROW_ID and LAST_UPDATE_DATE support row identification and incremental extraction.

Common Use Cases and Queries

Typical uses include auditing consolidation runs, reconciling mapped balances, verifying journal batch creation, and driving downstream extracts. A query returning mapping and ledger detail for a period might read:

• SELECT consolidation_set_name, consolidation_name, mapping_name, from_ledger_name, to_ledger_name, from_period_name, to_period_name, status_code FROM gl_consolidation_history_v WHERE mapping_name = :p_mapping_name AND from_period_name = :p_period;
• SELECT consolidation_name, je_batch_id, jb_name, jb_control_total, jb_status FROM gl_consolidation_history_v WHERE request_id = :p_request_id;
• SELECT mapping_name, COUNT(*) run_count, MAX(last_update_date) last_run FROM gl_consolidation_history_v WHERE actual_flag = 'A' GROUP BY mapping_name;
• SELECT consolidation_set_name, to_ledger_name, to_period_name, obsolete_consolidation_status FROM gl_consolidation_history_v WHERE obsolete_consolidation_flag = 'Y';

Because the view already resolves identifiers and enforces ledger access, it is the preferred source for consolidation status reports and for troubleshooting why a mapping produced no journal batch.