Search Results vendor_info

Overview

GMI_GMILTGEN_XMLP_PKG is the Oracle Application Object Library package body that backs the Oracle Process Manufacturing (OPM) Lot Genealogy report, a concurrent-program report registered with an XML Publisher (XMLP) template. The package implements the report's PL/SQL trigger logic — the Before Report, After Report, and formula-column functions — that BI Publisher invokes at predefined points during report execution. Its central business purpose is to produce forward and backward lot traceability: given an item number, lot number, and optional sublot number, the package expands the full lot genealogy tree, whether the user requests the "Lot Source" view (ingredients and parent lots) or the "Where Used" view (byproducts and consuming transactions). The report returns lot attributes such as grade, shelf life, inventory class, retest interval, and lot creation type, and generates the concatenated lot-name strings used in the trace output. The code carries the header identifier GMILTGENB.pls, version 120.0, last revised in 2007. Because the package is classified as OTHER rather than as a public API, it is intended for internal use by the Lot Genealogy report only and is not referenced by any other package.

Key Procedures and Functions

The package exposes 48 documented procedures and functions. The two main trigger functions are:

• AFTERPFORM — the Before Report trigger. It captures the concurrent request ID, conditionally applies the GMI FMSEC additional-attribute context, reads the LOT_GEN_DELIMITER profile option (defaulting to "~"), resolves the item and lot identifiers from IC_ITEM_MST and IC_LOTS_MST using the item, lot, and sublot parameters, sets the report and component titles from FND_MESSAGE based on whether the view is "Lot Source" or "Where Used," allocates a trace ID from GMI_LOT_TRACE_ID_S, and calls GMI_LOT_TRACE_PKG.EXP_LOT to explode the genealogy into GMI_LOT_TRACE.
• AFTERREPORT — the After Report trigger. It deletes the working rows created for the current trace ID from GMI_LOT_TRACE and commits, ensuring the temporary genealogy data does not persist.

The remaining entries are formula and helper functions that supply formatted values to the report layout. They include ITEM_NOFORMULA, CF_1FORMULA, I_ITEM_NOFORMULA, DOC_NOFORMULA, QC_SPECFORMULA, UOMFORMULA, and IND_KEY2FORMULA, each deriving a display string for the corresponding report column. The header and attribute functions — HEADER, ITEM_DESC_P, LOT_NO_P, SUBLOT_NO_P, INV_TYPE_P, SHELF_LIFE_P, INV_CLASS_P, GRADE_P, RETEST_INTERVAL_P, LOT_CREATION_TYPE_P, and LOT_CREATION_TYPE_DESC_P — resolve lot and item descriptive attributes for the report output.

Tables Accessed

The package reads Oracle Process Manufacturing inventory and quality tables through APPS synonyms:

• IC_ITEM_MST, IC_LOTS_MST — master item and lot definitions, used to resolve ITEM_ID and LOT_ID and to populate item/lot description attributes.
• GMI_LOT_TRACE, GMI_LOT_TRACE_ID_S — the working table and sequence that hold the exploded genealogy for the run; rows are inserted by the trace package and deleted by AFTERREPORT.
• GMD_SPEC_TESTS_B, GMD_SPEC_RESULTS, GMD_QC_TESTS_B, GMD_SAMPLES, GMD_RESULTS — quality specification and test-result tables supplying QC specification and result values.
• IC_ADJS_JNL, IC_CYCL_HDR, IC_JRNL_MST, OP_BILL_LAD — inventory adjustment, cycle count, journal, and bill-of-material tables contributing to the genealogy and transaction detail.
• OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL — sales order headers and lines, providing where-used demand detail for lots shipped to customers.

Usage Notes

The package is invoked exclusively by the Lot Genealogy concurrent program through its XML Publisher data template; the trigger functions and formula columns are referenced by name in the report definition. Application developers may also call the individual formula functions from custom XMLP templates, but the package is not a supported public API and provides no documented interface for external callers. The user search term "vend_name" does not correspond to any procedure, function, or parameter in this package; vendor name is not part of the lot genealogy output assembled here. Implementation of these triggers depends on the LOT_GEN_DELIMITER profile option and, for sites using GMI FMSEC, the additional attribute context applied in AFTERPFORM.