Search Results sub_lot_number




Overview
Explore in AI Chat

Overview

APPS.PMIFV_QC_MATCH_HDR_V is a public Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as PMI.PMIFV_QC_MATCH_HDR_V. The object is a reporting and integration view in the Process Manufacturing (PMI) quality module. Its purpose is to associate quality control sampling activity with specific on-hand inventory records, resolving the customer, item, warehouse, locator, lot, and sub-lot context of a quality result or specification. The view is marked VALID in both Oracle EBS 12.1.1 and 12.2.2 and is not referenced by any other database object, confirming its role as a terminal reporting surface rather than a dependency for other code.

The view is especially relevant to users searching on the term "sub_lot_number," because it exposes SUB_LOT_NUMBER together with LOT_NUMBER, LOCATION_ONHAND, LOT_STATUS, and EXPIRE_DATE in a single row. This makes it a convenient join point between quality sampling headers and detailed lot/sub-lot holdings without requiring the caller to reconstruct that linkage manually.

Underlying Base Objects

The documented dependency list defines the following base objects for the view:

  • FND_GLOBAL (package) — supplies runtime environment values such as organization and user identifiers used in the view predicate.
  • FND_LOOKUPS (view) — repository of Oracle Application Object Library lookup codes and meanings, typically used to decode status or type values.
  • HZ_CUST_ACCOUNTS_ALL (synonym) — customer account master, providing CUSTOMER_NUMBER.
  • HZ_PARTIES (synonym) — party master, supplying CUSTOMER_NAME.
  • IC_ITEM_MST (synonym) — item master, supplying ITEM_NUMBER and ITEM_DESCRIPTION.
  • IC_LOCT_INV (synonym) — inventory by locator, supplying WAREHOUSE_CODE, LOCATION, and LOCATION_ONHAND.
  • IC_LOTS_MST (synonym) — lot master, supplying LOT_NUMBER, SUB_LOT_NUMBER, LOT_STATUS, and EXPIRE_DATE.
  • QC_RSLT_MST (synonym) — quality results master, supplying SAMPLE_ID and the result data that drives the match.
  • QC_SPEC_MST (synonym) — quality specification master, supplying the specification context and USE.

Because these objects resolve through APPS synonyms to the PMI and HZ schemas, the view presents a consolidated quality-to-inventory picture without exposing underlying schema details to the report writer.

Key Columns

The view exposes fourteen columns. The most significant for inventory and quality reconciliation are:

  • SUB_LOT_NUMBER (VARCHAR2, 32) — identifies the sub-lot within the parent lot, critical for granular traceability in regulated process industries.
  • LOT_NUMBER (VARCHAR2, 32) — the parent lot identifier.
  • LOCATION_ONHAND (NUMBER) — the on-hand quantity at the specified LOCATION.
  • LOT_STATUS (VARCHAR2) — status of the lot, commonly decoded via FND_LOOKUPS.
  • EXPIRE_DATE (DATE) — lot expiration for shelf-life monitoring.
  • SAMPLE_ID (NUMBER, 10) — link to the quality sample/result record.
  • ITEM_NUMBER, ITEM_DESCRIPTION, ITEM_UOM — item identity and unit of measure.
  • CUSTOMER_NUMBER, CUSTOMER_NAME — customer context where the sampled material is customer-owned or consigned.
  • WAREHOUSE_CODE, LOCATION — physical inventory position.
  • USE (VARCHAR2, 80) — specification usage or disposition text.

Common Use Cases and Queries

Typical scenarios include lot and sub-lot traceability reports, on-hand reconciliation against quality samples, expiration monitoring, and quality disposition dashboards. A simple query by sub-lot is:

SELECT CUSTOMER_NUMBER, ITEM_NUMBER, WAREHOUSE_CODE, LOCATION,
       LOT_NUMBER, SUB_LOT_NUMBER, LOCATION_ONHAND,
       LOT_STATUS, EXPIRE_DATE, SAMPLE_ID
FROM   APPS.PMIFV_QC_MATCH_HDR_V
WHERE  SUB_LOT_NUMBER = :sub_lot_number;

For a broader lot view, replace the predicate with LOT_NUMBER. When reporting on customer consigned stock, filter on CUSTOMER_NUMBER and join to supporting reporting tables as required. Because the view is read-only and not referenced by other database objects, it can be queried safely in custom SQL, BI Publisher data templates, and EBS analytics without affecting transactional integrity.