Search Results effective_date_rule_code




Overview
Explore in AI Chat

Overview

APPS.GL_JE_SOURCES_VL is a read-only, language-dependent view over the journal entry sources defined for the General Ledger application in Oracle E-Business Suite. It exposes the translated ("_TL") interface of journal sources, presenting the descriptive name and user-facing fields in the session language while retaining the base source columns needed for validation and processing. In EBS 12.1.1 and 12.2.2, this view is the standard reporting and integration entry point for querying journal sources: it is consumed by concurrent programs, Discoverer reports, Oracle Reports, and external integrations that must resolve a journal source name, key, or its associated control flags.

The search term "effective_date_rule_code" identifies one of the most significant columns exposed here. This column governs how the accounting date (effective date) of a journal entry is defaulted or validated for the source, determining whether the system derives, validates, or allows override of the effective date on journals entered against that source.

Underlying Base Objects

The view is defined exclusively over the base object GL_JE_SOURCES_TL, referenced in ETRM as a SYNONYM. All columns are projected directly from that translated table; there is no join, aggregation, or computed expression. The view text is a direct SELECT from gl_je_sources_tl, filtered by the language predicate LANGUAGE = USERENV('LANG'). The "_VL" suffix signals that this is a language view, meaning the language predicate restricts rows to the caller's session language. Because the base object is the _TL table only, this view does not itself union with the non-translated base table; consumers relying on it operate on the translated attributes. Note that the view uses the ROWID of the underlying _TL row as its ROW_ID pseudo-column.

Key Columns

  • JE_SOURCE_NAME — the internal, language-independent source name.
  • USER_JE_SOURCE_NAME — the descriptive name displayed to users in the session language.
  • JE_SOURCE_KEY — the unique key identifying the journal source; used by import and integration interfaces when key-based import is enabled.
  • EFFECTIVE_DATE_RULE_CODE — controls the effective date (accounting date) rule applied to journals created from this source, governing defaulting and validation of the date.
  • JOURNAL_REFERENCE_FLAG — indicates whether a journal reference is required for the source.
  • JOURNAL_APPROVAL_FLAG — indicates whether journals from the source require approval.
  • IMPORT_ USING_KEY_FLAG — determines whether Journal Import matches on the source key rather than the source name.
  • LANGUAGE, SOURCE_LANG — the language of the translated row and its source language.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
  • ATTRIBUTE1–ATTRIBUTE5, CONTEXT — descriptive flexfield (DFF) context and attribute segments.

Common Use Cases and Queries

Typical uses include validating a journal source prior to import, listing available sources for a data-entry or reconciliation report, and auditing the effective date rule configured against each source. The following query retrieves sources with their effective date rule and import behavior:

SELECT je_source_name,
       user_je_source_name,
       effective_date_rule_code,
       import_using_key_flag,
       journal_approval_flag
FROM   apps.gl_je_sources_vl
ORDER  BY user_je_source_name;

To inspect a single source identified by name or key:

SELECT user_je_source_name,
       effective_date_rule_code,
       journal_reference_flag
FROM   apps.gl_je_sources_vl
WHERE  je_source_name = :p_source;

Because the view filters on USERENV('LANG'), results reflect the caller's language session; integrations requiring the untranslated name should query the corresponding base table. Reading through GL_JE_SOURCES_VL is recommended for reporting in order to honor translation and to remain aligned with documented ETRM metadata.