Search Results target_budget_name

Overview

GL_TRANSLATION_STATUSES_V is a General Ledger (GL) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides a denormalized, read-only presentation of the currency translation status of a ledger for a given accounting period. Currency translation is the process by which account balances maintained in a ledger's functional currency are converted into a target (reporting) currency. The view consolidates the tracking record for each translation run and joins it to period-status and budget-version information, producing a single row per ledger, period, target currency, and translation context.

Because the view abstracts the join logic and exposes meaningful column aliases, it is commonly used for reporting, reconciliation, and integration purposes — for example, in custom concurrent programs, BI Publisher reports, or interfaces that must determine whether a period's balances have been translated before downstream consolidation, elimination, or financial statement generation.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms:

• GL_TRANSLATION_STATUSES — the primary table holding one row per translation run, keyed by ledger, period, target currency, and actual/budget flag. It supplies the balancing segment value, status, last run date, and audit/WHO columns.
• GL_PERIOD_STATUSES — filtered to APPLICATION_ID = 101 (the General Ledger application), supplying PERIOD_NAME, PERIOD_YEAR, and PERIOD_NUM. The join is on LEDGER_ID and PERIOD_NAME.
• GL_BUDGET_VERSIONS — outer-joined on TARGET_BUDGET_VERSION_ID (BV.BUDGET_VERSION_ID(+)) to resolve the target budget name for budget-type translations. Because it is an outer join, actual-balance translation rows without a budget version still appear.

The WHERE clause fixes the GL application context (101) and correlates ledger and period across the status tables, so the view reflects only valid ledger-period combinations.

Key Columns

• PERIOD, PERIOD_YEAR, PERIOD_NUM — the accounting period name, year, and number derived from GL_PERIOD_STATUSES.
• LEDGER_ID — the ledger whose balances were translated.
• CURRENCY_CODE — the target currency (TS.TARGET_CURRENCY) into which balances were translated.
• ACTUAL_FLAG — distinguishes actual (A) from budget (B) translation runs.
• BALANCING_SEGMENT_VALUE — the balancing segment value (TS.BAL_SEG_VALUE), identifying the balancing entity or set of books context for the translation; this is the column most directly associated with the user's search term.
• STATUS — the translation run status (e.g., translated, untranslated, or error).
• DATE_LAST_RUN — the last run timestamp (TS.LAST_RUN_DATE).
• TARGET_BUDGET_NAME / TARGET_BUDGET_VERSION_ID — budget context from GL_BUDGET_VERSIONS for budget translations.
• AVERAGE_TRANSLATION_FLAG — indicates whether average-rate translation was applied.
• ROW_ID and WHO columns — ROWID plus audit fields (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQ_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_ID).

Common Use Cases and Queries

Typical scenarios include verifying translation completeness before close, identifying periods not yet translated, and reviewing translation history by ledger and currency.

• Check translated status for a ledger and period:

SELECT period, currency_code, balancing_segment_value, status, date_last_run
FROM   apps.gl_translation_statuses_v
WHERE  ledger_id = :ledger_id
AND    period    = :period_name
ORDER  BY currency_code;

• Locate untranslated periods or errors:

SELECT period, currency_code, status
FROM   apps.gl_translation_statuses_v
WHERE  status NOT IN ('T')
AND    period_year = :year;

• Filter by balancing segment value, as implied by the search term:

SELECT period, currency_code, status
FROM   apps.gl_translation_statuses_v
WHERE  balancing_segment_value = :bal_seg_value;

Because the view is read-only and based on standard GL tables, it is safe for ad hoc inquiry but should not be used for updates; status changes must be performed through the GL translation concurrent processes that maintain GL_TRANSLATION_STATUSES.