Results for “transaction_quantity_uom2”

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

Overview

PMIBV_LOT_SOURCE_PURCH_V is an APPS-owned database view in Oracle E-Business Suite, delivered as part of the Process Manufacturing Intelligence (PMI) product family. In Oracle EBS 12.1.1 and 12.2.2, PMI is classified as obsolete, meaning the module receives no new functional enhancements, though the underlying database objects frequently remain valid in upgraded environments and are still referenced by legacy reports, custom integrations, and historical genealogy extracts.

The view answers a specific traceability question: for a given finished or intermediate product lot, which purchased raw material lots were consumed in its manufacture, and from which suppliers and receipts did those raw materials originate? It joins the Process Manufacturing lot genealogy (PMI_LOT_GENEALOGY), pending inventory transactions (IC_TRAN_PND), and the purchasing/receiving chain (PO_HEADERS_ALL, RCV_SHIPMENT_HEADERS/LINES, RCV_TRANSACTIONS) to produce a flattened, query-ready result set. Its primary value is regulatory and quality-driven lot traceability, supporting recall investigations, ingredient sourcing analysis, and audit reporting in process industries such as food, beverage, pharmaceutical, and chemicals.

Underlying Base Objects

The view is defined over both inventory and purchasing base objects, joined through shared item, lot, and receipt identifiers. Key documented dependencies include:

• PMI_LOT_GENEALOGY — the core genealogy table linking product item/lot to ingredient item/lot.
• PMI_LOT_SOURCE_LEAF_V — a supporting view in the genealogy hierarchy.
• IC_ITEM_MST, IC_LOTS_MST, IC_WHSE_MST — inventory item, lot, and warehouse master synonyms.
• IC_TRAN_PND / IC_TRAN_CMP — pending and completed inventory transactions that carry the receipt document reference.
• PO_HEADERS_ALL, PO_VENDOR_SITES_ALL, PO_VENDORS_VIEW — purchase order and supplier attributes.
• RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS — receiving receipt, line, and transaction detail.
• FND_GLOBAL — the standard EBS package providing session context (e.g., organization, user).

The view text joins these tables on ITEM_ID, LOT_ID, DOC_ID, and SHIPMENT_HEADER_ID, then aggregates transaction quantities, confirming its role as a consolidated sourcing report rather than a transactional base table.

Key Columns

• PRODUCT_ITEM_ID / PRODUCT_LOT_ID — the manufactured item and lot produced from the ingredients.
• INGRED_ITEM_ID / INGRED_LOT_ID — the raw material item and lot that was consumed.
• WHSE_CODE / ORGN_CODE / LOCATION — warehouse and inventory organization where the transaction occurred.
• TRANS_DATE — the transaction date for the ingredient issue.
• SUM(TRANS_QTY) / SUM(TRANS_QTY2) — aggregated transaction quantities in primary and secondary units of measure.
• RECEIPT_NUM — the receiving receipt number tied to the raw material.
• SEGMENT1 and VENDOR_NUMBER / VENDOR_NAME — purchase order number and supplier identification.
• ITEM_NO, ITEM_DESC1, ITEM_UM, ITEM_UM2, INV_CLASS, PLANNING_CLASS, SALES_CLASS — ingredient item attributes.
• LOT_NO / SUBLOT_NO — lot and sublot numbers for both product and ingredient.

Common Use Cases and Queries

The most frequent scenario is recalling or tracing a finished lot back to its purchased inputs. For example, to identify all supplier lots contributing to a specific product lot:

SELECT product_lot_id, ingred_item_id, ingred_lot_id,
       receipt_num, segment1, vendor_name, trans_date
FROM   apps.pmibv_lot_source_purch_v
WHERE  product_lot_id = :p_lot_id;

Other uses include supplier accountability reporting (aggregating quantities received per vendor), ingredient consumption analysis by warehouse organization, and audit trails linking raw material receipts to production output. Because the view aggregates quantities, results should be interpreted at the lot-sourcing grain. Given the obsolete PMI status, organizations on 12.2.2 are advised to validate output against supported traceability tools or custom extracts before relying on this view for regulated submissions.