Results for “max_spec”

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

Overview

PMIFV_QC_MATCH_DTL_V is an APPS-owned database view in Oracle E-Business Suite that presents matched Quality Control (QC) specification and result data. It belongs to the Process Manufacturing Intelligence (PMI) product family, which Oracle classifies as obsolete, meaning the view is retained for backward compatibility but is not part of the strategic EBS data model. The view joins QC specification master records with QC result master records on both the specification identifier and the assay code, producing a flattened, report-friendly result set that pairs each analytical result with the limits it must satisfy.

Its functional role is to expose specification-versus-result matching in a single queryable object. Rather than requiring report or integration code to join QC_SPEC_MST and QC_RSLT_MST directly, consumers can read columns such as SAMPLE_ID, ASSAY_CODE, NUM_RESULT, MIN_SPEC, and MAX_SPEC from one view. This is particularly useful for quality reporting, LIMS-style integrations, certificate-of-analysis extracts, and ad hoc investigations where a user searches by a specific sample identifier. Because the view applies no aggregation, it returns one row per specification/assay combination for each matching result record.

Two characteristics of the view are documented and operationally relevant. First, it enforces a security filter: rows are returned only when the ORGN_CODE on the result is null or when PMI_SECURITY_PKG.SHOW_RECORD returns the string 'TRUE' for that organization. Second, a column is exposed under the alias QUALITY_CONTROL_UNIT_CODE, which maps to the underlying SPEC.QCUNIT_CODE; consumers should not assume the physical column name matches the view alias. The view is defined with status VALID.

Underlying Base Objects

The documented base objects for PMIFV_QC_MATCH_DTL_V are two synonyms within the APPS schema:

• QC_RSLT_MST — the QC result master, aliased RES in the view text. It contributes the analytical result values, the sample reference, and the organization used by the security filter.
• QC_SPEC_MST — the QC specification master, aliased SPEC. It contributes the specification limits and the quality control unit of measure.

The two objects are joined on two predicates that must both match: RES.QC_SPEC_ID = SPEC.QC_SPEC_ID and RES.ASSAY_CODE = SPEC.ASSAY_CODE. This composite join means a result is matched only to the specification defined for the same specification identifier and the same assay. The additional WHERE clause on ORGN_CODE is embedded in the view definition and cannot be bypassed by the calling query; it depends on PMI_SECURITY_PKG, a PL/SQL security package, which introduces a function call into every execution of the view and is a factor in its performance profile.

Key Columns

• SAMPLE_ID — the sample identifier carried from the result record (RES.SAMPLE_ID). This is the column most frequently used as a search or filter key, since it ties results and their matched specifications to a specific physical sample.
• ASSAY_CODE — the assay or test identifier present on both the result and the specification, and the second half of the join condition.
• NUM_RESULT — the numeric result value recorded for the assay.
• TEXT_RESULT — the textual result value, used for qualitative or descriptive outcomes.
• MIN_SPEC, MAX_SPEC, TARGET_SPEC, TEXT_SPEC — the specification limits and target exposed from the specification master. These, combined with NUM_RESULT, drive pass/fail evaluation logic in reports.
• QUALITY_CONTROL_UNIT_CODE — the unit of measure from SPEC.QCUNIT_CODE.
• FINAL_MARK, ACCEPT_ANYWAY — disposition flags from the result record indicating finalization and any acceptance-override decision.

Common Use Cases and Queries

The most common access pattern is a sample-driven lookup, reflecting the frequent user search on "sample_id". A typical query retrieves all matched specification and result rows for a given sample:

• SELECT sample_id, assay_code, num_result, text_result, min_spec, max_spec, target_spec, final_mark FROM pmifv_qc_match_dtl_v WHERE sample_id = :sample_id;
• Out-of-specification reporting: SELECT * FROM pmifv_qc_match_dtl_v WHERE num_result < min_spec OR num_result > max_spec;
• Assay-level trending for a given test code: SELECT sample_id, num_result FROM pmifv_qc_match_dtl_v WHERE assay_code = :assay_code;
• Integration extracts that join the view back to sample or batch headers to enrich certificates of analysis.

Searches against this view are always subject to the embedded organization security predicate, so users restricted by PMI_SECURITY_PKG may see fewer rows than exist in the underlying tables. When the view appears empty for an expected SAMPLE_ID, organization security is the first item to validate before investigating data itself.