Search Results gl_je_headers_s

Overview

GL_JE_SOURCES_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that governs the maintenance of journal entry source definitions used by the General Ledger application. Journal sources classify the origin of journal entries, such as Payables, Receivables, Purchasing, or manual entry, and they drive important processing behavior including the import of subledger data, the journal approval workflow, and the reversal of journals. This package body belongs to the Foundation or "Other" API classification, meaning it supports the internal validation, concurrency control, and multilanguage requirements underlying the GL_JE_SOURCES enterprise entity rather than acting as a formal public business API. In Oracle EBS 12.1.1 and 12.2.2, this package sits alongside the underlying tables GL_JE_SOURCES, GL_JE_SOURCES_S, and GL_JE_SOURCES_TL, ensuring that source definitions remain consistent across all supported languages and that concurrent definition changes are properly serialized. The package is a valid, compiled object in the APPS schema and is referenced by four other database objects.

Key Procedures and Functions

The package exposes thirteen documented procedures and functions, each addressing a specific facet of source definition management:

• SELECT_COLUMNS — constructs or returns the column list used when querying journal source records, providing a consistent projection for callers.
• CHECK_UNIQUE_NAME — validates that a proposed journal source name does not duplicate an existing definition.
• CHECK_UNIQUE_USER_NAME — verifies that the user-facing or alternate name of a journal source is unique.
• CHECK_UNIQUE_KEY — enforces uniqueness of the source key value, which is used as the identifier for journal import and interface processing.
• CHECK_UNIQUE — performs the combined uniqueness validation for a journal source definition.
• GET_UNIQUE_ID — obtains the next unique identifier for a new journal source record, typically drawing from the table's sequence.
• IS_SLA_SOURCE — determines whether a given journal source is associated with Subledger Accounting, which affects how journals originating from that source are created and accounted for.
• INSERT_ROW — inserts a new journal source row.
• UPDATE_ROW — modifies an existing journal source row.
• LOCK_ROW — acquires a row-level lock to serialize concurrent updates to a source definition.
• DELETE_ROW — removes a journal source definition.
• LOAD_ROW — loads or populates a row, supporting programmatic or bulk definition maintenance.
• TRANSLATE_ROW and ADD_LANGUAGE — manage the translatable attributes of journals across installed languages, maintaining rows in the translation table.

Tables Accessed

The package reads and writes the core journal source tables. GL_JE_SOURCES holds the base definition of each source, while GL_JE_SOURCES_S stores the shorter, denormalized representation used by journal entry and import processing. GL_JE_SOURCES_TL contains the language-specific translated names and descriptions, supported by FND_LANGUAGES, which is used to determine the installed and active languages for translation maintenance. GL_JE_HEADERS_S is referenced, reflecting the relationship between journal source definitions and the header staging table used during journal import and validation. XLA_SUBLEDGERS is accessed to support the IS_SLA_SOURCE determination, allowing the package to recognize sources that originate from Subledger Accounting. DUAL is used for simple singular value evaluations. Error handling throughout relies on constructs from APP_EXCEPTION and APP_EXCEPTIONS together with FND_MESSAGE for user-facing messages.

Usage Notes

This package is not referenced by any database object in the dependency metadata, indicating that it is invoked directly by application forms, concurrent programs, and custom extensions rather than being embedded in stored object logic. The GL Journal Sources setup form on the General Ledger setup menu is the primary consumer, calling the insert, update, delete, lock, uniqueness-checking, and translation routines as the user defines and maintains sources. Journal import and subledger accounting processes may consult IS_SLA_SOURCE to determine whether entries arriving from a given source require SLA-generated accounting. Custom code should call the supplied check and lock routines before performing inserts or updates to preserve the integrity of the source-key and naming conventions. Because the package manipulates multilingual data through GL_JE_SOURCES_TL and FND_LANGUAGES, additions of new languages should route through TRANSLATE_ROW and ADD_LANGUAGE rather than direct DML to keep translation rows consistent.