Search Results gmd_qc_tests_b_pk

Overview

GMD_QC_TESTS_B is the base (or "B" language-independent) table that stores the master definition of quality control tests within the Oracle Process Manufacturing (OPM) Quality module. It resides in the GMD schema, which is shared by Oracle Process Manufacturing Product Development and Quality Management, and holds the template-level definition of a test — the specification, method, limits, and category — from which executable QC test instances are generated. In Oracle EBS 12.1.1 and 12.2.2 the object carries a VALID status and is exposed to the application through the OPM Quality setup and specification screens, most notably where analysts define the tests that appear on a specification or a laboratory worklist.

The ETRM metadata classifies this object heuristically as a standalone Data Vault entity. In modeling terms this suggests treating GMD_QC_TESTS_B as a hub: a table whose identity is governed by a stable business key rather than by transactional context, with no strong dependency linkage to other tables beyond the single foreign-key reference to the test method. The classification is a suggestion, not a physical constraint, but it usefully signals that the table functions as a reference or master record.

Key Information Stored

The table contains 64 documented columns. The most significant include:

• TEST_ID — the surrogate primary key, enforced by the GMD_QC_TESTS_B_PK constraint. This is the internal identifier referenced by all dependent transactional tables.
• TEST_CODE — the alternate unique key, enforced by GMD_QC_TESTS_B_U1. This is the user-facing business identifier of the test.
• TEST_METHOD_ID — the foreign key to GMD_TEST_METHODS_B that records how the test is performed.
• TEST_CLASS, TEST_TYPE, TEST_UNIT — the classification, category, and unit of measure of the test, governing how results are interpreted and displayed.
• MIN_VALUE_NUM, MAX_VALUE_NUM — the numeric lower and upper limits of the specification.
• EXP_ERROR_TYPE — the error or tolerance model applied when a result deviates.
• BELOW_SPEC_MIN, ABOVE_SPEC_MIN, BELOW_SPEC_MAX, ABOVE_SPEC_MAX — directional spec-limit fields defining excursion thresholds.
• BELOW_MIN_ACTION_CODE, ABOVE_MIN_ACTION_CODE, BELOW_MAX_ACTION_CODE, ABOVE_MAX_ACTION_CODE — the disposition or action triggered at each limit breach.
• EXPRESSION — a formula used for calculated tests.
• DISPLAY_PRECISION, REPORT_PRECISION — rounding and formatting controls.
• TEST_PROVIDER_CODE / TEST_PROVIDER_ID — linkage to the testing laboratory or provider.
• DELETE_MARK — the soft-delete flag used throughout OPM tables.
• ATTRIBUTE1…ATTRIBUTE30, ATTRIBUTE_CATEGORY — the standard Oracle DFF/descriptive-flexfield column set.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns.

Note that most columns are optional at the database level; the business-key pair TEST_ID and TEST_CODE, together with TEST_METHOD_ID, forms the reliable join and filter surface.

Common Use Cases and Queries

The primary scenarios are specification setup reporting, laboratory worklist prioritization, and audit of limit/action configurations. A typical lookup by business key:

SELECT test_id, test_code, test_method_id, test_class, test_unit,
       min_value_num, max_value_num, test_type, priority
  FROM gmd.gmd_qc_tests_b
 WHERE delete_mark = 0
   AND test_code = :p_test_code;

Reporting tests with their initiating method:

SELECT t.test_code, t.test_class, m.method_code
  FROM gmd.gmd_qc_tests_b t, gmd.gmd_test_methods_b m
 WHERE t.test_method_id = m.test_method_id
   AND t.delete_mark = 0
 ORDER BY t.test_class, t.test_code;

Extracting action codes and limits for a validation review:

SELECT test_code, min_value_num, max_value_num,
       below_min_action_code, above_max_action_code, exp_error_type
  FROM gmd.gmd_qc_tests_b
 WHERE delete_mark = 0
   AND (test_group_order IS NOT NULL OR test_provider_id IS NOT NULL);

Because the table is a standalone master, DBAs and analysts frequently join it to specification and result tables via TEST_ID and cross-check transactions in GMD_QC_RESULTS for tests whose configured limits are being breached.

Related Objects

• GMD_TEST_METHODS_B — referenced by TEST_METHOD_ID; supplies the procedure and equipment associated with each test.
• GMD_QC_TESTS_TL — the translation companion table, joined on TEST_ID, supplying the language-specific test name and description.
• GMD_QC_RESULTS — the transactional result table that links back to GMD_QC_TESTS_B via TEST_ID.
• GMD_SPEC_TESTS — associates a specification with the tests defined here.
• GMD_QC_SPECS — the specification master whose validity depends on the test definitions.
• GMD_QC_TEST_GROUPS — groups tests for worklist generation; referenced through TEST_GROUP_ORDER.
• GMD_TEST_PROVIDERS — resolves the TEST_PROVIDER_ID/CODE linkage to the external or internal laboratory.

Directly or indirectly, these objects form the quality-testing data web surrounding GMD_QC_TESTS_B, with TEST_ID (surrogate PK) and TEST_CODE (business-key unique index) serving as the stable points of reference.