Results for “pmibv_qc_match_hdr_v”

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

Overview

PMIBV_QC_MATCH_HDR_V is a base reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PMI (Process Manufacturing Intelligence) product family under Oracle Process Manufacturing. The view is documented as a valid object in both EBS 12.1.1 and 12.2.2 and carries the description "QC Customer Specification and results matching Base view." Its purpose is to correlate quality control (QC) customer specifications against actual QC results for inventoried lots, presenting a denormalized, readable row set suitable for quality analysts, customer-facing certificate reporting, and downstream integration.

Rather than exposing the raw QC specification and result tables separately, the view joins them to inventory, lot, item, and customer master data so that a single row answers the question: for this customer, this item, this lot, and this warehouse location, what sample was taken, what was the outcome, and when does the lot expire? As a reporting view it holds no data itself; it is a SQL projection over base tables and is refreshed in real time as the underlying data changes.

Underlying Base Objects

The view is defined over the following documented base objects:

• IC_LOCT_INV — Lot/location inventory balances.
• IC_LOTS_MST — Lot master, including expiry information.
• IC_ITEM_MST — Item master.
• QC_SPEC_MST — QC specifications (customer specifications).
• QC_RSLT_MST — QC results.
• HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES — Customer account and party (TCA) data.
• FND_LOOKUPS — Lookup values, here restricted to the PMI_YES_NO lookup type.

The join path drives from inventory to item and lot, links the specification to the item and matched customer account, and links results to the same item and lot. The predicate RES.CUST_ID IS NULL AND RES.VENDOR_ID IS NULL restricts results to non-customer, non-vendor (internal) results, while SPEC.FROM_DATE <= SYSDATE AND SPEC.TO_DATE >= SYSDATE ensures only currently effective specifications are returned. Rows are limited to positive on-hand (INV.LOCT_ONHAND > 0), and the USE column is populated by the RES.ACCEPT_ANYWAY flag decoded through FND_LOOKUPS. Only one customer-specification relationship is enforced per item and account via the equality of SPEC.ASSAY_CODE and RES.ASSAY_CODE.

Key Columns

• CUSTOMER_NUMBER / CUSTOMER_NAME — Party number and name from HZ_PARTIES.
• ITEM_NUMBER / ITEM_DESCRIPTION / ITEM_UOM — Item identifiers and unit of measure.
• WAREHOUSE_CODE / LOCATION — Inventory organization warehouse and storage location.
• LOT_NUMBER / SUB_LOT_NUMBER — Lot and sublot identifiers.
• LOCATION_ONHAND — Quantity on hand at the location.
• LOT_STATUS — Current lot status code.
• EXPIRE_DATE — Lot expiry date sourced from IC_LOTS_MST; this is the column most frequently searched, used to identify lots nearing or past expiry.
• SAMPLE_ID — The QC sample associated with the result.
• USE — Decoded ACCEPT_ANYWAY meaning from the PMI_YES_NO lookup, indicating whether the result was accepted despite specification variance.

Common Use Cases and Queries

The view is most commonly queried to identify qualifying lots approaching expiry, to prepare customer specification-versus-result comparisons on positive-on-hand stock, and to feed quality dashboards. A representative query filtering on the expiry column is:

SELECT CUSTOMER_NUMBER, CUSTOMER_NAME, ITEM_NUMBER, LOT_NUMBER, SUB_LOT_NUMBER, WAREHOUSE_CODE, LOCATION_ONHAND, LOT_STATUS, EXPIRE_DATE, SAMPLE_ID, USE FROM APPS.PMIBV_QC_MATCH_HDR_V WHERE EXPIRE_DATE BETWEEN SYSDATE AND SYSDATE + 30 ORDER BY EXPIRE_DATE, ITEM_NUMBER;

For a specific customer and item, the view can be constrained on CUSTOMER_NUMBER and ITEM_NUMBER to list currently effective specifications with their associated QC results. Because the view is read-only and defined entirely over base tables, it is safe to embed in custom reports, BI Publisher data models, and OAF/ADF query regions, subject to the standard APPS schema grants required for the calling responsibility.