Search Results gl_je_sources_tl




Overview
Explore in AI Chat

Overview

The GL_JE_SOURCES_TL table is a core reference table within the Oracle E-Business Suite General Ledger (GL) module. It stores the translated, user-facing names for journal entry sources. A journal entry source defines the origin or subsystem from which a journal entry is generated, such as 'Payables', 'Receivables', 'Spreadsheet', or 'Manual'. This table supports the application's multilingual capabilities, allowing a single source code (e.g., 'PAYABLES') to have a descriptive name (e.g., 'Payables') stored in multiple languages. Its primary role is to provide the translated labels used throughout the GL user interface and reports, ensuring consistency and localization. The table is integral to the setup and validation of journal entries within the financial architecture.

Key Information Stored

The table's structure centers on a unique combination of a source identifier and a language code. The primary key constraint, GL_JE_SOURCES_PK, is defined on the columns JE_SOURCE_NAME and LANGUAGE. Key columns include:

  • JE_SOURCE_NAME: The internal, non-translated code for the journal source (e.g., 'PAYABLES'). This corresponds to the JE_SOURCE_NAME in the base table GL_JE_SOURCES_B.
  • LANGUAGE: The ISO language code (e.g., 'US', 'FR', 'DE') for the translation.
  • USER_JE_SOURCE_NAME: The translated, descriptive name of the source as displayed to users in the specified language.
  • DESCRIPTION: A longer description of the journal source.
  • Standard Oracle Application Object Library columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for auditing.

Common Use Cases and Queries

This table is primarily queried for reporting, data validation, and integration tasks. A common use case is generating a list of all active journal sources with their user-friendly names for a specific language, often joining to the base table GL_JE_SOURCES_B for status information. Developers use it to ensure translated labels are correctly populated in custom reports or interfaces. A typical query pattern is:

SELECT b.je_source_name, tl.user_je_source_name, b.description
FROM gl_je_sources_b b, gl_je_sources_tl tl
WHERE b.je_source_name = tl.je_source_name
AND tl.language = USERENV('LANG')
AND b.status = 'A';

Another critical use is validating the existence of a source during data loads from external systems or when writing custom journal import programs, ensuring that the source code referenced in the data file has a corresponding entry in this translation table.

Related Objects

GL_JE_SOURCES_TL has a direct relationship with several key GL objects. Its primary relationship is with the base table GL_JE_SOURCES_B, which stores the non-translated, seed data for journal sources. The TL table provides the translations for the records in this base table. It is also fundamentally linked to the GL_JE_HEADERS table, where the JE_SOURCE column references a value stored in JE_SOURCE_NAME. For application development, the FND_LANGUAGES table provides the valid language codes referenced in the LANGUAGE column. This table is typically accessed via standard Oracle APIs or through the relevant setup forms in the GL application, which maintain data integrity across these related objects.