Search Results gl_fc_xlate_pkg




Overview
Explore in AI Chat

Overview

The APPS.GL_FC_XLATE_PKG package body is a component of the Oracle E-Business Suite General Ledger module, specifically supporting the Financial Consolidation and foreign currency translation (FC/XLATE) functionality. In Oracle EBS 12.1.1 and 12.2.2, this package serves as a backend utility layer that the translation and consolidation engines rely upon to resolve ledger information, verify ledger relationships, and determine whether balances have been translated for a given period. It is classified under the ETRM metadata as an API of type "OTHER," indicating it is a supporting internal package rather than a documented public interface intended for direct customer use.

Its primary business role is to answer the critical questions that the translation process must resolve before converting account balances from a source ledger to a target ledger: which ledgers are involved, whether a valid consolidation relationship exists between them, and whether translation has already occurred for the relevant period. Because translation and consolidation of financial statements must respect hierarchical ledger structures and period statuses, this package acts as a gatekeeper that prevents duplicate, premature, or invalid translation runs.

Key Procedures and Functions

The package exposes seven documented procedures and functions, each addressing a discrete aspect of ledger resolution and translation validation:

  • GET_UNIQUE_NAME — Returns a unique name used to disambiguate ledger or translation context, typically for constructing internal identifiers during translation processing.
  • GET_UNIQUE_SHORT_NAME — Returns a unique short name, complementing the full name for abbreviated internal or display purposes.
  • GET_LEDGER_NAME — Retrieves the descriptive name of a given ledger. This is used to resolve and display the ledger being translated.
  • GET_LEDGER_SHORT_NAME — Retrieves the short name of a ledger, providing a compact reference for reports and lookup logic.
  • RELATION_EXIST — Determines whether a valid consolidation relationship exists between two ledgers. This is a prerequisite check before any translation between source and target ledgers can proceed.
  • XLATED_EVER — Indicates whether balances have ever been translated, used to determine whether translation history exists for a ledger or period.
  • FIRST_EVER_PERIOD_CHECK — Identifies or validates the first period in which translation was or could be performed, supporting correct sequencing of the translation cycle.

Tables Accessed

The package reads from several core General Ledger tables via APPS synonyms:

  • GL_LEDGERS — The base ledger definition table, used to resolve ledger names and short names.
  • GL_LEDGER_RELATIONSHIPS — Stores the relationships between ledgers (such as parent/child or primary/secondary), used by RELATION_EXIST.
  • GL_LEDGER_SET_ASSIGNMENTS — Maps ledgers to ledger sets, supporting resolution across ledger set definitions.
  • GL_PERIODS — Defines period names and dates, used to map period logic during translation checks.
  • GL_PERIOD_STATUSES — Tracks the open, closed, or future-enterable status of periods, essential for validating whether translation is permitted.
  • GL_TRANSLATION_TRACKING — Records which ledgers have been translated and for which periods, underpinning XLATED_EVER and FIRST_EVER_PERIOD_CHECK.
  • DUAL — The standard SYS dummy table, used for scalar evaluations and single-row lookups.

Usage Notes

Because GL_FC_XLATE_PKG is not referenced by any other database object and is classified as "OTHER," it is typically invoked internally rather than through a supported public API. It is most commonly called by the translation and consolidation programs, including the Financial Consolidation concurrent processes and related internal packages (the ETRM metadata notes it is referenced by five other packages). Developers extending or debugging translation behavior may encounter it when tracing how ledger relationships and translation tracking are evaluated. Direct custom invocation is not recommended, as Oracle may modify this package without notice across patch levels of 12.1.1 and 12.2.2.