Search Results wf_response

Overview

PMIBV_QCRESULT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined for the Process Manufacturing Intelligence (PMI) product family. The object type is VIEW and its current status in ETRM is VALID, although PMI itself is flagged as obsolete in release 12.1.1 and 12.2.2. Its stated purpose is to expose Quality Control results in a denormalized, query-ready form.

The view joins result-level records from the QC result master to specification, sample, assay type, item, lot, customer, and vendor master data, so that a single row describes a QC outcome together with the specification limits and business context that applied to it. This makes it useful for quality analysts, cost and compliance reporting, and any downstream integration that needs QC result data without reconstructing the underlying joins. A frequent search term associated with this view is outaction_code, which is surfaced from the QC specification master and indicates the out-of-action (out-of-specification response) rule attached to the specification.

Underlying Base Objects

PMIBV_QCRESULT_V is defined over the following documented base objects: QC_RSLT_MST, QC_SPEC_MST, QC_SMPL_MST, QC_ASSY_TYP, IC_ITEM_MST, IC_LOTS_MST, PO_VEND_MST, HZ_CUST_ACCOUNTS_ALL, HZ_PARTIES, SY_ORGN_MST, PMI_COST_ANALZ_PACK (a package), and PMI_SECURITY_PKG (a package), all referenced through APPS synonyms.

The driving table is QC_RSLT_MST, aliased QCRESULT in the view text. QC_SPEC_MST (QCSPEC) supplies specification limits, tolerances, flags, and the OUTACTION_CODE. QC_SMPL_MST (QCSMPLMST) supplies sample number, description, and status. QC_ASSY_TYP (QCASSYTYP) supplies the assay description. IC_ITEM_MST and IC_LOTS_MST provide item and lot identifiers, PO_VEND_MST provides vendor detail, and HZ_CUST_ACCOUNTS_ALL and HZ_PARTIES provide customer and party attributes. PMI_COST_ANALZ_PACK is called through GMCA_GET_MEANING to translate the coded SAMPLE_STATUS into a displayable meaning, truncated to 80 characters. PMI_SECURITY_PKG is referenced for the organization security model that governs which operating units' QC data are visible.

Key Columns

• OUTACTION_CODE and OUTACTION_INTERVAL — the out-of-action rule and interval from QC_SPEC_MST, describing the response required when a result falls outside specification.
• RESULT_DATE, NUM_RESULT, TEXT_RESULT — the result is decoded: numeric results are returned directly, while null numeric results fall back to the text result.
• QCUNIT_CODE, ASSAY_CODE, ASSAY_DESC — unit of measure and the assay/test identity and description.
• ACCEPT_ANYWAY, FINAL_MARK, ASSAY_RETEST, WF_RESPONSE — disposition and workflow flags on the result.
• QC_RESULT_ID, QC_SPEC_ID, SAMPLE_ID, SAMPLE_NO, SAMPLE_STATUS — keys and human-readable sample context.
• ITEM_ID, ITEM_NO, ITEM_DESC1, ITEM_UM, LOT_ID, LOT_NO, SUBLOT_NO, WHSE_CODE, LOCATION — material and inventory context.
• TARGET_SPEC, MIN_SPEC, MAX_SPEC, TEXT_SPEC, FROM_DATE, TO_DATE, PREFERENCE — specification limits and validity.
• CUST_SPECIFICATION, VENDOR_SPECIFICATION, PRINT_COA_SHIPPED, PRINT_COA_INVOICED, VENDOR_COA_REQUIRED — certification and certificate-of-analysis controls.
• PARTY_NUMBER, PARTY_NAME, VENDOR_NO, VENDOR_NAME — customer and supplier identification.

Common Use Cases and Queries

Typical scenarios include listing QC results with their specification limits, identifying results governed by a particular out-action code, tracing results back to a lot or item, and supporting certificate-of-analysis and vendor certification reporting.

Query results governed by a specific out-action code:

SELECT qc_result_id, result_date, sample_no, item_no, assay_desc, num_result, outaction_code, outaction_interval
FROM apps.pmibv_qcresult_v
WHERE outaction_code IS NOT NULL
ORDER BY result_date DESC;

Query results outside specification limits for a given item:

SELECT sample_no, lot_no, assay_code, num_result, min_spec, max_spec, final_mark
FROM apps.pmibv_qcresult_v
WHERE item_no = :item_no
AND (num_result < min_spec OR num_result > max_spec);

Because the view filters on organization through PMI_SECURITY_PKG, queries are subject to the operating-unit security profile of the connected user. On obsolete PMI installations, confirm that the supporting synonyms and package functions remain valid before depending on this view in new integrations.