Search Results inventory_class

Overview

PMIFV_LOT_RESOURCE_LIST_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PMI (Process Manufacturing Intelligence) product family. It is a reporting and integration object rather than a transactional entity, and it is exposed only through the APPS synonym so that it can be referenced uniformly by custom reports, concurrent programs, and analytic extracts. The view presents a denormalized inventory of lots that shared a particular combination of production parameters, drawing together item master attributes, lot master attributes, organization detail, supplier detail, and the batch step resources consumed during production.

Because the view is strictly read-only (it is defined WITH READ ONLY), no DML is permitted against it. All access is query-only, consistent with its purpose as a process manufacturing intelligence reporting construct. In ETRM metadata for 12.1.1 and 12.2.2, the object is documented as VALID with the description "This view lists lots that shared a particular set of parameters," which summarizes its role: enabling users to associate lots with the resources that produced them, then compare and group lots by those shared attributes.

Underlying Base Objects

The view is defined over six underlying objects, each referenced through an APPS synonym in the documented 12.2.2 metadata:

• IC_TRAN_PND — the pending inventory transaction table, aliased T, which supplies the production transactions and links to items, lots, organizations, and batch documents.
• IC_ITEM_MST — the item master, aliased I, providing item number, description, item id, inventory class, and inventory type.
• IC_LOTS_MST — the lot master, aliased L, providing lot number, sublot number, creation date, QC grade, and the ship-from vendor reference.
• PO_VEND_MST — the vendor master, aliased V, supplying vendor number, name, and id; it is outer-joined to the lot via SHIPVEND_ID.
• SY_ORGN_MST — the organization master, aliased S, providing the organization name for the transaction organization code.
• GME_BATCH_STEP_RESOURCES — the batch step resources table, aliased O, providing the concatenated RESOURCES value and joined to the transaction via BATCH_ID = DOC_ID.

The joins are inner joins throughout except for the vendor lookup, which uses the Oracle outer-join operator (+). The view text further restricts results with T.LOT_ID <> 0, T.LINE_TYPE IN (1, 2), and T.DOC_TYPE = 'PROD', and applies SELECT DISTINCT to eliminate duplicate combinations.

Key Columns

• ITEM_NO, ITEM_DESCRIPTION, ITEM_ID — item identification and description from the item master.
• INVENTORY_CLASS, INVENTORY_TYPE — the item's inventory class and type, exposed from IC_ITEM_MST's INV_CLASS and INV_TYPE columns. These are frequently used to classify and filter lots.
• LOT_ID, LOT_NO, SUBLOT_NO — lot identity and sublot reference from the lot master.
• LOT_CREATION_DATE, QC_GRADE — the lot creation date and quality grade, useful for age analysis and quality reporting.
• ORGANIZATION_CODE, ORGANIZATION_NAME — the transaction organization and its descriptive name.
• VENDOR_NO, VENDOR_NAME, VENDOR_ID — supplier detail from the outer-joined vendor master; these are null when no ship-from vendor is recorded on the lot.
• RESOURCES — the batch step resource string associated with the production transaction, which is the central "parameter set" referenced by the view description.

Common Use Cases and Queries

Typical uses include lot traceability reports, resource-to-lot association analysis, inventory class and type breakdowns, and supplier-to-lot linkage. A basic query to list lots by item and inventory class is:

SELECT item_no, inventory_class, lot_no, sublot_no, qc_grade, resources FROM apps.pmifv_lot_resource_list_v WHERE inventory_class = 'FG' ORDER BY item_no, lot_creation_date;

To enumerate lots sharing a given resource, filter on the RESOURCES column:

SELECT lot_no, item_no, organization_code, resources FROM apps.pmifv_lot_resource_list_v WHERE resources LIKE '%REACTOR%' ORDER BY organization_code, lot_no;

Supplier-oriented analysis uses the vendor columns:

SELECT vendor_name, item_no, lot_no, qc_grade FROM apps.pmifv_lot_resource_list_v WHERE vendor_id IS NOT NULL;

Because the view applies SELECT DISTINCT and inner joins across production transactions and batch step resources, results reflect only lots with qualifying PROD transactions that have associated batch resources; queries should account for this scope when reconciling against the underlying transactional tables.