Search Results routing_version




Overview
Explore in AI Chat

Overview

PMIFV_LOT_LIST_V is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Process Manufacturing (PMI/GME) product family and is registered under the FND Design Data namespace PMI.PMIFV_LOT_LIST_V. The view consolidates lot and batch information together with routing, formula, and procurement context into a single, denormalized projection intended for reporting and integration consumers. Rather than requiring callers to join the discrete Process Manufacturing lot, batch, and receiving tables directly, the view flattens those relationships and surfaces descriptive attributes such as item number, lot number, sublot, vendor name, and—critically for callers searching on routing attributes—ROUTING_NO and ROUTING_VERSION. The view is a BI System view, meaning it is optimized for query access rather than transactional maintenance, and it is not referenced by any other database object, so it serves purely as a read-only presentation layer.

Underlying Base Objects

Per the documented dependency list, PMIFV_LOT_LIST_V resolves over the following objects:

The view therefore joins inventory master data, Process Manufacturing batch execution data, and procurement/receiving data. Its routing columns originate from the batch header's associated routing, which is why a search on "routing_version" surfaces this object.

Key Columns

Common Use Cases and Queries

The view is typically used for lot traceability reporting, where lots must be linked to their batch, formula, routing version, and vendor. A common pattern filters by a specific routing or version:

SELECT LOT_NO, SUBLOT_NO, ITEM_NO, BATCH_NO, ROUTING_NO, ROUTING_VERSION, FORMULA_NO, FORMULA_VERSION
FROM APPS.PMIFV_LOT_LIST_V
WHERE ROUTING_VERSION = :routing_version;

Another frequent scenario is lot genealogy by organization and date range, or tracing lots back to the vendor and receipt number:

SELECT ITEM_NO, LOT_NO, ORGANIZATION_CODE, VENDOR_NAME, RECIEPT_NO, LOT_CREATION_DATE
FROM APPS.PMIFV_LOT_LIST_V
WHERE LOT_CREATION_DATE >= :from_date;

Because the view is populated with descriptive columns only, it should be used for read-only reporting and BI extracts. Queries should always include selective filters on LOT_NO, ITEM_NO, BATCH_NO, or ORGANIZATION_CODE to limit the cost of the underlying multi-table join.