Results for “gmd_results”

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

Overview

GMD_RESULTS is the Oracle Process Manufacturing (OPM) Quality Results table residing in the GMD schema, delivered as part of the Process Manufacturing Product Development module. It stores the analytical outcomes produced when a quality specification test is executed against a sample. Where GMD_SAMPLES identifies the physical material drawn for inspection and GMD_TESTS defines the individual test lines to be performed, GMD_RESULTS captures the measured value, the method employed, the analyst, the instrument or resource used, and the disposition-oriented dates that drive Quality Management and Certificate of Analysis (COA) processing.

The table occupies a central position in the OPM quality lifecycle: a laboratory record cannot be released, a lot cannot be dispositioned as accepted, and a COA cannot be published without a corresponding result row. It is equally important to Production, since results are consumed by manufacturing execution to confirm that in-process and finished material meets specification.

Mined foreign-key metadata classifies GMD_RESULTS as standalone under the heuristic Data Vault model; it references GMD_TEST_METHODS_B but is not itself a dependent of a parent hub through enforced FKs. The most accurate modeling suggestion is therefore a satellite hanging off the sample-and-test business key (SAMPLE_ID plus TEST_ID), with RESULT_ID acting as the surrogate sequence key rather than a true integration hub key.

Key Information Stored

The primary key is GMD_RESULTS_PK, defined on the surrogate column RESULT_ID. The documented unique index is limited to this same key, meaning the table has no separate enforced business-key constraint; SAMPLE_ID combined with TEST_ID and TEST_REPLICATE_CNT functions as the practical natural key.

• RESULT_ID — surrogate primary key populated from a sequence.
• SAMPLE_ID — foreign reference to the sample being tested; the principal business linkage.
• TEST_ID — the specification test line satisfied by this result.
• TEST_METHOD_ID — the analytical method used; the only enforced FK, pointing to GMD_TEST_METHODS_B.
• RESULT_VALUE_NUM and RESULT_VALUE_CHAR — numeric and alphanumeric outcome, one selected by the test's data type.
• TEST_UOM, TEST_QTY, TEST_QTY_UOM — unit of measure and quantity consumed or assayed.
• RESULT_DATE, PLANNED_RESULT_DATE, TEST_BY_DATE — completion, expected, and expiry-driven due dates.
• TESTER / TESTER_ID, TEST_PROVIDER_CODE, TEST_PROVIDER_ID, QC_LAB_ORGN_CODE, LAB_ORGANIZATION_ID — analyst and laboratory attribution.
• ORGANIZATION_ID — the inventory organization in which the result applies.
• PARENT_RESULT_ID, RESERVE_SAMPLE_ID, TEST_REPLICATE_CNT, ASSAY_RETEST — replicate, retest, and parent/child result lineage.
• CONSUMED_QTY, ACTUAL_RESOURCE, PLANNED_RESOURCE and their instance columns — resource consumption for cost and scheduling.
• DELETE_MARK — logical deletion flag used throughout GMD.
• ATTRIBUTE1–30 and the standard CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE who-columns provide extensibility and audit.

Common Use Cases and Queries

Typical reporting retrieves all results for a sample, computes pass/fail against specification limits, or lists outstanding tests past their due date.

• Sample result detail: SELECT r.result_id, r.test_id, r.result_value_num, r.result_value_char, r.test_uom, r.result_date, r.tester FROM gmd_results r WHERE r.sample_id = :sample_id AND NVL(r.delete_mark,0) = 0 ORDER BY r.seq;
• Overdue testing: SELECT r.sample_id, r.test_id, r.test_by_date FROM gmd_results r WHERE r.test_by_date < SYSDATE AND r.result_value_num IS NULL AND NVL(r.delete_mark,0) = 0;
• Method usage analysis: join GMD_TEST_METHODS_B on TEST_METHOD_ID to count results per analytical method by organization.
• Retest and replicate auditing: filter on ASSAY_RETEST or non-null PARENT_RESULT_ID to trace result lineage.
• COA generation support: select results where AD_HOC_PRINT_ON_COA_IND is set, joined to sample and lot data.

Related Objects

• GMD_TEST_METHODS_B — referenced through TEST_METHOD_ID; supplies method name and version.
• GMD_SAMPLES — parent of a result, joined on SAMPLE_ID.
• GMD_TESTS — defines the test specification satisfied by each result, joined on TEST_ID.
• GMD_SPECIFICATIONS — target limits against which RESULT_VALUE_NUM is evaluated.
• GMD_RESULTS (self-reference) — parent/child chains via PARENT_RESULT_ID.
• GMD_SAMPLE_RESULTS / COA views — reporting objects that aggregate results for certificate output.
• INV_ORGANIZATION_PARAMETERS / HR_OPERATING_UNITS — resolve ORGANIZATION_ID and QC_LAB_ORGN_CODE to descriptive names.