Search Results get_category_set_id

Overview

APPS.GMIVDBL is the private database-layer package body for the Oracle Process Manufacturing (OPM) Inventory API, internally designated "GMIVDBL Inventory API Database Layer." Its header comment defines its scope precisely: it contains routines accessible only from the Inventory API processing layers, and no other public or private use is supported. Within Oracle EBS 12.1.1 and 12.2.2, OPM inventory objects retain the legacy GMIV naming prefix even though the schema is APPS. The package therefore occupies the lowest tier of a multi-layer API stack — it performs the actual DML and query work against the IC_% and SY_% base tables on behalf of the public OPM Inventory APIs.

A user searching for "get_category_set_id" is likely tracing how a category set identifier is resolved during item, lot, or grade processing. GMIVDBL does not expose a routine by that name. Category set resolution in OPM generally occurs in the public API layer (such as GMIVITMM / GMIVINVM) or in the OPM category validation packages, with GMIVDBL supplying the underlying item, lot, grade, and action master record retrieval that those layers depend on. Applications that must obtain a category set ID should call the public API or query the relevant category tables directly rather than attempting to reach into this private package.

Key Procedures and Functions

Twenty-seven documented procedures and functions are catalogued. They fall into two functional groups.

• Select (query) routines — IC_ITEM_MST_SELECT, IC_LOTS_MST_SELECT, IC_ITEM_CPG_SELECT, IC_LOTS_CPG_SELECT, IC_LOTS_STS_SELECT, IC_JRNL_MST_SELECT, IC_WHSE_MST_SELECT, IC_LOCT_INV_SELECT, SY_REAS_CDS_SELECT, SY_UOMS_MST_SELECT, SY_UOMS_TYP_SELECT, QC_ACTN_MST_SELECT, and QC_GRAD_MST_SELECT. These retrieve master, status, journal, warehouse, reason code, unit-of-measure, and quality (action/grade) records for validation and enrichment by the calling API.
• Insert (DML) routines — IC_ITEM_MST_INSERT, IC_LOTS_MST_INSERT, IC_ITEM_CPG_INSERT, IC_LOTS_CPG_INSERT, IC_JRNL_MST_INSERT, IC_ADJS_JNL_INSERT, and IC_ITEM_CNV_INSERT. These create item, lot, lot-conversion (CPG), journal, adjustment-journal, and item-conversion records.

Parameter lists are not published in the documented metadata and are not reproduced here; each routine implements the database contract expected by its corresponding public API entry point. History entries confirm several housekeeping behaviours: select functions deliberately avoid logging "no data found" (an expected condition), unexpected database errors return SQLERRM, NOCOPY was applied to large record parameters, and IC_ITEM_CNV_INSERT additionally writes an audit row through the GMI_CONV_AUDIT_ID_S sequence.

Tables Accessed

Access is via APPS synonyms, covering inventory master, journal, inventory-on-hand, and reference data.

• Item and conversion — IC_ITEM_MST, IC_ITEM_CPG, IC_ITEM_CNV: item master, item-level CPG (conversion/lot attribute) data, and unit-of-measure conversion factors. The conversion insert also maintains the conversion audit record.
• Lot data — IC_LOTS_MST, IC_LOTS_CPG, IC_LOTS_STS: lot master, lot CPG attributes, and lot status.
• Journal and adjustments — IC_JRNL_MST, IC_ADJS_JNL: inventory journal headers and adjustment journal entries. Journal number insertion is suppressed when a journal number already exists (Bug 2483656).
• Inventory and warehouse — IC_LOCT_INV, IC_WHSE_MST: location-level inventory balances and warehouse master.
• Reference and quality — SY_REAS_CDS, SY_UOMS_MST, SY_UOMS_TYP, QC_ACTN_MST, QC_GRAD_MST, and PO_VEND_MST: reason codes, UOM and UOM types, QC actions, QC grades, and vendor master for validation lookups.

Usage Notes

GMIVDBL is classified as Other and is explicitly private. It is never invoked directly from Oracle Forms or concurrent programs; instead it is reached indirectly through the public OPM Inventory API layer, which in turn is called by OPM forms (item, lot, and inventory transactions), concurrent programs performing inventory and cost processing, and supported custom API integrations. The package is referenced by six other database packages, confirming its role as a shared low-level dependency. Because its signature and behaviour are not part of Oracle's supported interface, custom code should integrate through the public GMIVITMM/GMIVINVM-style APIs. For a requirement such as resolving a category set ID, the supported path is the OPM category API or a direct query against the OPM category tables, never a call into GMIVDBL.