Search Results location_onhand




Overview
Explore in AI Chat

Overview

APPS.PMIBV_QC_MATCH_HDR_V is a reporting view in the Oracle E-Business Suite Process Manufacturing (OPM) module. It consolidates quality control (QC) match information with inventory, lot, customer, and item attributes, providing a single read-only source for reconciliation and reporting between QC results and specification data. The view is owned by the APPS schema and carries an FND Design Data registration of PMI.PMIBV_QC_MATCH_HDR_V, confirming it as part of the Process Manufacturing design baseline rather than a custom object. Its status is VALID in the documented 12.1.1 and 12.2.2 environments.

The view is intended for query and integration rather than maintenance; it is not referenced by any other database object, meaning no dependent views, packages, or triggers rely on it. This makes it safe to query directly from custom reports, business intelligence extracts, or ad hoc SQL without affecting transactional logic.

Underlying Base Objects

The view is defined over a set of OPM and Oracle applications synonyms. Item and lot information is sourced from IC_ITEM_MST (item master), IC_LOCT_INV (location inventory balances), and IC_LOTS_MST (lot master). Quality data is derived from QC_RSLT_MST (QC results) and QC_SPEC_MST (QC specifications). Customer data is joined from HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES, supporting the customer number and name columns. Utility objects include FND_GLOBAL for session and environment context (for example, organization or user context) and FND_LOOKUPS for decoding lookup values such as lot status and use. The joins collectively produce a denormalized header-level record that pairs QC sample information with the on-hand lot it concerns.

Key Columns

  • CUSTOMER_NUMBER / CUSTOMER_NAME — Customer account number and party name derived from HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES, identifying the customer associated with the QC match.
  • ITEM_NUMBER / ITEM_DESCRIPTION — Item identifier and description from IC_ITEM_MST.
  • WAREHOUSE_CODE / LOCATION — Warehouse and storage location for the inventory record.
  • LOT_NUMBER / SUB_LOT_NUMBER — Lot and sub-lot identifiers from IC_LOTS_MST.
  • LOCATION_ONHAND — The on-hand quantity at the given location, the column typically used when users search for location-on-hand reconciliation. It reflects the inventory balance in IC_LOCT_INV for the lot/location combination.
  • ITEM_UOM — Unit of measure for the item and on-hand quantity.
  • LOT_STATUS — Current lot status, typically decoded from FND_LOOKUPS.
  • EXPIRE_DATE — Lot expiration date.
  • SAMPLE_ID — Identifier linking the record to the QC sample.
  • USE — Usage classification, generally decoded through FND_LOOKUPS.

Common Use Cases and Queries

Typical usage includes reconciling QC sample results against actual on-hand inventory, extracting lot and expiration data for quality audits, and building reports that combine customer, item, and QC specification information. Because the LOCATION_ONHAND column is exposed directly, the view is frequently used where a user needs on-hand quantity alongside QC context without joining IC_LOCT_INV manually.

SELECT ITEM_NUMBER,
       LOT_NUMBER,
       WAREHOUSE_CODE,
       LOCATION,
       LOCATION_ONHAND,
       ITEM_UOM,
       LOT_STATUS,
       EXPIRE_DATE
FROM   APPS.PMIBV_QC_MATCH_HDR_V
WHERE  ITEM_NUMBER = :item
AND    LOCATION_ONHAND > 0
ORDER BY LOT_NUMBER;

A second common pattern filters by customer and sample for QC traceability:

SELECT CUSTOMER_NUMBER,
       CUSTOMER_NAME,
       SAMPLE_ID,
       ITEM_NUMBER,
       LOT_NUMBER,
       EXPIRE_DATE
FROM   APPS.PMIBV_QC_MATCH_HDR_V
WHERE  CUSTOMER_NUMBER = :cust
AND    SAMPLE_ID = :sample_id;

All queries should be executed as the APPS schema or a custom user granted SELECT on the view. Since the object is a view, no DML is supported; data correction must be performed in the underlying base tables through standard OPM and Oracle application forms.