Results for “delete_mark”

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

Overview

GMD_SAMPLE_SPEC_DISP is a table within the GMD schema, belonging to the Oracle Process Manufacturing (OPM) Product Development module. Its documented description is "OPM Quality Sample Specification Display." In Oracle EBS 12.1.1 and 12.2.2, the GMD schema supports process manufacturing quality and product development functions, and this object serves as a display-oriented store that associates quality event specification results with the samples to which they apply. It is used by the OPM Quality Management functionality to present specification and disposition information for samples tested against event-level specifications.

Based on the FK and dependency structure provided in the metadata, the heuristic Data Vault classification for this object is standalone. This is a modeling suggestion rather than a physical constraint; it implies that, from a Data Vault perspective, GMD_SAMPLE_SPEC_DISP could be represented as an independent construct rather than a strict hub, link, or satellite. In practice the table behaves as a composite-key association between event specification displays and samples, with descriptive attributes attached.

Key Information Stored

The table is documented with nine columns and a composite primary key. The most important data elements are:

• EVENT_SPEC_DISP_ID — Part of the composite primary key; identifies the event specification display record associated with the row.
• SAMPLE_ID — Part of the composite primary key; identifies the OPM quality sample to which the specification display applies.
• DISPOSITION — Holds the disposition outcome or status for the sample specification display, such as accept, reject, or a quality decision code.
• DELETE_MARK — Standard Oracle EBS soft-delete indicator; a nonzero value denotes a logically deleted row.
• CREATION_DATE — Timestamp when the record was created.
• CREATED_BY — User identifier responsible for creating the record.
• LAST_UPDATE_DATE — Timestamp of the most recent update; central to audit and incremental extraction.
• LAST_UPDATED_BY — User identifier responsible for the most recent change.
• LAST_UPDATE_LOGIN — Login/session identifier for the updating session, supporting audit traceability.

The surrogate/business key is represented by the unique index GMD_SAMPLE_SPEC_DISP_PK over (EVENT_SPEC_DISP_ID, SAMPLE_ID). No separate single-column surrogate key is documented; the composite pair serves as the primary key and the principal business-key candidate.

Common Use Cases and Queries

Typical uses involve reporting on sample dispositions against specifications, auditing changes to quality results, and integrating OPM quality data into downstream analytics. Because DELETE_MARK and LAST_UPDATE_DATE are present, this table is well suited to incremental (high-water-mark) extraction.

• Retrieve all active specification displays for a given sample: SELECT * FROM gmd.gmd_sample_spec_disp WHERE sample_id = :p_sample_id AND NVL(delete_mark,0) = 0;
• Report disposition counts by status: SELECT disposition, COUNT(*) FROM gmd.gmd_sample_spec_disp WHERE NVL(delete_mark,0)=0 GROUP BY disposition;
• Incremental load pattern: SELECT * FROM gmd.gmd_sample_spec_disp WHERE last_update_date >= :last_run AND NVL(delete_mark,0)=0;
• Join to event specification display data using event_spec_disp_id and to sample master data using sample_id to enrich quality reports.

Related Objects

The metadata identifies the table as standalone with no documented foreign keys beyond its composite primary key. The following related objects are the most significant based on the join columns EVENT_SPEC_DISP_ID and SAMPLE_ID:

• Event specification display objects (in the GMD event specification area) — joined on EVENT_SPEC_DISP_ID to retrieve the specification context.
• GMD_SAMPLES / sample master — joined on SAMPLE_ID to retrieve sample details.
• OPM Quality event specification tables — provide the specification definitions referenced by the display identifier.
• Quality disposition and results views in GMD that aggregate specification displays for reporting.
• APIs and concurrent programs within OPM Product Development/Quality that read or maintain sample specification display records.

Because the metadata documents no outbound foreign keys, joins to related objects rely on the business columns EVENT_SPEC_DISP_ID and SAMPLE_ID rather than enforced constraints.