Results for “gmd_tests_b”

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

Overview

GMD_TESTS_B is the base (non-translated) definition table for assay test specifications within the Oracle E-Business Suite Process Manufacturing Product Development module (GMD). It stores the header-level definition of a quality assay or test, including its operational context, validation ranges, and specification limits that govern how a quality result is evaluated against a product or batch. In EBS 12.1.1 and 12.2.2 the object resides in the GMD schema and is fully valid in the data dictionary, with a documented physical schema of 62 columns.

From a data-warehouse modeling perspective, the heuristic classification of GMD_TESTS_B is satellite-leaning. The table is keyed by a single surrogate identifier and carries descriptive attributes, specification limits, action codes, and audit columns, which is characteristic of a satellite attached to a business key rather than an independent hub or an associative link.

Key Information Stored

The primary key is enforced through GMD_TESTS_B_PK on QCASSY_TYP_ID, the internal surrogate identifier for the assay test type. A second unique constraint, GMD_TESTS_B_U1, spans ORGN_CODE and ASSAY_CODE, establishing the natural business key: an assay code is unique within an organization. Both columns should be treated as the strongest business-key candidates for integration and cross-reference purposes.

• QCASSY_TYP_ID — surrogate primary key of the assay test definition.
• ORGN_CODE — organization owning the test; foreign key to SY_ORGN_MST_B.
• ASSAY_CODE, ASSAY_DESC, ASSAY_TYPE, ASSAY_CLASS — the user-facing identity and categorization of the test.
• QCUNIT_CODE — unit of measure for the test result.
• MIN_VALID, MAX_VALID — valid numeric range accepted for the result.
• INSIDE_SPEC_MIN, INSIDE_SPEC_MAX, OUTSIDE_SPEC_MIN, OUTSIDE_SPEC_MAX — inner and outer specification limits used for acceptance decisions.
• INSIDE_MIN_ACTION_CODE, INSIDE_MAX_ACTION_CODE, OUTSIDE_MIN_ACTION_CODE, OUTSIDE_MAX_ACTION_CODE — disposition or action code triggered when a result falls in each band.
• ERROR_VAL_TYPE — error handling behavior for out-of-range results.
• TEXT_CODE — foreign key to QC_TEXT_HDR, linking explanatory text to the test.
• POTENCY_UOM, TEST_PROVIDER_CODE, TEST_OPRN_ID, TEST_OPRN_LINE_ID — potency unit and operational routing of the test.
• DELETE_MARK, IN_USE — soft-delete and active-status flags.
• ATTRIBUTE_CATEGORY through ATTRIBUTE30 — extensible descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical reporting needs include identifying all active tests for an organization, extracting specification limits for quality yield analysis, and joining test definitions to their captured results. Because DELETE_MARK is a soft-delete indicator, most operational queries should filter on DELETE_MARK = 2 (active) and IN_USE = 'Y'.

• Test master extraction: SELECT ASSAY_CODE, ASSAY_DESC, ASSAY_TYPE, QCUNIT_CODE, INSIDE_SPEC_MIN, INSIDE_SPEC_MAX FROM GMD_TESTS_B WHERE ORGN_CODE = :org AND DELETE_MARK = 2.
• Result-to-specification comparison: join GMD_TESTS_B to GMD_TEST_VALUES_B on QCASSY_TYP_ID to compare captured values against MIN_VALID/MAX_VALID.
• Disposition rule reporting: select the four action-code columns alongside the inner and outside spec limits to document acceptance logic.
• Organization-scoped uniqueness audit: SELECT ORGN_CODE, ASSAY_CODE, COUNT(*) FROM GMD_TESTS_B GROUP BY ORGN_CODE, ASSAY_CODE HAVING COUNT(*) > 1 to validate the GMD_TESTS_B_U1 constraint.

Related Objects

GMD_TESTS_B participates in a small but well-defined relationship set. GMD_TEST_VALUES_B references this table through QCASSY_TYP_ID, making it the principal child holding actual measured values. QC_TEXT_HDR supplies explanatory text via TEXT_CODE. SY_ORGN_MST_B supplies the owning organization via ORGN_CODE. The QCUNIT_CODE foreign key resolves against a unit-of-measure reference, and configuration of assay test definitions is maintained through the Process Manufacturing Product Development setup forms that write to this table. These four relationships, together with the unique business key on ORGN_CODE and ASSAY_CODE, define the principal integration and query paths for the object.