Search Results target_spec




Overview
Explore in AI Chat

Overview

The view PMIBV_QC_MATCH_DTL_V is an Oracle E-Business Suite database object owned by the APPS schema and validated as VALID across release levels 12.1.1 and 12.2.2. It belongs to the Process Manufacturing Intelligence (PMI) product family and is documented as the "QC Specification and results matching Base view." Its purpose is to present quality control specification limits alongside the corresponding quality results recorded against those specifications, joined at the assay level. Rather than requiring report authors, integrators, or analytics developers to construct the join between specification master and result master data manually, the view encapsulates that relationship and exposes a flattened, query-ready result set.

Because the object is a view rather than a table, it stores no data of its own. It functions as a reporting and integration convenience layer, enabling OBIEE dashboards, custom concurrent programs, BI Publisher reports, and inbound/outbound interface logic to compare measured QC outcomes against the tolerances defined in the specification. This makes it central to any workflow that must determine whether a sample passed, failed, or was accepted outside specification limits.

Underlying Base Objects

The view is defined over two documented base objects, both resolved through synonyms in the APPS schema:

  • QC_SPEC_MST — the quality control specification master, supplying the specification limits and target values.
  • QC_RSLT_MST — the quality control result master, supplying the measured or entered assay results.

The join is performed on two conditions joined by AND: RES.QC_SPEC_ID = SPEC.QC_SPEC_ID and RES.ASSAY_CODE = SPEC.ASSAY_CODE. Consequently, a row is returned only where a result exists for the same specification identifier and assay code, ensuring both the specification definition and the observed result are available for comparison.

Key Columns

  • ASSAY_CODE — the assay identifier that links a specification entry to its result; the primary matching key beyond QC_SPEC_ID.
  • NUM_RESULT — the numeric value of the QC result, comparable directly against numeric specification limits.
  • TEXT_RESULT — the textual form of the result, used where the assay is descriptive rather than numeric.
  • FINAL_MARK — indicates whether the result is the final or authoritative reading for the sample.
  • ACCEPT_ANYWAY — flags results accepted despite falling outside specification, supporting disposition and exception reporting.
  • MIN_SPEC / MAX_SPEC — the lower and upper numeric specification limits against which NUM_RESULT is evaluated.
  • TEXT_SPEC — the textual specification value, the counterpart to TEXT_RESULT for descriptive assays.
  • TARGET_SPEC — the nominal or target specification value.
  • QUALITY_CONTROL_UNIT_CODE — the unit of measure associated with the specification (aliased from QCUNIT_CODE).
  • SAMPLE_ID — the identifier of the sample to which the result pertains, enabling traceability back to the originating batch or lot.

The distinction between TEXT_SPEC and numeric specifications is significant: assays that cannot be expressed numerically are validated against the textual specification value, so any out-of-specification analysis must account for both forms.

Common Use Cases and Queries

Typical uses include out-of-specification detection, specification-versus-result exception reporting, and quality dashboards that track acceptance rates by assay or sample.

A straightforward listing of results with their limits:

SELECT ASSAY_CODE, SAMPLE_ID, NUM_RESULT,
       MIN_SPEC, MAX_SPEC, TARGET_SPEC, TEXT_SPEC
FROM   APPS.PMIBV_QC_MATCH_DTL_V;

Identifying numeric results outside specification limits:

SELECT ASSAY_CODE, SAMPLE_ID, NUM_RESULT, MIN_SPEC, MAX_SPEC
FROM   APPS.PMIBV_QC_MATCH_DTL_V
WHERE  NUM_RESULT < MIN_SPEC
OR     NUM_RESULT > MAX_SPEC;

Reporting results accepted outside specification:

SELECT SAMPLE_ID, ASSAY_CODE, NUM_RESULT, ACCEPT_ANYWAY
FROM   APPS.PMIBV_QC_MATCH_DTL_V
WHERE  ACCEPT_ANYWAY = 'Y';

Filtering to final results only ensures that intermediate readings do not distort conformance statistics. All queries should be issued with the APPS schema qualifier or from a session whose naming resolution reaches the APPS synonyms for QC_SPEC_MST and QC_RSLT_MST.