Results for “jg_format_curr_amt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JG_INFO is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM metadata as an "OTHER" API. It functions as a general-purpose utility and information-retrieval layer for Oracle General Ledger setup data. Rather than performing transactional posting or journal entry work, JG_INFO centralizes the retrieval of commonly needed reference information — accounting period definitions, set of books attributes, budget and encumbrance identifiers, lookup values, and currency formatting — so that other GL components and custom extensions can obtain consistent results without duplicating query logic against the underlying GL tables.

The package body is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its dependency footprint confirms its supporting role: it references GL_SETS_OF_BOOKS, GL_PERIOD_STATUSES, GL_BUDGET_VERSIONS, GL_CONSOLIDATION, GL_ENCUMBRANCE_TYPES, and GL_LOOKUPS, and it draws on FND_MESSAGE for message handling. Notably, the ETRM record states that APPS.JG_INFO is not referenced by any database object, while separately noting it is referenced by six other packages — the practical implication is that the package is consumed at the application and PL/SQL call level rather than through compiled object dependencies registered against it.

Key Procedures and Functions

Six documented program units are exposed by the package body:

• JG_GET_SET_OF_BOOKS_INFO — Returns descriptive and control attributes for a given set of books, sourced primarily from GL_SETS_OF_BOOKS. It is used wherever GL code needs the chart of accounts, functional currency, or accounting calendar context associated with a ledger.
• JG_GET_BUD_OR_ENC_NAME — Resolves the name of a budget or encumbrance definition. It queries GL_BUDGET_VERSIONS and GL_ENCUMBRANCE_TYPES to translate an internal identifier into a user-recognizable name.
• JG_GET_LOOKUP_VALUE — Retrieves the meaningful value or description associated with a GL lookup code from GL_LOOKUPS, providing consistent decoding of reference values across GL components.
• JG_GET_FIRST_PERIOD — Returns the first (earliest) accounting period for a ledger or calendar, derived from GL_PERIOD_STATUSES. This supports period-range defaults in inquiries and reports.
• JG_GET_FIRST_PERIOD_OF_QUARTER — Returns the first period belonging to a given quarter, enabling quarter-based reporting, budget comparison, and consolidation roll-ups.
• JG_FORMAT_CURR_AMT — Formats a currency amount for display, applying the appropriate numeric and currency conventions. It is a presentation helper rather than a data-retrieval routine.

Tables Accessed

• GL_SETS_OF_BOOKS — Master setup for ledgers/sets of books; supplies currency, chart of accounts, and calendar attributes returned by JG_GET_SET_OF_BOOKS_INFO.
• GL_PERIOD_STATUSES — Holds period definitions and open/closed status; drives JG_GET_FIRST_PERIOD and JG_GET_FIRST_PERIOD_OF_QUARTER.
• GL_BUDGET_VERSIONS — Stores budget version definitions; used by JG_GET_BUD_OR_ENC_NAME to resolve budget names.
• GL_ENCUMBRANCE_TYPES — Defines encumbrance categories; also used by JG_GET_BUD_OR_ENC_NAME for name resolution.

Additional dependencies include GL_CONSOLIDATION, GL_LOOKUPS, and FND_MESSAGE, which support consolidation lookups, lookup decoding, and message text respectively.

Usage Notes

JG_INFO is invoked as a supporting utility rather than through a dedicated concurrent program or form. Typical consumers include General Ledger forms and concurrent programs that need ledger, period, budget, or lookup information, and custom PL/SQL that would otherwise hard-code queries against GL base tables. Because the package centralizes these lookups, callers inherit consistent handling of ledger context and period sequencing. The ETRM record documents no direct database-level referencers, so the six package-level consumers are the primary integration surface. Developers extending GL functionality should call JG_INFO routines rather than re-querying GL_SETS_OF_BOOKS or GL_PERIOD_STATUSES directly, ensuring that formatting and lookup semantics remain uniform across the 12.1.1 and 12.2.2 environments.