Search Results vendor_specification




Overview
Explore in AI Chat

Overview

PMIFV_QC_PRODUCTION_SPEC_V is a full view owned by the APPS schema within the PMI (Process Manufacturing Intelligence) product family in Oracle EBS 12.1.1 and 12.2.2. The view is documented as a "QC Production Specification Full View," and its purpose is to present a consolidated, denormalized representation of quality control specifications tied to production entities such as items, formulas, batches, routings, and operations. Rather than forcing report developers and integrators to join the QC specification master table independently against item, formula, lot, batch, routing, and operation master tables, the view performs those joins internally and exposes descriptive attributes alongside the specification values.

The view plays a significant role in Oracle Process Manufacturing Intelligence reporting, where quality specifications must be reconciled against production context. Because it resolves foreign keys into human-readable numbers and descriptions, it is well suited for operational reports, compliance extracts, and integration interfaces that need to communicate which specifications apply to a given manufactured item, batch, or routing step. The user's search term, "print_coa_shipped," maps directly to the PRINT_COA_SHIPPED column exposed by this view, indicating that the view is frequently used to determine whether a Certificate of Analysis should be printed upon shipment. This makes the view directly relevant to shipping, quality, and customer-facing documentation processes.

Underlying Base Objects

The documented view metadata for 12.2.2 lists the following referenced base objects: FM_FORM_MST, FM_OPRN_MST, FM_ROUT_HDR, FND_LOOKUPS, GME_BATCH_HEADER, IC_ITEM_MST, IC_LOTS_MST, and QC_SPEC_MST, each referenced as a synonym except FND_LOOKUPS (view) and the FND_GLOBAL package. The primary driving table is QC_SPEC_MST (aliased QS), which supplies the specification identity and its numeric, textual, and date-range attributes. IC_ITEM_MST (IM) supplies ITEM_NO and ITEM_DESC1, anchoring each specification to a specific item. FM_FORM_MST (FM) contributes the formula identifier, number, and version. IC_LOTS_MST (LO) is joined with an outer join, supplying lot and sublot numbers where a specification is lot-specific. GME_BATCH_HEADER (PM) provides the batch number, linking quality specifications to executed production. FM_ROUT_HDR (RO) and FM_OPRN_MST (OP) contribute routing and operation identifiers and version numbers. FND_LOOKUPS (ACTIVELKUP) is used to resolve the lookup meaning for the effective-from context. FND_GLOBAL is referenced as a package, typically for session context such as organization or user.

Key Columns

The view exposes a broad set of specification attributes and resolved descriptive columns. Notable specification columns include QUALITY_CONTROL_SPEC_ID (renamed from QC_SPEC_ID), ASSAY_TYPE_ID, ASSAY_CODE, TEXT_SPEC, MIN_SPEC, MAX_SPEC, TARGET_SPEC, and QUALITY_CONTROL_UNIT_CODE, which together define the specification range and its assay basis. Documentation and certificate flags include PRINT_COA_SHIPPED, PRINT_COA_INVOICED, VENDOR_SPECIFICATION, VENDOR_CERTIFICATION, CUSTOMER_SPECIFICATION, and CUSTOMER_CERTIFICATION; the "print_coa_shipped" search term corresponds precisely to PRINT_COA_SHIPPED, which controls whether a COA is printed when goods are shipped. Contextual columns such as ORGANIZATION_CODE, WAREHOUSE_CODE, LOCATION, DOCUMENT_TYPE, VENDOR_COA_REQUIRED, OUT_OF_ACTION_CODE, and OUT_OF_ACTION_INTERVAL describe applicability and governance. Date columns FROM_DATE and TO_DATE bound the effective period, while PREFERENCE and ROUTING_STEP_NUMBER indicate priority and process position. Resolved descriptive columns include ITEM_NUMBER, ITEM_DESCRIPTION, FORMULA_ID, FORMULA_NUMBER, FORMULA_VERSION, LOT_NUMBER, SUB_LOT_NUMBER, BATCH_NUMBER, ROUTING_ID, ROUTING_NUMBER, ROUTING_VERSION, OPERATION_ID, OPERATION_NUMBER, and OPERATION_VERSION. Columns such as CUSTOMER_NUMBER, CUSTOMER_NAME, VENDOR_ID, VENDOR_NUMBER, and VENDOR_NAME are exposed as placeholders with blank or zero values in the view definition, and DELETE_MARK indicates logical deletion.

Common Use Cases and Queries

A primary use case is identifying which items or lots require a Certificate of Analysis to be printed at shipment. A representative query filters on the shipped-COA flag and joins item context:

  • SELECT ITEM_NUMBER, ITEM_DESCRIPTION, LOT_NUMBER, BATCH_NUMBER, ASSAY_CODE, MIN_SPEC, MAX_SPEC FROM PMIFV_QC_PRODUCTION_SPEC_V WHERE PRINT_COA_SHIPPED = 1 AND DELETE_MARK = 0;
  • SELECT ORGANIZATION_CODE, ITEM_NUMBER, FORMULA_NUMBER, FORMULA_VERSION, ROUTING_NUMBER, OPERATION_NUMBER, TEXT_SPEC FROM PMIFV_QC_PRODUCTION_SPEC_V WHERE BATCH_NUMBER = :batch AND DELETE_MARK = 0;
  • SELECT ITEM_NUMBER, LOT_NUMBER, FROM_DATE, TO_DATE, PRINT_COA_INVOICED, VENDOR_COA_REQUIRED FROM PMIFV_QC_PRODUCTION_SPEC_V WHERE FROM_DATE <= SYSDATE AND NVL(TO_DATE, SYSDATE) >= SYSDATE AND DELETE_MARK = 0;

These queries support COA generation at shipping and invoicing, batch release and compliance reporting, vendor quality management, and integration extracts feeding external quality or laboratory systems. Because the view already resolves item, formula, lot, batch, routing, and operation descriptions, it reduces the join complexity required in PMI reporting environments.