Results for “pmibv_lot_list_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PMIBV_LOT_LIST_V is an APPS-owned database view in Oracle E-Business Suite, defined in the Process Manufacturing Intelligence (PMI) product family. In ETRM 12.2.2 the object carries a VALID status; the PMI module itself is flagged as obsolete, which means the view is retained for backward compatibility with existing customizations, workbook definitions, and historical reporting rather than for active product development. Its documented purpose is to serve as a "Lot List View used by the Lot Genealogy workbook," a BI Publisher / Oracle Discoverer-style workbook that traces lot lineage through receiving, inspection, and inventory transactions in process manufacturing environments.

Functionally, the view consolidates lot-level inventory data with item, organization, and vendor attributes. It presents one row per lot per source document (receiving transaction or receipt), enriched with item description, inventory class and type, QC grade, warehouse code and name, lot creation date, and the originating vendor or supplier information. The view is defined as a UNION ALL of two queries, one handling process inventory transactions (DOC_TYPE = 'PORC') and one handling receiving transactions (DOC_TYPE = 'RECV'), which allows the Lot Genealogy workbook to present a unified supplier-to-lot picture regardless of how the lot was introduced into inventory.

Underlying Base Objects

The documented referenced base objects for PMIBV_LOT_LIST_V in 12.2.2 include FND_GLOBAL (package) and the following synonyms and views in the APPS schema: GME_BATCH_HEADER, IC_ITEM_MST, IC_LOTS_MST, IC_TRAN_PND, PO_RECV_DTL, PO_RECV_HDR, PO_VEND_MST, PO_VENDORS_VIEW (view), PO_VENDOR_SITES_ALL (view), RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS, and SY_ORGN_MST.

The primary driving table in both UNION ALL branches is IC_TRAN_PND, joined to IC_ITEM_MST on ITEM_ID and IC_LOTS_MST on LOT_ID. The first branch links purchase receipts through RCV_SHIPMENT_LINES, RCV_SHIPMENT_HEADERS, and RCV_TRANSACTIONS, resolving the supplier via PO_VENDOR_SITES_ALL and PO_VENDORS_VIEW. The second branch uses the legacy procurement tables PO_RECV_DTL and PO_RECV_HDR, joined to PO_VEND_MST for vendor identification. SY_ORGN_MST supplies the organization name for the warehouse code. The referenced use of PO_VENDORS_VIEW is significant given the user's search term: the view does not query PO_VENDORS directly but instead resolves vendor attributes through the PO_VENDORS_VIEW view, which encapsulates the effective-dated vendor master and applies the standard Oracle date-range filter for current vendor records.

Key Columns

• ITEM_NO, ITEM_DESC1, ITEM_ID, INV_CLASS, INV_TYPE — item identifier, description, and inventory classification attributes sourced from IC_ITEM_MST.
• LOT_ID, LOT_NO, SUBLOT_NO, LOT_CREATED, QC_GRADE — lot identity and quality attributes from IC_LOTS_MST; LOT_CREATED is truncated to date precision.
• ORGN_CODE, ORGN_NAME — warehouse/organization code from IC_TRAN_PND and its descriptive name from SY_ORGN_MST.
• VENDOR_NUMBER, VENDOR_NAME, VENDOR_ID — supplier identifier and name, resolved through PO_VENDORS_VIEW (branch one) or PO_VEND_MST (branch two).
• RECEIPT_NUM — receipt number from RCV_SHIPMENT_HEADERS, giving traceability back to the originating receipt transaction.
• Literal placeholder columns — the view emits three constants (' ', ' ', 0) followed by another (' ', 0), used for column alignment and compatibility with the workbook's expected output layout.

Common Use Cases and Queries

The principal use case is lot genealogy and supplier traceability reporting: identifying which supplier provided a given lot, when the lot was created, and in which warehouse it resides. A typical query filters by lot or item:

• SELECT LOT_NO, ITEM_NO, VENDOR_NAME, ORGN_CODE, LOT_CREATED, QC_GRADE FROM APPS.PMIBV_LOT_LIST_V WHERE LOT_NO = :lot_no;
• SELECT ITEM_NO, LOT_NO, VENDOR_NUMBER, VENDOR_NAME, RECEIPT_NUM FROM APPS.PMIBV_LOT_LIST_V WHERE VENDOR_ID = :vendor_id ORDER BY LOT_CREATED DESC;
• SELECT ORGN_CODE, COUNT(DISTINCT LOT_NO) FROM APPS.PMIBV_LOT_LIST_V GROUP BY ORGN_CODE;

Because the view is a UNION ALL over inventory and receiving transaction data with a HAVING SUM(TRANS_QTY) > 0 predicate on the first branch, queries should be constrained on item, lot, vendor, or organization where possible to control the scan cost against IC_TRAN_PND and the receiving tables. Given the obsolete status of the PMI module, new development should treat this view as a read-only compatibility object and prefer current OPM or receiving data models for net-new reporting.