Results for “tester_id”

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

Overview

GMD_MASS_RESULTS_GT is a table in the GMD schema, owned by the Oracle Process Manufacturing Product Development module (GMD). Despite the "_GT" suffix commonly associated with global temporary tables in Oracle EBS, this object is documented in the ETRM 12.2.2 physical schema as a persistent table holding 83 columns. It stores mass-balance and laboratory test results captured during sampling events, tying quality specifications to measured values for process-manufactured items, lots, and sublots. Its role is to record the outcome of quality tests performed on samples, including numeric and character result values, specification limits, and in-spec/out-of-spec evaluations.

The ETRM metadata offers a heuristic Data Vault classification of standalone, mined from its foreign key structure. As a modeling suggestion, this indicates the table behaves more like an independent entity than a dependent link or satellite, though it carries implied associations to sampling events, test methods, and event specification dispositions.

Key Information Stored

The most significant columns include:

• SAMPLING_EVENT_ID — foreign key to GMD_SAMPLING_EVENTS, identifying the parent sampling event.
• SAMPLE_ID / SAMPLE_NO — the sample identifier and its business number.
• RESULT_ID — the result record identifier, likely a key candidate.
• TEST_ID / TEST_METHOD_ID — the quality test and its method; TEST_METHOD_ID references GMD_TEST_METHODS_B.
• RESULT_VALUE_NUM / RESULT_VALUE_CHAR — the measured numeric or character result.
• RESULT_DATE — timestamp of the test result.
• EVENT_SPEC_DISP_ID — foreign key to GMD_EVENT_SPEC_DISP, linking the result to its specification disposition.
• SPEC_ID / SPEC_VR_ID — the specification and version against which the result is evaluated.
• MIN_VALUE_NUM / TARGET_VALUE_NUM / MAX_VALUE_NUM — numeric specification limits.
• IN_SPEC_IND / EVALUATION_IND — flags indicating whether the result passes specification.
• ITEM_ID / LOT_ID / ORGANIZATION_ID — the item, lot, and organization context of the sample.

The surrogate primary key is not explicitly documented, but RESULT_ID or SAMPLING_EVENT_ID combined with TEST_ID and SEQ commonly serve as business-key candidates.

Common Use Cases and Queries

Typical scenarios include quality results reporting, out-of-spec investigation, and lot release decisions. A frequent query joins results to sampling events and items to list failing tests:

• Reporting all results for a given sampling event by joining on SAMPLING_EVENT_ID.
• Identifying out-of-spec lots using IN_SPEC_IND and the ABOVE_SPEC_MAX / BELOW_SPEC_MIN flags.
• Aggregating result values by TEST_METHOD_ID for laboratory trending.
• Reconciling specification limits (MIN_VALUE_NUM, MAX_VALUE_NUM) against measured values.

A representative pattern: SELECT r.RESULT_ID, r.TEST_ID, r.RESULT_VALUE_NUM, r.IN_SPEC_IND FROM GMD.GMD_MASS_RESULTS_GT r WHERE r.SAMPLING_EVENT_ID = :event_id.

Related Objects

The documented foreign keys point to the most significant related objects:

• GMD_SAMPLING_EVENTS — joined via SAMPLING_EVENT_ID.
• GMD_TEST_METHODS_B — joined via TEST_METHOD_ID.
• GMD_EVENT_SPEC_DISP — joined via EVENT_SPEC_DISP_ID.

Related specification and item tables (such as GMD_SPECS and inventory item master) are also commonly referenced through SPEC_ID and INVENTORY_ITEM_ID columns.