Search Results gl_je_sources_tl_u3

Overview

GL.GL_JE_SOURCES_TL is the translation (TL) table that stores journal entry source names, user-defined source names, and descriptions for Oracle General Ledger in Oracle E-Business Suite 12.1.1 and 12.2.2. Every journal entry in Oracle GL is stamped with a source name identifying how it was created — for example Manual, Payables, Receivables, or Spreadsheet. GL_JE_SOURCES_TL is the multilingual repository that supplies the displayable text for those sources, and it corresponds directly to the Journal Sources setup form (GLXJESRC). The table resides in the APPS_TS_SEED tablespace, is owned by the GL schema, and is registered in FND Design Data as SQLGL.GL_JE_SOURCES_TL.

The table is classified as standalone under the documented Data Vault heuristic, meaning it carries no foreign keys other than the standard Who audit columns. As a modeling suggestion, this positions GL_JE_SOURCES_TL as a satellite-like descriptive table attached to the base GL_JE_SOURCES entity, holding the language-dependent attributes (names and descriptions) for each source definition. The primary key of the base table is GL_JE_SOURCES_PK (JE_SOURCE_NAME, LANGUAGE); the TL table mirrors that key structure while adding a surrogate JE_SOURCE_KEY column and the ZD_EDITION_NAME discriminator introduced for edition-based redefinition support in 12.2.x.

Key Information Stored

The following columns are the most significant for functional and reporting purposes:

• JE_SOURCE_NAME (VARCHAR2, 25) — The internal journal entry source name. Part of the primary key and of unique index GL_JE_SOURCES_TL_U1.
• LANGUAGE (VARCHAR2) — The language of the translated row. Part of the primary key and of all three unique indexes.
• SOURCE_LANG (VARCHAR2) — The language the text mirrors. If the text has not yet been translated into LANGUAGE, changes made to the source-language row are reflected here as well.
• USER_JE_SOURCE_NAME (VARCHAR2, 25) — The user-defined (display) name shown on the Journal Sources form. Business-key candidate via unique index GL_JE_SOURCES_TL_U2.
• JE_SOURCE_KEY (VARCHAR2) — Surrogate/business key introduced for editioning support. Business-key candidate via unique index GL_JE_SOURCES_TL_U3.
• DESCRIPTION (VARCHAR2, 240) — Free-text description of the journal entry source.
• OVERRIDE_EDITS_FLAG (VARCHAR2) — Indicates whether the source is a frozen source.
• JOURNAL_REFERENCE_FLAG (VARCHAR2) — Controls population of GL_IMPORT_REFERENCES with reference information from the subledger.
• JOURNAL_APPROVAL_FLAG (VARCHAR2) — Determines whether journal approval is required for entries from this source.
• EFFECTIVE_DATE_RULE_CODE (VARCHAR2) — Non-business day rule applied at posting (Roll Date, Leave Alone, or Fail).
• IMPORT_USING_KEY_FLAG (VARCHAR2) — Controls whether subledger imports match on the key rather than the name.
• ZD_EDITION_NAME (VARCHAR2) — Edition discriminator used by Edition-Based Redefinition in 12.2.2. It is a component of all three unique indexes.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — Standard Who audit columns.
• ATTRIBUTE1–ATTRIBUTE5, CONTEXT — Descriptive flexfield segments available for customer extension.

Common Use Cases and Queries

The most frequent requirement is resolving a source name to its user-facing description for reporting. The query below joins the TL row for the current session language:

• SELECT je_source_name, user_je_source_name, description FROM gl_je_sources_tl WHERE language = USERENV('LANG') AND je_source_name = :p_source;

Typical scenarios include:

• Validating that a source is configured with the correct approval flag or effective-date rule before enabling journal approval workflows.
• Auditing which sources populate GL_IMPORT_REFERENCES, useful when tracing subledger journal line references.
• Confirming translation completeness by comparing rows where SOURCE_LANG differs from LANGUAGE.
• Identifying frozen sources (OVERRIDE_EDITS_FLAG) that restrict manual edit overrides during posting.
• Joining to GL_JE_HEADERS.JE_SOURCE to produce source-level journal volume and balance reports, using JE_SOURCE_NAME as the join key.

Because of the ZD_EDITION_NAME column in 12.2.2, ad-hoc queries should filter on the active edition — often via the editioning view — to avoid returning superseded rows.

Related Objects

The following objects are most significant when working with GL_JE_SOURCES_TL:

• GL_JE_SOURCES — The base definition table. Joined on JE_SOURCE_NAME and LANGUAGE; shares primary key GL_JE_SOURCES_PK.
• GL.JE_SOURCES_VL and GL.JE_SOURCES_V — The translation-enabled views normally used by forms and reports in place of the TL table directly.
• GL_JE_HEADERS — References JE_SOURCE_NAME, providing the definitive link between posted journals and their source.
• GL_JE_BATCHES — Also carries JE_SOURCE_NAME, enabling source-level batch reconciliation.
• GL_IMPORT_REFERENCES — Its population behavior is governed by the JOURNAL_REFERENCE_FLAG column in this table.
• GL_JE_SOURCES_TL_U1 / _U2 / _U3 — The three unique indexes supporting lookups by source name, user source name, and source key respectively, each including LANGUAGE and ZD_EDITION_NAME.
• Journal Sources form (GLXJESRC) — The maintenance UI that writes USER_JE_SOURCE_NAME and DESCRIPTION into this table.