Results for “gl_translation_interim”

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

Overview

GL_TRANSLATION_INTERIM is a General Ledger (GL) staging table that stores foreign currency translated interim balances during the period-end translation process in Oracle E-Business Suite 12.1.1 and 12.2.2. Translation is a required step in the financial close cycle: it converts functional-currency balances of a ledger into a reporting currency using the appropriate period-average and period-end rates defined in GL_DAILY_RATES. Before translated results are posted into GL_BALANCES and later into reporting-currency balance tables, the translation engine writes its working results into this interim table, where they remain available for review, re-derivation, and audit before the final posting step.

The object resides in the GL schema, is owned by General Ledger, and carries a status of VALID. Its described purpose is the storage of foreign currency translated interim balances. Because the table accumulates balances across periods, currencies, accounts, and ledgers, its column set is wide (55 documented columns in ETRM 12.2.2), reflecting the flattened, denormalized shape typical of GL balance and interim tables. Under a heuristic Data Vault classification derived from the foreign-key structure, this object is best modeled as a link, sitting between the account-combination, ledger, period-type, currency, and summary-template dimensions that jointly qualify each interim balance row.

Key Information Stored

The most significant columns fall into keys, period attributes, and monetary measures.

• CODE_COMBINATION_ID — foreign key to GL_CODE_COMBINATIONS, identifying the account combination whose balance is being translated.
• SET_OF_BOOKS_ID / LEDGER_ID — the ledger or set of books context for the translation; SET_OF_BOOKS_ID is documented as an FK to GL_SETS_OF_BOOKS.
• TEMPLATE_ID — FK to GL_SUMMARY_TEMPLATES, indicating the summary account template applied to the interim balance.
• CURRENCY_CODE — FK to FND_CURRENCIES, the reporting (translated-to) currency.
• PERIOD_TYPE — FK to GL_PERIOD_TYPES, qualifying the period type for which the interim balance is held.
• PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM — the accounting period identification.
• ACCOUNT_TYPE — the natural account classification (asset, liability, revenue, expense, owner's equity) that governs the rate convention applied.
• BAL_SEG_VALUE / SEC_BAL_SEG_VALUE — balancing segment (and secondary balancing segment) values used to enforce balance rules.
• ACTUAL_FLAG and INCREMENTAL_FLAG — indicate whether the amounts are actual versus budget/encumbrance, and whether the row represents an incremental translation run.
• PERIOD_NET_DR / PERIOD_NET_CR — translated net activity debits and credits for the period.
• QUARTER_TO_DATE_DR / QUARTER_TO_DATE_CR and PROJECT_TO_DATE_DR / PROJECT_TO_DATE_CR — translated quarter-to-date and project/period-to-date activity.
• BEGIN_BALANCE_DR / BEGIN_BALANCE_CR — translated opening balances.
• PERIOD_NET_DR_BEQ / PERIOD_NET_CR_BEQ, BEGIN_BALANCE_DR_BEQ / BEGIN_BALANCE_CR_BEQ — the same measures expressed in the entered (BEQ, balanced-equivalent) currency, retained for reconciliation between the source and translated amounts.
• SEGMENT1 through SEGMENT30 — the individual key flexfield segment values that make up the account combination, denormalized to support reporting without joining GL_CODE_COMBINATIONS.

The physical table does not expose a single-column surrogate primary key in the documented metadata; the effective uniqueness of a row is the composite of ledger, period, code combination, currency, period type, template, and actual/incremental flags. The ETRM metadata documents the 55 columns and the five inbound foreign keys but does not enumerate a unique index, so the business key must be inferred from these qualifying columns.

Common Use Cases and Queries

Typical usage centers on validating translation results before posting, reconciling translated versus entered amounts, and reporting translated activity by account and currency.

• Reviewing interim translated balances for a given ledger and period before the translation run is finalized: select code_combination_id, currency_code, period_net_dr, period_net_cr from gl_translation_interim where ledger_id = :p_ledger and period_name = :p_period.
• Reconciling the translated amount against the entered amount by comparing the DR/CR columns with their _BEQ counterparts to identify translation gain/loss or rate anomalies.
• Reporting translated periodic activity by naturally derived segments using the denormalized SEGMENT1–SEGMENT30 columns, avoiding a join to GL_CODE_COMBINATIONS.
• Confirming which currencies and period types were processed for a ledger, and whether an incremental or full translation applies, via CURRENCY_CODE, PERIOD_TYPE, and INCREMENTAL_FLAG.
• Auditing the summary template mapping applied to each interim account balance through TEMPLATE_ID.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign-key relationships.

• GL_CODE_COMBINATIONS — joined on GL_TRANSLATION_INTERIM.CODE_COMBINATION_ID; supplies account combination detail and validation.
• GL_SETS_OF_BOOKS — joined on GL_TRANSLATION_INTERIM.SET_OF_BOOKS_ID; defines the ledger, chart of accounts, and functional currency.
• GL_SUMMARY_TEMPLATES — joined on GL_TRANSLATION_INTERIM.TEMPLATE_ID; identifies the summary account template used for interim aggregation.
• GL_PERIOD_TYPES — joined on GL_TRANSLATION_INTERIM.PERIOD_TYPE; qualifies the accounting period type.
• FND_CURRENCIES — joined on GL_TRANSLATION_INTERIM.CURRENCY_CODE; provides the translated reporting currency definition.
• GL_DAILY_RATES and GL_BALANCES — although not documented as FKs, these are the rate source and the downstream target of the translation process, making them operationally related to this interim table.