Search Results gmd_event_spec_disp

Overview

The GMD_EVENT_SPEC_DISP table is a core data object within the Oracle Process Manufacturing (OPM) Product Development module (GMD) of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. As indicated by its description, "OPM Quality Event Specification Display," this table serves as a repository for managing the display and presentation logic of quality specifications linked to manufacturing events. In the OPM Quality Management framework, events trigger the collection of quality data against predefined specifications. This table governs how those specification details are rendered and organized for user interaction within the application's forms and interfaces, acting as a configuration layer between the underlying specification data and its user-facing presentation.

Key Information Stored

The table's primary purpose is to map display attributes to quality event specifications. The documented metadata confirms a primary key column, EVENT_SPEC_DISP_ID, which uniquely identifies each display configuration record. While the full column list is not detailed in the provided excerpt, based on its function, typical columns would include foreign keys to core specification and event tables, along with display-control attributes. These likely encompass sequence numbers for ordering, flags to control visibility or mandatory entry status, display prompts or labels, and references to the associated specification (from tables like GMD_SPECIFICATIONS) and the quality event (from tables like GMD_EVENTS). The structure ensures that for a given quality event, the relevant specifications are presented to the user in a defined, controlled manner.

Common Use Cases and Queries

The primary use case is the dynamic generation of data collection screens or lists of tests during quality transaction processing, such as recording results for in-process checks, ingredient receipt, or finished product testing. A common reporting need is to list all display configurations for a specific event or specification to audit or modify the user interface setup. Sample SQL patterns often involve joining to event and specification master tables.

• Retrieving Display Setup for an Event: SELECT * FROM GMD.GMD_EVENT_SPEC_DISP WHERE event_id = :p_event_id ORDER BY display_sequence;
• Identifying Specifications with Active Display Rules: SELECT spec_id, spec_vr FROM GMD.GMD_EVENT_SPEC_DISP WHERE enabled_flag = 'Y' GROUP BY spec_id, spec_vr;

These queries support configuration validation and troubleshooting of the quality data entry workflow.

Related Objects

The table is central to the OPM Quality schema and has defined relationships with other key GMD tables. The documented primary key constraint, GMD_EVENT_SPEC_DISP_PK on EVENT_SPEC_DISP_ID, is referenced by foreign keys in related transactional or child tables. While the specific foreign key relationships are not listed, this table is inherently linked to:

• GMD_EVENTS: The master table for quality events. GMD_EVENT_SPEC_DISP typically contains an EVENT_ID column as a foreign key to this table.
• GMD_SPECIFICATIONS: The master table for quality specifications. GMD_EVENT_SPEC_DISP typically contains foreign key columns like SPEC_ID and SPEC_VR (specification version).
• Transactional Tables (e.g., GMD_RESULTS): Tables storing actual quality results may reference GMD_EVENT_SPEC_DISP to preserve the display context under which data was collected.

Joins are typically performed on EVENT_ID, SPEC_ID, and SPEC_VR to retrieve a comprehensive view of event-specific quality requirements and their presentation rules.