Search Results get_account_number

Overview

JAI_CMN_GL_PKG is a shared ("common") PL/SQL package owned by the APPS schema within the Oracle E-Business Suite, first shipped under version number 120.1 with a header date of 2005. It belongs to the JAI (Oracle Financials for India / localization) family of packages and provides a thin, reusable abstraction layer over General Ledger interface activity. The package serves two distinct business purposes. First, it resolves a code combination identifier (CCID) into a human-readable, concatenated account number string for a given chart of accounts. Second, it constructs and inserts journal entries directly into the GL open interface, allowing localized sub-ledger processes—notably those relating to excise, tax, and manufacturing transactions in the Indian localization—to post accounting entries without invoking the standard sub-ledger accounting engine paths. The package is classified as an OTHER API under ETRM 12.2.2 and is referenced by thirteen other packages, confirming its role as a low-level utility consumed by localization modules rather than an end-user-facing interface.

Key Procedures and Functions

Three procedures comprise the documented interface.

• GET_ACCOUNT_NUMBER — Returns the formatted account number for a supplied chart of accounts identifier and code combination identifier. The account number is delivered through an output parameter, so callers invoke it purely for value resolution. This is the object most likely to be located by a search on "get_account_number," as it is the package's most commonly referenced entry point for converting an internal CCID into the display form used in reports and interfaces.
• CREATE_GL_ENTRY — Creates a single GL interface entry with a rich parameter set covering organization, currency, credit and debit amounts, the code combination, journal source and category, creator identity, accounting and currency conversion attributes, and a set of reference columns (reference_10 and reference_23 through reference_26). The reference parameters were added for Bug 2801751 and are intended to carry transaction type, document number, transaction description, object name, unique key table name, unique key column name, and unique key value, giving downstream reconciliation a traceable link back to the originating transaction.
• CREATE_GL_ENTRY_FOR_OPM — A specialized variant of the create routine adapted for Oracle Process Manufacturing, accepting the organization, currency, credit amount, debit amount, code combination, journal source, journal category, and creator.

Tables Accessed

• FND_CURRENCIES — Consulted to validate currency codes and attributes during entry creation.
• FND_ID_FLEX_SEGMENTS — Used to determine segment structure and ordering when assembling a concatenated account number from a CCID.
• GL_INTERFACE — The primary write target; created journal entries are staged here for later import into the general ledger.
• DUAL — Accessed for scalar evaluations and single-row arithmetic.
• DBMS_SQL — The dynamic SQL facility referenced by the package, indicating that at least one operation constructs and executes SQL at runtime.

Usage Notes

The package is normally invoked from other PL/SQL packages rather than directly from Oracle Forms or concurrent programs. Callers should be aware that entries placed in GL_INTERFACE require a subsequent journal import run to reach the general ledger, and that the reference columns are optional and default to null when not supplied. Because the package writes to an interface table, it should be called within the transaction that owns the originating business event, and any failure should be handled so that partially staged interface rows are cleaned up. GET_ACCOUNT_NUMBER is safe to call for read-only account display purposes and does not modify data. As with all JAI localization objects, customizations should wrap rather than modify the package, since the header indicates controlled versioning by Oracle development.