Search Results gmd_test_methods_b_u1

Overview

GMD_TEST_METHODS_B is the base table in the Oracle E-Business Suite Process Manufacturing Product Development module (GMD) that stores OPM Quality Test Method definitions. A test method describes a specific quality procedure — its code, the quantity of sample it consumes, the unit of measure, its expected duration, and any associated resource, kit, or text requirements. Test methods are the building blocks of quality specifications: specifications select tests, and tests reference the test method that governs how the measurement is performed. Within Oracle EBS 12.1.1 and 12.2.2, this table is therefore a foundational quality configuration object for process manufacturing organizations, and it is explicitly edition-enabled in 12.2.2, as evidenced by the ZD_EDITION_NAME column participating in both unique indexes.

From a heuristic Data Vault perspective, the ETRM relationship mining classifies this object as standalone — it owns its own business key and is not treated as an association table. A reasonable modeling suggestion is to treat GMD_TEST_METHODS_B as a hub-like reference for test methods, with the descriptive columns (quantities, durations, UOM, attributes) forming satellite-type content. This is a suggestion only, derived from the FK topology, not an enforced Oracle design.

Key Information Stored

The table exposes 56 documented columns. The most significant are:

• TEST_METHOD_ID — the surrogate primary key, defined by GMD_TEST_METHODS_B_PK together with ZD_EDITION_NAME.
• TEST_METHOD_CODE — the user-facing business key, enforced by the unique index GMD_TEST_METHODS_B_U1 (TEST_METHOD_CODE, ZD_EDITION_NAME). This is the value users search on and the value referenced by child tables.
• TEST_QTY and TEST_QTY_UOM/TEST_UOM — the sample quantity consumed and its unit of measure.
• TEST_DURATION, DAYS, HOURS, MINUTES, SECONDS — the expected elapsed time for the test, stored both as a consolidated duration and in component units.
• TEST_REPLICATE and DISPLAY_PRECISION — the number of replicates to run and the numeric precision for displaying results.
• RESOURCES — resource or equipment requirements for performing the method.
• TEST_KIT_ITEM_ID, TEST_KIT_INV_ITEM_ID, and TEST_KIT_ORGANIZATION_ID — the inventory item and organization identifying a test kit associated with the method.
• TEXT_CODE — identifies attached descriptive text (procedure narrative).
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard EBS extensibility flexfield block.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the mandatory Who-column audit set.
• DELETE_MARK, MIGRATED_IND, ZD_EDITION_NAME — logical deletion, migration, and Editioning flags.

Common Use Cases and Queries

The primary scenario is retrieving and validating test method definitions for specification and quality result processing. A typical lookup by business key is:

• SELECT test_method_id, test_method_code, test_qty, test_uom, display_precision FROM gmd_test_methods_b WHERE test_method_code = :p_code AND NVL(delete_mark, 0) = 0;

Reporting scenarios include listing methods with their durations or resource requirements for laboratory workload planning, and joining results back to methods to analyze outcome trends:

• SELECT r.test_method_id, m.test_method_code, COUNT(*) FROM gmd_results r, gmd_test_methods_b m WHERE r.test_method_id = m.test_method_id GROUP BY r.test_method_id, m.test_method_code;

Extensibility reporting frequently queries the ATTRIBUTE columns for customer-specific data captured during implementation.

Related Objects

Four documented foreign keys establish the dependency footprint of this table, each joining on TEST_METHOD_ID:

• GMD_QC_TESTS_B — quality test definitions (TEST_METHOD_ID → GMD_TEST_METHODS_B).
• GMD_SPEC_TESTS_B — specification test assignments (TEST_METHOD_ID → GMD_TEST_METHODS_B).
• GMD_RESULTS — captured quality results (TEST_METHOD_ID → GMD_TEST_METHODS_B).
• GMD_MASS_RESULTS_GT — global temporary table of mass result processing (TEST_METHOD_ID → GMD_TEST_METHODS_B).

Because these children retain the surrogate TEST_METHOD_ID rather than the code, the unique index GMD_TEST_METHODS_B_U1 is the mechanism that guarantees TEST_METHOD_CODE remains unambiguous per edition. Deletion should be handled through DELETE_MARK rather than physical removal, given the referential dependency from results and specification data.