Results for “sample_status”

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

Overview

PMIFV_BTCH_QCRSLT_V is an APPS-owned database view in Oracle E-Business Suite that exposes batch quality control (QC) results for the Process Manufacturing Intelligence (PMI) product family. In the 12.1.1 and 12.2.2 releases, the underlying PMI module is documented as obsolete, meaning the view is retained primarily for backward compatibility with existing PMI reports, extracts, and integration points rather than for new development. The view is named as the documented source for the search term gmd_spec_results, and it consolidates data from the Process Manufacturing quality schema (GMD tables) with batch execution, item, routing, operation, and calendar data from the GME and FM schemas.

The view presents one row per QC result line, enriched with the sample, test, specification, disposition, batch, and routing context required for analytical reporting on batch quality outcomes. Its role is essentially a denormalized reporting surface: it joins transactional QC results to the specifications that govern them so that target, minimum, and maximum values can be compared alongside actual results without requiring the report author to reconstruct the specification model manually.

Underlying Base Objects

The view text joins the following documented base objects:

• GMD_RESULTS (synonym) — the QC result transactions, aliased QCRESULT.
• GMD_SAMPLES (synonym) — sample headers, aliased QCSMPLMST.
• GMD_SAMPLE_SPEC_DISP (synonym) — sample-level specification disposition.
• GMD_SPEC_RESULTS (synonym) — specification evaluation results, aliased GSRSLT.
• GMD_SPEC_TESTS (synonym) — specification test definitions providing target/min/max values.
• GMD_QC_TESTS_VL (view) — the translated QC test master, supplying test code, type, and unit.
• GMD_EVENT_SPEC_DISP (synonym) — event-level specification disposition.
• GEM_LOOKUPS (view) — lookup meanings, specifically the disposition meaning.
• GME_BATCH_HEADER (synonym) — batch header information.
• IC_ITEM_MST (synonym) — item master for item number and description.
• FM_ROUT_HDR, FM_OPRN_MST, FM_FORM_MST_B (synonyms) — routing header, operation master, and formula master for routing and operation context.
• SY_ORGN_MST (synonym) — organization master for the company code.
• PMI_GL_CALENDAR_V (view) — period year, number, and name.
• PMI_PRODUCTION_SUM (package) — supplies the adjusted count via NO_OF_TIMES_ADJUSTED.
• PMI_SECURITY_PKG (package) — referenced for PMI security filtering.

Key Columns

• CO_CODE, PLANT_CODE, WIP_WHSE_CODE — organization, plant, and warehouse context for the batch.
• SAMPLE_ID, SAMPLE_NO, SAMPLE_DESC — sample identification.
• DISPOSITION, MEANING — disposition code and its lookup meaning.
• TEST_CODE, TEST_UNIT, RESULT_DATE — the test performed and when the result was recorded.
• RESULT — a DECODE over QCTESTS.TEST_TYPE that returns the character value for text tests ('T') and the numeric value for 'E', 'N', and 'L' test types.
• TEXT_VALUE, TARGET_VALUE, MIN_VALUE, MAX_VALUE — specification limits, similarly decoded by test type so numeric and character specifications remain type-consistent.
• ACCEPT_ANYWAY — derived from GSRSLT.EVALUATION_IND ('0A' maps to '1', otherwise '0').
• ITEM_ID, ITEM_NO, ITEM_DESC1, BATCH_ID, BATCH_NO — item and batch identity.
• ROUTING_ID, ROUTING_NO, ROUTING_VERS, STEP_ID, STEP_NO, OPRN_ID, OPRN_NO — routing and operation context.
• PERIOD_YEAR, PERIOD_NUM, PERIOD_NAME — calendar period for time-based analysis.

Common Use Cases and Queries

Typical use cases include batch quality scorecards, out-of-specification (OOS) reporting, and period-based QC trend analysis. A simple query returning results with specification limits would be:

SELECT batch_no, sample_no, test_code, result,
       target_value, min_value, max_value, meaning
FROM   apps.pmifv_btch_qcrslt_v
WHERE  plant_code = :plant
AND    result_date BETWEEN :from_date AND :to_date;

For OOS identification, callers compare RESULT against MIN_VALUE and MAX_VALUE, applying the ACCEPT_ANYWAY flag to distinguish accepted deviations. Because the view is defined over the obsolete PMI product, any new implementation should verify its continued availability in the target instance and consider migrating to supported Process Manufacturing quality reporting alternatives in 12.2.2 and later.