Search Results gmd_technical_data_dtl

Overview

GMD_TECHNICAL_DATA_DTL is a Process Manufacturing Product Development (GMD) table that stores technical parameter data detail records. It holds the individual parameter values that make up a technical data definition, functioning as the child detail store for the technical parameter specifications used in product development and formulation workflows. The table resides in the GMD schema and is classified as VALID in the ETRM repository for both Oracle EBS 12.1.1 and 12.2.2.

The object is documented as a standalone entity under the heuristic Data Vault classification mined from its foreign key structure. In Data Vault modeling terms, this suggests the table is best treated as a satellite-like structure capturing descriptive attributes, or as a detail/link component, rather than as a conventional hub. The absence of outbound foreign keys to parent hubs implies the table carries descriptive payload keyed against technical data and parameter identifiers supplied and enforced at the application layer.

Key Information Stored

The table is documented with 12 columns. The composite primary key, enforced by the GMD_TECHNICAL_DATA_DTL_PK unique index, comprises TECH_DATA_ID and TECH_PARM_ID. TECH_DATA_ID identifies the parent technical data record, while TECH_PARM_ID identifies the specific technical parameter being captured. Together they form the business-key candidate and uniquely identify each detail row.

• TECH_DATA_ID — Surrogate/composite key component pointing to the technical data header context.
• TECH_PARM_ID — Composite key component identifying the individual technical parameter.
• SORT_SEQ — Display or processing sequence for the parameter detail.
• TEXT_DATA — Character value captured for the parameter.
• NUM_DATA — Numeric value captured for the parameter.
• BOOLEAN_DATA — Boolean (Yes/No) value captured for the parameter.
• TEXT_CODE — Coded value reference associated with the parameter entry.
• CREATION_DATE, CREATED_BY — Standard audit stamp for row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit stamps for the most recent change, supporting concurrent-user tracking and change reporting.

The TEXT_DATA, NUM_DATA, BOOLEAN_DATA, and TEXT_CODE columns form a polymorphic value store, allowing each parameter to carry values of differing data types within one uniform detail structure.

Common Use Cases and Queries

Typical usage centers on retrieving and reporting the parameter values attached to a technical data record, and on joining details back to their parent specification. Common patterns include:

• Listing all parameters and their captured values for a given TECH_DATA_ID, ordered by SORT_SEQ, to reconstruct the specification detail.
• Auditing who created or last modified a parameter value using CREATED_BY, LAST_UPDATED_BY, and the corresponding date columns.
• Extracting numeric results via NUM_DATA for statistical or QC reporting while filtering to the relevant TECH_PARM_ID set.
• Detecting coded versus free-text captures by comparing TEXT_CODE against TEXT_DATA population.

A representative query selects the parameter values for one technical data record:

• SELECT d.tech_parm_id, d.sort_seq, d.text_data, d.num_data, d.boolean_data, d.text_code FROM gmd_technical_data_dtl d WHERE d.tech_data_id = :tech_data_id ORDER BY d.sort_seq;

Because the table is standalone, joins to headers or parameter masters are performed on the key components rather than through declared foreign keys.

Related Objects

Although the documented metadata records no formal foreign keys, the key components relate this detail table to the technical data header and parameter definition objects within the GMD product development model. The most significant related objects are:

• Technical data header object — joined on TECH_DATA_ID to retrieve the specification context.
• Technical parameter master/definition object — joined on TECH_PARM_ID to resolve parameter names, data types, and validations.
• GMD_TECHNICAL_DATA_DTL itself as parent in business-key joins on (TECH_DATA_ID, TECH_PARM_ID).
• Process Manufacturing specification and formulation tables in the GMD schema that consume technical data for product development.
• Standard audit/user references (FND_USER, FND_LOGINS) joined on CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for user attribution.

Because the table is classified as standalone, referential integrity is largely enforced by application logic and concurrent-process code rather than database constraints.