Search Results routing_version




Overview
Explore in AI Chat

Overview

The APPS.PMIFV_QC_SPECIFICATIONS_V view is a denormalized, read-only reporting construct belonging to the PMI – Process Manufacturing Intelligence product family. Its stated purpose is to serve as a "QC Specifications Base View," exposing quality control specification records from Process Manufacturing in a form that joins specification attributes to descriptive reference data. Because the underlying PMI module is obsolete in the Oracle EBS 12.1.1 and 12.2.2 application stack, the view is no longer part of an actively enhanced functional area, yet it often remains present and VALID in the APPS schema on legacy installations. It is therefore encountered chiefly by support and migration teams reconciling historical quality data rather than by current implementers.

Architecturally, the view operates as a flattened reporting layer. Rather than requiring report authors to resolve the many foreign keys involved in a quality specification, the view performs the joins on the caller's behalf and substitutes coded lookup values with their translated meanings.

Underlying Base Objects

Per the documented metadata, the view resolves against the following base objects: QC_SPEC_MST (the driving synonym holding the specification master records), IC_ITEM_MST, IC_LOTS_MST, PO_VEND_MST, HZ_CUST_ACCOUNTS_ALL, HZ_PARTIES, and two instances of FND_LOOKUPS. A reference to FND_GLOBAL is also documented, typically used to supply the runtime organization context.

The join topology is predominantly outer-joined. Customer account and party rows are attached via PARTY.PARTY_ID(+) = CUST_ACCT.PARTY_ID and CUST_ACCT.CUST_ACCOUNT_ID(+) = QS.CUST_ID, meaning a specification is never excluded simply because a customer or party is absent. Similarly, lot and item master rows are outer-joined through LO.LOT_ID(+), LO.ITEM_ID(+), and IM.ITEM_ID(+). Vendor and lookup joins complete the picture, so that a specification row always survives regardless of whether descriptive reference data exists.

Key Columns

The view renames most QC_SPEC_MST columns to more explicit labels. QC_SPEC_ID becomes QUALITY_CONTROL_SPEC_ID, and QCASSY_TYP_ID becomes ASSAY_TYPE_ID. Numeric and textual bounds are exposed as MIN_SPEC, MAX_SPEC, TARGET_SPEC, and TEXT_SPEC, with QUALITY_CONTROL_UNIT_CODE carrying the unit of measure.

Of particular interest to the searched term vendor_coa_required, the view exposes COALKUP.MEANING AS VENDOR_COA_REQUIRED. This column is sourced from FND_LOOKUPS and returns the human-readable meaning associated with the stored lookup code that governs whether a Certificate of Analysis is mandatory from the vendor. Related columns VENDOR_SPECIFICATION, VENDOR_CERTIFICATION, CUSTOMER_SPECIFICATION, CUSTOMER_CERTIFICATION, PRINT_COA_SHIPPED, and PRINT_COA_INVOICED describe the certificate and specification obligations attached to the record. ACTIVELKUP.MEANING AS EFFECTIVE provides the active/inactive status, while DELETE_MARK flags logically removed rows. Descriptive attributes include ITEM_NUMBER, ITEM_DESCRIPTION, VENDOR_NUMBER, VENDOR_NAME, CUSTOMER_NUMBER, CUSTOMER_NAME, LOT_NUMBER, and SUB_LOT_NUMBER. Several structural columns, including FORMULA_NUMBER, BATCH_NUMBER, ROUTING_NUMBER, and the various operation and version fields, are hardcoded placeholders.

Common Use Cases and Queries

Typical usage centers on quality reporting and audit extracts, particularly identifying which vendor-linked specifications mandate a Certificate of Analysis.

  • Listing active specifications with vendor COA obligations.
  • Reconciling specification bounds per item, lot, and organization.
  • Producing customer and vendor certificate status extracts.

A representative query follows:

SELECT quality_control_spec_id, item_number, vendor_name,
vendor_coa_required, effective
FROM apps.pmifv_qc_specifications_v
WHERE vendor_coa_required IS NOT NULL
AND NVL(delete_mark, 0) = 0;

Because the view performs numerous outer joins, queries should filter aggressively and avoid selecting unused description columns to limit overhead on legacy data sets.