Search Results gmd_composite_results




Overview
Explore in AI Chat

Overview

GMD_COMPOSITE_RESULTS is a table in the GMD schema belonging to the Oracle Process Manufacturing (OPM) Product Development module, which encompasses Quality Management functionality. The table stores OPM Quality Composite results — aggregated statistical summaries derived from multiple individual test results that are combined into a single representative composite value. Composite testing is used in process manufacturing when a meaningful quality assessment requires statistical consolidation across samples, lots, or time periods rather than evaluation of a single measurement.

Under the heuristic Data Vault classification mined from the foreign key structure, GMD_COMPOSITE_RESULTS is modeled as a standalone object. No parent tables reference it through inbound foreign keys in the documented relationship data; instead, it acts as a referenced parent for downstream tables. In Data Vault terms this suggests a hub-like posture, where COMPOSITE_RESULT_ID serves as the durable business key anchor. The table exists in both Oracle EBS 12.1.1 and 12.2.2, with a documented physical schema of 59 columns in the 12.2.2 ETRM reference.

Key Information Stored

The surrogate primary key is COMPOSITE_RESULT_ID, enforced by the unique index GMD_COMPOSITE_RESULTS_PK. A second unique index, GMD_COMPOSITE_RESULTS_U1, covers (COMPOSITE_SPEC_DISP_ID, TEST_ID) and represents the principal business-key candidate: a composite result is uniquely identified by the combination of the composite specification/display context and the specific quality test performed.

Common Use Cases and Queries

The most frequent access pattern is retrieval of composite statistics for a given test and specification context, typically for quality reporting, certificate-of-analysis generation, or laboratory dashboarding. A representative query joins the composite to its test definition:

SELECT cr.composite_result_id, cr.test_id, cr.mean,
       cr.standard_deviation, cr.sample_total, cr.in_spec_ind
FROM   gmd_composite_results cr
WHERE  cr.composite_spec_disp_id = :spec_disp_id
AND    cr.delete_mark = 0;

A second common pattern resolves the U1 business key directly, retrieving the single composite row for a spec/test pair. Out-of-specification monitoring queries filter on IN_SPEC_IND and NON_VALIDATED_RESULT to isolate results requiring investigation or workflow action. Hierarchical reporting walks PARENT_COMPOSITE_RESULT_ID to reconstruct nested composite relationships. Batch or lot-level trending reports aggregate MEAN and STANDARD_DEVIATION over time to detect process drift, and the attribute flexfield columns support customer-specific reporting extensions without schema modification.

Related Objects

  • GMD_COMPOSITE_RESULT_ASSOC — references GMD_COMPOSITE_RESULTS via COMPOSITE_RESULT_ID; stores the association between a composite result and its constituent source results.
  • GMD_UOM_CONVERSIONS — references COMPOSITE_RESULT_ID; holds unit-of-measure conversion data tied to composite result values.
  • GMD_COMPOSITE_RESULTS_PK — primary key unique index on COMPOSITE_RESULT_ID.
  • GMD_COMPOSITE_RESULTS_U1 — unique index on (COMPOSITE_SPEC_DISP_ID, TEST_ID), the business-key candidate.
  • GMD specification and test definition tables — provide the TEST_ID and COMPOSITE_SPEC_DISP_ID context that scopes each composite record.

Because the documented schema is largely standalone, integrations should treat GMD_COMPOSITE_RESULTS as an authoritative parent record, with GMD_COMPOSITE_RESULT_ASSOC and GMD_UOM_CONVERSIONS as the primary dependent children when tracing composite results across the OPM Quality data model.