Search Results default_lot

Overview

GMI_LOTS_PUB is a public PL/SQL package in the Oracle E-Business Suite Process Manufacturing (OPM) schema, owned by APPS. Its stated purpose, taken directly from the package header comments in GMIPLOTB.pls, is to expose "all APIs related to the Business Object Lot/Sub-Lot." In practice this makes it the supported programmatic entry point for creating and validating inventory lots used throughout OPM inventory, quality, and production transactions. The package was introduced during the R11 upgrade cycle (history entry dated 17-FEB-1999) and has been maintained through several bug fixes, including corrections to date handling in the Create procedure (Bug 2158123) and the addition of NOCOPY hints for large parameter passing (Bug 2643440). It is classified as a PUB interface, meaning it is intended to be called by external consumers such as forms, concurrent programs, and custom extensions rather than being an internal private package.

Key Procedures and Functions

• CREATE_LOT — Creates a new inventory lot record. The procedure encapsulates the full business validation and insert logic required to register a lot against an item and organization, including assignment of the internal lot identifier. Its parameter set includes a standard API version indicator, an initialization message list flag, and a commit indicator, consistent with the EBS PL/SQL API conventions used across the codebase. Based on the documented history, this procedure is the location of the date-assignment corrections applied under Bug 2158123, confirming that lot date attributes are set explicitly inside the routine rather than by the caller.
• VALIDATE_LOT — Performs validation of lot data prior to or independent of creation. It allows a caller to confirm that supplied lot attributes satisfy the package's business rules without committing a row, which is useful for pre-submission checks in forms and for defensive validation in inbound interfaces.

Only these two procedures are documented in the ETRM metadata for version 12.2.2. No additional public entry points should be assumed.

Tables Accessed

The package references the following objects through APPS synonyms:

• IC_LOTS_MST and IC_LOTS_CPG — the master and constraint/grouping tables for lot data; these are the primary targets of Create_Lot and the sources read by Validate_Lot.
• IC_ITEM_MST and IC_ITEM_CPG — item master and item grouping tables, used to confirm that the lot's parent item exists and is valid.
• GEM5_LOT_ID_S — the sequence used to generate surrogate lot identifiers, indicating that lot numbering is sequence-driven.
• PO_VEND_MST — vendor master, consulted when a lot carries supplier or origin information.
• FND_USER — the application user table, used to resolve or record the creating/updating user.
• DUAL — used for single-row computations and default derivations.

Usage Notes

GMI_LOTS_PUB is typically invoked from OPM inventory and lot maintenance forms, from inbound interface concurrent programs that load lot data from external systems, and from custom PL/SQL that needs to create lots through a supported API rather than direct DML. The ETRM metadata records that the package is referenced by three other packages, so callers should treat any signature change as potentially impacting dependent code. Callers should pass p_init_msg_list and p_commit according to their transaction context and should expect validation failures to be returned through the standard message stack.

Note on "default_lot"

The search term default_lot corresponds to the package-level global variable IC$DEFAULT_LOT VARCHAR2(255), declared immediately after G_PKG_NAME in the package body. This is an internal working variable used during lot processing to hold a default lot value; it is not a documented public parameter of either procedure and is not part of the supported API surface.