Results for “expire_date”

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

Overview

The view PMIFV_QC_MATCH_HDR_V is an APPS-owned database view within the Oracle E-Business Suite environment, belonging to the PMI (Process Manufacturing Intelligence) product family. In ETRM 12.1.1 and 12.2.2, PMI is documented as obsolete, meaning the product is no longer actively enhanced or supported for new implementations; nevertheless the view remains valid and may still be referenced by legacy reports, custom concurrent programs, or migration efforts. The description identifies it as the "QC Customer Specification and results matching Full view," indicating that it consolidates quality-control specification data with matching result records at the customer, item, and lot level. Its primary role is to expose a denormalized, read-only result set suitable for reporting and integration, joining inventory lot master data with quality results and customer definitions so that users can compare customer-required specifications against captured sample outcomes.

Underlying Base Objects

The view is defined over a set of synonyms and views resolving to base tables in the Process Manufacturing and Oracle Applications schemas. The documented referenced objects are:

• IC_LOCT_INV — location inventory, supplying warehouse code, location, and on-hand quantity.
• IC_LOTS_MST — lot master, supplying lot number, sublot number, and expiration date.
• IC_ITEM_MST — item master, supplying item number, description, and unit of measure.
• QC_SPEC_MST — QC specification master, filtered to non-deleted specifications active as of SYSDATE.
• QC_RSLT_MST — QC result master, filtered to non-deleted results associated with the item and lot.
• HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES — customer account and party data, providing customer number and name.
• FND_LOOKUPS — lookup values for the PMI_YES_NO lookup type, resolving the acceptance flag into a display meaning.
• FND_GLOBAL — the standard EBS global package, referenced for session context such as SYSDATE/responsibility context.

The joins tie inventory and lot data to items, then to active customer specifications, and finally to result records where ASSAY_CODE matches between the specification and the result, and where customer and vendor identifiers on the result are null.

Key Columns

The view exposes fourteen columns, several of which are directly relevant to sublot-level quality matching:

• CUSTOMER_NUMBER / CUSTOMER_NAME — party number and name of the customer owning the specification.
• ITEM_NUMBER, ITEM_DESCRIPTION, ITEM_UOM — item identification and stocking unit.
• WAREHOUSE_CODE, LOCATION, LOCATION_ONHAND, LOT_STATUS — inventory placement and quantity on hand at the location.
• LOT_NUMBER — the lot identifier from IC_LOTS_MST.
• SUB_LOT_NUMBER — mapped from LOT.SUBLOT_NO, representing the sublot subdivision of a lot. This is the column of interest for the search term "sub_lot_number."
• EXPIRE_DATE — the lot expiration date.
• SAMPLE_ID — the QC sample identifier from the result master.
• USE — the decoded PMI_YES_NO lookup meaning for the ACCEPT_ANYWAY flag, indicating disposition.

Common Use Cases and Queries

Typical usage includes quality reporting, customer specification compliance checks, and inventory-to-sample traceability. Because the view already restricts to on-hand quantities greater than zero, it is well suited to current stock reporting. A representative query filtering on sublot is:

• SELECT customer_number, item_number, lot_number, sub_lot_number, location_onhand, sample_id, use FROM apps.pmifv_qc_match_hdr_v WHERE sub_lot_number = :p_sublot;
• Aggregating on-hand by item and sublot for warehouse review.
• Joining the view back to QC result detail tables using SAMPLE_ID for drill-down reporting.

Because the object is obsolete and read-only, it should be used for query and integration purposes only, and any replacement should be evaluated against current QC and inventory reporting objects.