Search Results gl_translation_statuses




Overview
Explore in AI Chat

Overview

GL_TRANSLATION_STATUSES is a General Ledger table owned by the GL schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It records the foreign currency translation status of accounting periods, tracking which ledger, period, and balancing segment have been translated into a given target currency and whether that translation run completed successfully. In an EBS implementation, this table acts as the operational control record that the Translation and Revaluation programs consult and update, preventing duplicate translation runs and providing audit evidence of translation activity across the fiscal calendar.

Under a heuristic Data Vault classification mined from its foreign key structure, the table is best modeled as a link. Its composite identity ties together multiple reference entities — a ledger, a period, a balancing segment value, a target currency, an average-translation indicator, and a budget version — so it functions as an associative record connecting these dimensions rather than as an independent hub or a pure descriptive satellite. No single-column surrogate key is documented; identity is expressed entirely through the composite business key.

Key Information Stored

The table contains 18 documented columns. The most significant include:

The composite primary key GL_TRANSLATION_STATUSES_PK spans LEDGER_ID, PERIOD_NAME, BAL_SEG_VALUE, TARGET_CURRENCY, AVERAGE_TRANSLATION_FLAG, and TARGET_BUDGET_VERSION_ID. The unique index GL_TRANSLATION_STATUSES_U1 carries the identical column list, confirming this set as the business-key candidate. There is no separate single-column surrogate key.

Common Use Cases and Queries

Typical scenarios include confirming whether a period has been translated before closing, auditing translation history for a ledger, and diagnosing concurrent request failures. A representative query retrieves the latest status per ledger and period:

  • SELECT ledger_id, period_name, target_currency, status, last_run_date FROM gl_translation_statuses WHERE ledger_id = :ledger_id AND period_name = :period_name ORDER BY last_run_date DESC;
  • Filtering by actual_flag separates actual from budget translation records, while target_budget_version_id isolates a specific budget version.
  • Joining to FND_CURRENCIES resolves the target currency name; joining to GL_SETS_OF_BOOKS_11I resolves ledger attributes.
  • Reporting by request_id links the status row to the concurrent request log for root-cause analysis of failed runs.

Related Objects

  • GL_SETS_OF_BOOKS_11I — referenced via GL_TRANSLATION_STATUSES.LEDGER_ID, supplying ledger definition and currency context.
  • FND_CURRENCIES — referenced via TARGET_CURRENCY, providing currency names and precision attributes.
  • GL_BUDGET_VERSIONS — referenced via TARGET_BUDGET_VERSION_ID, identifying the budget version translated.
  • GL_BALANCES — holds the translated balances the status rows describe, joined by ledger, period, and currency.
  • GL_PERIOD_STATUSES — controls the open/closed state of the periods against which translation status is evaluated.
  • FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to trace the translation or revaluation program execution.