Results for “gl_translation_tracking_v”

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

Overview

GL_TRANSLATION_TRACKING_V is a General Ledger reporting view exposed in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Per the documented ETRM metadata, the object is restricted to the 10SC configuration and is explicitly described as "10SC ONLY." This indicates that the view is not part of the standard, globally shipped General Ledger schema; rather, it exists to support a specific deployment or localization scenario associated with the 10SC designation. In the documentation sample provided, the view is further qualified with the note "Not implemented in this database," confirming that its presence is conditional and depends on whether the relevant 10SC component has been installed and configured.

Functionally, the view provides a denormalized, filtered presentation of translation-tracking information held in the General Ledger. It surfaces the set of books, target currency, balancing segment value, and the earliest period for which translation has ever been performed. Because translation tracking underpins the periodic conversion of functional-currency balances into a reporting currency, the view serves as a lightweight access point for both reporting and integration routines that need to determine translation history without querying the base table directly.

Underlying Base Objects

The view is defined over a single base object, GL_TRANSLATION_TRACKING, aliased as TT in the view text. The defining query is a straightforward projection with one predicate:

• Base table: GL_TRANSLATION_TRACKING (alias TT).
• Filter condition: TT.ACTUAL_FLAG = 'A', restricting output to actual (as opposed to budget or encumbrance) balances.
• Documented referenced base objects: none separately documented beyond the underlying table, consistent with the select-project-filter nature of the view.

Because no joins, aggregations, or set operations are present, the view adds no data transformation beyond row filtering and column naming. Row cardinality therefore mirrors the qualifying rows in GL_TRANSLATION_TRACKING, and any changes to that table are immediately visible through the view.

Key Columns

The view exposes six columns, each carrying translation-tracking semantics:

• SET_OF_BOOKS_ID — Identifies the set of books (ledger) to which the translation record belongs.
• TARGET_CURRENCY — The currency into which balances were translated.
• BAL_SEG_VALUE — The balancing segment value, allowing tracking at the level of an individual balancing entity.
• EARLIEST_EVER_PERIOD_NAME — The name of the earliest period ever translated for the corresponding set of books, currency, and balancing segment.
• EARLIEST_EVER_PERIOD_YEAR — The fiscal year component associated with that earliest translated period. This is the column most directly relevant to the user search term "earliest_ever_period_year," which appears in reporting predicates that isolate the first year of translation activity.
• EARLIEST_EVER_PERIOD_NUM — The period number within the fiscal year for the earliest translated period.

Together, these columns allow consumers to reconstruct both the identity of a translation scope and the historical starting point of translation activity.

Common Use Cases and Queries

Typical scenarios include identifying when translation was first performed for a ledger/currency/balancing-segment combination, driving reconciliation or audit checks, and feeding downstream reporting or integration processes that must respect translation history. Because the view filters on ACTUAL_FLAG = 'A', queries against it inherently ignore budget-type records.

A representative query returning both the earliest period year and name is shown below:

SELECT set_of_books_id, target_currency, bal_seg_value,
       earliest_ever_period_year, earliest_ever_period_name
  FROM gl_translation_tracking_v
 WHERE earliest_ever_period_year = &year;

An alternative grouping query summarizes translation scopes per ledger and currency:

SELECT set_of_books_id, target_currency,
       MIN(earliest_ever_period_year) first_year
  FROM gl_translation_tracking_v
 GROUP BY set_of_books_id, target_currency;

Because the view is documented as 10SC only, implementations on standard 12.1.1 or 12.2.2 instances should verify object availability before referencing it in code or reports.