Search Results value_in_report_precision

Overview

PMITS_QC_RESULTS_V is an APPS-owned, VALID database view belonging to the PMI (Process Manufacturing Intelligence) product family — the business intelligence and reporting layer for Oracle Process Manufacturing. It exposes quality control (QC) results alongside the specification and test definitions that govern them, so that a single query can return both a measured value and the minimum, target and maximum limits against which that value should be judged. This pairing is what makes the view suitable for out-of-specification analytics, certificate of analysis (COA) reporting, and laboratory throughput reporting without requiring consumers to join the QC results schema to the specification schema manually.

The view is read-only and intended for reporting and integration rather than transactional maintenance. Because it is owned by APPS, it can be queried by any responsibility holding SELECT privilege on the APPS objects.

Underlying Base Objects

The ETRM metadata lists DUAL (a synonym) as the only referenced base object, which reflects the shell metadata captured for the deployed view rather than its true dependency set. The view text shows that it is defined over the core OPM quality tables, principally:

• GMD_QC_RESULTS (aliased RSLT) — the QC result lines holding sample, test, replicate count, numeric and character values, tester, test kit item/lot/sublot, provider and sequence.
• GMD_SPEC_TESTS (aliased GSTS) — the specification/test definition supplying the spec-level min, target and max values, test method, quantity, UOM, replicate settings, COA printing flag, control-step usage, out-of-spec action, and the below/above min and max action codes.
• GMD_QC_TESTS_B (aliased GQTS) — the test master, used for the TEST_TYPE decode that determines whether the result and limits are treated as character or numeric.
• GSR_RESULTS (aliased GSRSLT) — sample result detail supplying ADDITIONAL_TEST_IND.
• Lookup views FLY/FLN — the standard Yes/No meaning lookups used to translate indicators and delete marks.

Key Columns

• RESULT_ID, SAMPLE_ID, TEST_ID — the primary result identity and the sample and test to which it belongs.
• RESULT_VALUE_NUM / RESULT_VALUE_CHAR — the raw captured value in the appropriate datatype.
• TEST_RESULT — a normalized value driven by GQTS.TEST_TYPE ('T' text, 'E'/'N'/'L' numeric).
• RESULT_MEANING — a descriptive value obtained via GMD_QC_TEST_VALUES_GRP.GET_TEST_VALUE_DESC.
• ASSAY_RETEST — the flag identifying assay retest records, directly relevant to the assay_retest search term.
• SPEC_MIN_VALUE, SPEC_TARGET_VALUE, SPEC_MAX_VALUE — the specification limits, returned as character or numeric depending on test type.
• OUT_OF_SPEC_ACTION, BELOW_MIN_ACTION_CODE, ABOVE_MIN_ACTION_CODE, BELOW_SPEC_MIN, ABOVE_SPEC_MIN, BELOW_SPEC_MAX, ABOVE_SPEC_MAX — specification enforcement attributes.
• TEST_REPLICATE, TEST_REPLICATE_CNT, CHECK_RESULT_INTERVAL — replicate and interval control.
• RSLT_DELETE_MARK — the delete indicator rendered as its lookup meaning.

Common Use Cases and Queries

The most common use is identifying results that fall outside specification limits, or locating assay retests for a batch. For example:

SELECT sample_id, test_id, result_value_num,
       spec_min_value, spec_max_value, assay_retest
FROM   apps.pmits_qc_results_v
WHERE  assay_retest = 'Y';

A second pattern compares numeric results to specification limits:

SELECT sample_id, test_id, result_value_num,
       TO_NUMBER(spec_min_value) min_val, TO_NUMBER(spec_max_value) max_val
FROM   apps.pmits_qc_results_v
WHERE  result_value_num < TO_NUMBER(spec_min_value)
   OR  result_value_num > TO_NUMBER(spec_max_value);

Additional scenarios include generating COA extracts (filtering on the COA print indicators carried through from the specification), laboratory turnaround analysis using RESULT_DATE, and tester productivity reporting using TESTER and TESTER_ID. Always cast specification columns to numeric only for non-text test types, since text tests return character limits.