Search Results gmd_spec_results




Overview
Explore in AI Chat

Overview

GMD_SPEC_RESULTS is a table in the GMD schema (Process Manufacturing Product Development) that stores OPM Quality Specification Results. It records the outcome of evaluating quality specifications against actual analytical or operational results within Oracle E-Business Suite Process Manufacturing. The table is classified as VALID in the ETRM metadata for releases 12.1.1 and 12.2.2 and is central to quality data capture, specification conformance analysis, and disposition reporting. Its documented physical schema comprises 15 columns.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests that GMD_SPEC_RESULTS is modeled as its own independent entity rather than as a satellite hanging off a parent hub, despite carrying a composite primary-key structure. Modelers may therefore treat it as a fact-like table that links specification display events to individual results, with no documented outbound FK dependencies in the provided metadata.

Key Information Stored

The primary key, GMD_SPEC_RESULTS_PK, is a composite surrogate key defined over the columns EVENT_SPEC_DISP_ID and RESULT_ID. The same pair is also the sole documented unique index and therefore the only business-key candidate identified in the ETRM metadata.

  • EVENT_SPEC_DISP_ID — Identifies the specification display event (the quality event/context under which the specification was surfaced); first component of the composite primary key.
  • RESULT_ID — Identifies the individual specification result; second component of the composite primary key.
  • VALUE_IN_REPORT_PRECISION — The evaluated value rendered at the precision defined for the specification report.
  • IN_SPEC_IND — Indicator of whether the result falls within specification limits.
  • EVALUATION_IND — Indicator of the evaluation state of the result.
  • ACTION_CODE — Code describing the action applied to the result (for example, accept, reject, or re-test disposition).
  • ADDITIONAL_TEST_IND — Indicates whether additional testing is required for the result.
  • WF_RESPONSE — Stores the workflow response associated with the result, supporting Oracle Workflow-driven quality approvals.
  • UPDATE_INSTANCE_ID — Links the row to a particular update instance, supporting change tracking across quality data maintenance.
  • DELETE_MARK — Standard soft-delete flag; zero indicates an active row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns providing audit lineage.

Common Use Cases and Queries

Typical usage centers on quality disposition reporting, in-specification yield analysis, and investigation of results flagged for additional testing. A representative query retrieving in-specification outcomes for a given event is:

  • SELECT EVENT_SPEC_DISP_ID, RESULT_ID, VALUE_IN_REPORT_PRECISION, ACTION_CODE FROM GMD.GMD_SPEC_RESULTS WHERE EVENT_SPEC_DISP_ID = :event_id AND IN_SPEC_IND = 'Y' AND NVL(DELETE_MARK, 0) = 0;
  • Out-of-specification exception reports: filter on IN_SPEC_IND = 'N' and group by EVENT_SPEC_DISP_ID to quantify conformance failures.
  • Workflow backlog monitoring: select rows where WF_RESPONSE is null or ACTION_CODE is unresolved to surface pending quality approvals.
  • Audit and change tracking: join on UPDATE_INSTANCE_ID to correlate result changes with maintenance events.
  • Re-test planning: query ADDITIONAL_TEST_IND = 'Y' to produce worklists for additional analytical testing.

All queries should exclude soft-deleted rows via DELETE_MARK unless historical reconstruction is required.

Related Objects

The metadata identifies GMD_SPEC_RESULTS as standalone, with no mined FK relationships from this table to parents. The following objects are the most significant functional associates based on the GMD quality specification domain and the documented join columns:

  • GMD_SPEC_RESULTS_PK — Non-clustered primary-key constraint/index on (EVENT_SPEC_DISP_ID, RESULT_ID).
  • Event specification display tables (GMD_SPEC_DISP family, referenced via EVENT_SPEC_DISP_ID) — Supply the event-level context for each result.
  • Result definition tables (referenced via RESULT_ID) — Define the specification test/result attribute being evaluated.
  • Oracle Workflow runtime tables (WF_*), via WF_RESPONSE — Support notification and approval routing for quality results.
  • Update instance / audit tracking objects, via UPDATE_INSTANCE_ID — Provide change-version context.

Because the object is documented as standalone, integrators should not assume referential constraints on the two key columns; joins to specification display and result master tables are application-enforced and should be validated with outer joins when data quality is uncertain.