Search Results get_new_id

Overview

APPS.GL_ELIMINATION_JOURNALS_PKG is a private PL/SQL package body in the Oracle General Ledger module of Oracle E-Business Suite. Its responsibility is to support the creation, validation, and management of elimination journals—the journals that General Ledger generates to remove intercompany and intra-entity balances during consolidation and financial reporting. Elimination journals are essential to producing accurate consolidated financial statements, and this package encapsulates the lower-level logic used when elimination sets and their associated journal entries are defined and processed.

The package was authored by W. Wong and last revised under header version 120.3 in May 2005, indicating a long-stable code base carried forward into EBS 12.1.1 and 12.2.2. The ETRM classification for this object is OTHER, and the package is referenced by zero other packages, confirming that it is an internal utility package rather than a published integration API.

Key Procedures and Functions

• GET_UNIQUE_ID — Returns the next available primary key value by selecting NEXTVAL from the GL_ELIMINATION_JOURNALS_S sequence. It opens an explicit cursor named get_new_id against DUAL, and if the fetch fails it raises a localized error via FND_MESSAGE (GL_ERROR_GETTING_UNIQUE_ID) before propagating an application exception. This is the routine that matches the user's search term "get_new_id."
• GET_CATEGORY_NAME — Accepts a JE category name and returns the corresponding user-facing journal entry category name by querying GL_JE_CATEGORIES. This allows elimination journal processing to display the descriptive category label rather than the internal code.
• CHECK_UNIQUE_NAME — Performs a uniqueness validation on elimination journal names, using the row identifier and elimination set identifier to scope the check. It ensures that duplicate elimination journal names are not introduced within the same set.

These three documented routines are the only published entry points identified in the ETRM metadata. Additional private routines and the package initialization section (including the balancing-segment position variable, company_seg_num) are used internally to support elimination journal logic.

Tables Accessed

• GL_ELIMINATION_JOURNALS — The primary elimination journal entity table; read and written as elimination journal records are created and validated.
• GL_ELIMINATION_JOURNALS_S — The sequence object supplying surrogate primary keys via NEXTVAL in GET_UNIQUE_ID.
• GL_JE_CATEGORIES — The journal entry category reference table, queried to translate a category code into its user-defined name.
• DUAL — Used solely as the source for the sequence NEXTVAL fetch.

Usage Notes

Because the package is classified as OTHER and is not referenced by any other package, it is intended for internal use within the General Ledger elimination journal feature rather than for direct customer invocation. It is typically exercised by the EBS forms and concurrent programs that maintain elimination sets and their journals, and by server-side GL processing that needs to allocate unique identifiers or validate names. Developers extending elimination journal functionality may call GET_UNIQUE_ID when inserting rows into GL_ELIMINATION_JOURNALS, GET_CATEGORY_NAME to resolve display labels, and CHECK_UNIQUE_NAME to enforce naming rules. Customizations should reference the package through the APPS schema synonym and be aware that its routines are not part of a formally published public API, so they may change between releases.