Search Results generate_lot_number

Overview

GMI_AUTOLOT is a PL/SQL package in the Oracle EBS Process Manufacturing (OPM) suite, owned by the APPS schema and declared with AUTHID CURRENT_USER. Its business purpose is to automate lot number generation for process-manufactured items, removing the need for operators to key lot numbers manually during transactional entry. The package is classified as OTHER in the ETRM documentation, meaning it is not a formally published public API but a supporting internal utility invoked by OPM lot-controlled transaction flows. The package provides a single entry point, GENERATE_LOT_NUMBER, that derives an outbound lot number and sublot number for a given item and document context, and a companion predicate, CHECK_FOR_AUTOLOT, that determines whether an item is configured for automatic lot numbering at all. Together they allow OPM inventory, production, and quality transactions to decide conditionally whether the system or the user supplies the lot identifier. The header comment dates the source to 2003, indicating a long-standing component carried forward through release 12.1.1 and 12.2.2.

Key Procedures and Functions

• GENERATE_LOT_NUMBER — The core generation routine. Given an item, an inbound lot number, an organization code, a document identifier, a line identifier, and a document type, it returns an outbound lot number, a sublot number, and a return status. The inbound lot number parameter allows the caller to pass a seed or pre-existing value, while the document type and document/line identifiers supply the transactional context used to select the appropriate numbering rule and to guard against duplicate generation.
• CHECK_FOR_AUTOLOT — A function returning a numeric indicator that reports whether the specified item is set up for automatic lot numbering. Callers use this as a lightweight test before invoking the generation routine, avoiding unnecessary work and ensuring that user-entered lot numbers are respected for items that are not autolot-enabled.

No other procedures or functions are documented in the package specification. Parameter lists should be taken from the package specification rather than reconstructed, because the documented interface is version-dependent.

Tables Accessed

• IC_ITEM_MST_B — The OPM item master base table. It is read to retrieve the item's lot-control and autolot attributes, which determine whether generation applies and which numbering scheme is used.
• GMI_SUBLOT_GENERATE — The sublot generation table. It supports derivation of the sublot number returned by GENERATE_LOT_NUMBER, allowing a lot to be subdivided into controlled sub-quantities.
• IC_LOTS_MST — The OPM lot master. It is consulted to validate and register lot numbers, and to prevent collisions with lots that already exist for the item and organization.
• FND_USER — The Oracle Applications user table. It is referenced for user context, typically to stamp or sequence generated values by the responsible user or to resolve the calling session's identity.

Usage Notes

GMI_AUTOLOT is normally invoked indirectly. OPM transaction forms and the underlying OPM APIs that create lots — inventory receipts, production batch completion, and quality results entry — call CHECK_FOR_AUTOLOT first and then GENERATE_LOT_NUMBER when the item is autolot-enabled. The package is documented as being referenced by one other package, confirming that it is a dependent utility rather than a top-level entry point, and it is not exposed as a concurrent program. Custom code should treat it as an internal interface: because it is AUTHID CURRENT_USER, all object privileges must be granted to the invoking schema, and the caller must handle the numeric return status from GENERATE_LOT_NUMBER explicitly. The presence of OUT NOCOPY parameters indicates the routine is designed for high-frequency transactional invocation where parameter copy overhead matters. Implementations should verify the exact signature against the installed package specification on 12.1.1 and 12.2.2, since the documented interface reflects the shipped source and is not guaranteed to be backward compatible across patches.