Results for “result_id”

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

Overview

GMD_COMPOSITE_RESULT_ASSOC is an Oracle E-Business Suite table owned by the GMD schema and delivered as part of the Process Manufacturing Product Development module (OPM Quality). Its documented purpose is to store the association between composite quality results and the individual quality results that make up those composites. In OPM Quality, a composite result aggregates multiple specification or quality results into a single logical outcome; this table defines exactly which detail results are members of a given composite and whether each member is included or excluded from the aggregation.

The heuristic Data Vault classification mined from the foreign key structure is standalone. From a modeling perspective, this suggests the table can be treated as an association or link-style entity that records the relationship between a composite result and a member result rather than as a full hub or satellite. It carries its own descriptive attribute (EXCLUDE_IND) and standard audit columns, so consumption in a warehouse should treat it as a relationship record keyed by the composite and member result identifiers.

Key Information Stored

The documented physical schema for 12.2.2 contains 8 columns. The most important are:

• COMPOSITE_RESULT_ID — the identifier of the parent composite quality result; this is also the documented foreign key referencing GMD_COMPOSITE_RESULTS.
• RESULT_ID — the identifier of the individual quality result associated with the composite. Together with COMPOSITE_RESULT_ID, it forms the effective business key of the association.
• EXCLUDE_IND — an indicator controlling whether the associated result is excluded from the composite outcome. This is the primary non-key business attribute and drives calculation behavior.
• CREATION_DATE, CREATED_BY — standard audit columns capturing when and by whom the association row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent modification and the login that performed it.

No dedicated surrogate primary key column beyond the composite/member identifier pair is documented in the provided metadata, and no unique index is explicitly listed. The COMPOSITE_RESULT_ID / RESULT_ID pair should be regarded as the business-key candidate for joins and de-duplication.

Common Use Cases and Queries

Typical scenarios include reproducing composite quality result composition, auditing which detail results contributed to a composite, and reporting excluded members. A basic join to the parent composite result table follows:

• List all member results for a composite: SELECT a.RESULT_ID, a.EXCLUDE_IND FROM GMD.GMD_COMPOSITE_RESULT_ASSOC a WHERE a.COMPOSITE_RESULT_ID = :composite_result_id;
• Identify composites that include a specific result: SELECT a.COMPOSITE_RESULT_ID FROM GMD.GMD_COMPOSITE_RESULT_ASSOC a WHERE a.RESULT_ID = :result_id AND NVL(a.EXCLUDE_IND,'N') = 'N';
• Audit recent changes using the standard audit columns: filter on LAST_UPDATE_DATE and join LAST_UPDATED_BY to FND_USER for user attribution.

Reporting use cases include quality result traceability, composite result reconstruction for regulatory submissions, and reconciliation of excluded versus included members in aggregated quality outcomes.

Related Objects

• GMD_COMPOSITE_RESULTS — the documented parent table referenced by COMPOSITE_RESULT_ID; join on COMPOSITE_RESULT_ID.
• GMD_QUALITY_RESULTS (and related result tables in the GMD schema) — the logical source of RESULT_ID values for member detail results.
• GMD_SPEC_RESULTS — specification result data that frequently feeds individual quality results.
• FND_USER — referenced indirectly through CREATED_BY and LAST_UPDATED_BY for audit attribution.
• GMD_COMPOSITE_RESULT_ASSOC-related OPM Quality concurrent programs and APIs — processes that build composite results and populate this association table.