Results for “shipped_quantity”

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

Overview

The PMIFV_LOT_SHARED_SHIP_V view is an APPS-owned database object within the Oracle E-Business Suite environment, belonging to the PMI (Process Manufacturing Intelligence) product family. Its documented purpose is to provide the relationship between a lot and the shipments that its destination lots have been involved in. In this context, a "Shared Lot" refers to lots that share the same source lots, meaning the view traces forward from a source (start) lot through to destination lots and the outbound shipments those destination lots participated in.

The view is materialized as a VALID object in the APPS schema and derives its core content from PMI_LOT_SHARED_V, enriching that relationship data with item, lot, order, customer, and transaction attributes. It is intended primarily for process manufacturing intelligence reporting where traceability across a shared lot genealogy and downstream shipping activity is required. Because it joins shipment transactions (DOC_TYPE = 'OPSO') to a shared-lot relationship, it supports recall, quality, and genealogy investigations rather than operational transaction entry.

Underlying Base Objects

The view is defined over a combination of synonyms, views, tables, and a package, all resolved in the APPS schema. The documented referenced base objects include:

• PMI_LOT_SHARED_V (VIEW) — supplies the driving shared-lot relationship between START_ITEM_ID/START_LOT_ID and SHARED_ITEM_ID/SHARED_LOT_ID.
• IC_ITEM_MST, IC_LOTS_MST, IC_TRAN_PND (SYNONYMS) — process manufacturing master item, lot, and transaction (pending/transaction) tables providing item, lot, and shipment event details.
• OP_ORDR_HDR, OP_CUST_MST (SYNONYMS) — process order header and customer master providing order number and customer identity.
• OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL (SYNONYMS) — Order Management order header and line tables.
• HR_ALL_ORGANIZATION_UNITS_VL (VIEW) — organization (warehouse/operating unit) lookup.
• PMI_HZ_PARTY_V (VIEW) — party/customer view used for customer resolution.
• FND_PROFILE (PACKAGE) — profile option access used for context-sensitive values.

The view text joins PMI_LOT_SHARED_V to item and lot masters on ITEM_ID and LOT_ID, and to transaction records in IC_TRAN_PND where DOC_TYPE = 'OPSO' (process shipment order), linking the order header through DOC_ID = ORDER_ID and the customer through SHIPCUST_ID = CUST_ID. Results are aggregated with SUM over transaction quantities grouped by item, lot, order, and shipment attributes.

Key Columns

• START_ITEM_ID / START_LOT_ID / START_ITEM.ITEM_NO / START_LOT.LOT_NO / SUBLOT_NO — identify the originating source item and lot in the shared relationship.
• SHARED_ITEM_ID / SHARED_LOT_ID / SHARED_ITEM.ITEM_NO / SHARED_LOT.LOT_NO / SUBLOT_NO — identify the destination (shared) lot that consumed the source lot.
• ITEM_DESC1, ITEM_UM, ITEM_UM2, INV_CLASS, PLANNING_CLASS, SALES_CLASS — descriptive and classification attributes of the shared item.
• SHARED_ORDR.ORGN_CODE — organization code of the shipment.
• SHARED_EVENT.WHSE_CODE / LOCATION — warehouse and location of the shipment event.
• SHARED_ORDR.ORDER_NO — the process order number.
• CUST.CUST_NO / CUST_NAME — customer number and name for the shipment.
• SHARED_EVENT.TRANS_DATE — transaction (shipment) date.
• ABS(SUM(TRANS_QTY)) / ABS(SUM(TRANS_QTY2)) — aggregated absolute shipment quantities in both primary and secondary units.
• SHARED_EVENT.COMPLETED_IND — completion indicator for the transaction.

Common Use Cases and Queries

Typical usage centers on genealogy and traceability reporting, such as identifying every shipment a shared destination lot was involved in, or tracing which customers received product descended from a given source lot for recall and quality investigations.

SELECT start_item_no,
       start_lot_no,
       shared_item_no,
       shared_lot_no,
       order_no,
       cust_name,
       trans_date,
       SUM(trans_qty) ship_qty
  FROM apps.pmifv_lot_shared_ship_v
 WHERE start_lot_no = :p_lot
 GROUP BY ...

Additional scenarios include reconciling downstream shipments against a source lot for yield analysis, and auditing shared-lot propagation across warehouses. Because the view aggregates transaction quantities, queries should apply appropriate GROUP BY or rely on the pre-aggregated grain when reporting. Filters on CUST_NO, ORDER_NO, or TRANS_DATE range are common.