Search Results get_journal_no

Overview

GMI_ERES_UTILS is a utility package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM as an "OTHER" API rather than a formal public interface. It belongs to the Process Manufacturing (OPM/GMI) family of objects, evidenced by its prefix and by the predominance of GME, IC, QC, and SY tables among its dependencies. Its role is to centralize common data-retrieval and formatting logic so that ERES (Electronic Records and Electronic Signatures) functionality and related Process Manufacturing components can resolve descriptive values — item numbers, lot identifiers, unit-of-measure attributes, vendor and warehouse descriptions, reason and grade codes, and journal comments — without embedding duplicate SQL in each calling program.

The package is documented as VALID in both 12.1.1 and 12.2.2, and its metadata lists 24 documented procedures and functions. It references no other APPS packages, depending only on SYS.STANDARD, which keeps it lightweight and free of circular dependencies. ETRM records that it is referenced by zero other packages, indicating it is a leaf utility invoked directly by forms, concurrent programs, or custom extensions rather than being consumed as a shared dependency by other PL/SQL APIs.

Key Procedures and Functions

The documented routines fall into several functional groups:

• Item attribute retrieval: GET_ITEM_NO, GET_ITEM_DESC, and GET_ITEM_UM return the item number, description, and stock unit of measure for a given inventory item.
• Unit-of-measure resolution: GET_UM_TYPE, GET_BASE_UOM, and GET_ITEM_UOM_AND_TYPE resolve the UOM class, the base UOM, and the combined item UOM/type information.
• Lot and sublot handling: GET_LOT_NO, GET_SUBLOT_NO, and GET_LOT_DESC return lot, sublot, and lot description values.
• Descriptive lookups: GET_LOOKUP_VALUE, GET_GRADE_DESC, GET_STATUS_DESC, GET_REASON_DESC, and GET_WHSE_DESC translate stored codes into user-facing descriptions for lookups, grades, statuses, reasons, and warehouses.
• Vendor data: GET_VENDOR_NO and GET_VENDOR_DESC return supplier number and supplier name.
• Journal and miscellany: GET_JOURNAL_NO and GET_JRNL_COMMENT return journal identifiers and comments, PAD_LANGUAGE handles language-code padding, and ACTIVATE_ITEM performs an activation action on an item.

Tables Accessed

The package reads through APPS synonyms across OPM and Oracle Inventory/Procurement:

• Item master: IC_ITEM_MST and IC_ITEM_MST_B supply item number, description, and UOM; MTL_CATEGORIES supports category-related lookups.
• Lots: IC_LOTS_MST, IC_LOTS_CPG, and IC_LOTS_STS provide lot, sublot, and lot status data.
• Batches and journals: GME_BATCH_HEADER supplies batch context, while IC_JRNL_MST provides journal numbers and comments.
• Warehouses: IC_WHSE_MST resolves warehouse codes to descriptions via GET_WHSE_DESC.
• Reference masters: SY_UOMS_MST and SY_UOMS_TYP hold UOM and UOM-type definitions; QC_GRAD_MST holds grade codes; SY_REAS_CDS holds reason codes; PO_VEND_MST holds supplier information.

Usage Notes

GMI_ERES_UTILS is typically invoked from Process Manufacturing forms and concurrent programs, and from custom PL/SQL that needs consistent, pre-validated descriptive text for ERES reports, electronic records, and signature-related output. Because the routines are simple retrieval helpers, they are best called in PL/SQL blocks or form triggers rather than through concurrent managers. The ETRM lists it in the APPS schema with no downstream package references, so customizations may safely call it directly; however, since these are internal ERES utilities rather than a supported public API, custom code should be prepared for signature changes during upgrades and should not rely on undocumented behavior.