Results for “gmd_spec_mapping_gtmp”

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

Overview

GMD_SPEC_MAPPING_GTMP is a Global Temporary Table (GTMP) in the GMD schema, which supports Oracle Process Manufacturing Product Development. The table participates in the quality and specification management flow by mapping specification identifiers to test identifiers and to the enabling quality control specification records. In Oracle EBS 12.1.1 and 12.2.2, global temporary tables such as this one are typically used as transient staging or intermediate work areas during concurrent processing, interface loading, or report generation. Rows inserted into a global temporary table are visible only to the session that created them, and are generally purged at transaction or session commit, making the object unsuitable for permanent reporting storage.

From a heuristic Data Vault modeling perspective, the documented metadata classifies this object as standalone. As a modeling suggestion rather than a constraint, a standalone classification implies the table does not conform to a conventional hub, link, or satellite pattern; instead it may be treated as a transient work table whose records are not part of the persistent analytical model. Analysts should therefore not expect durable history in this object.

Key Information Stored

The documented physical schema for ETRM 12.2.2 lists eight columns. The most significant include:

• QC_SPEC_ID — the primary specification key referenced from QC_SPEC_MST via the documented foreign key GMD_SPEC_MAPPING_GTMP.QC_SPEC_ID → QC_SPEC_MST.
• SPEC_ID — the specification identifier being mapped within the working set.
• VR_SPEC_ID — the version-specific specification identifier used to distinguish revisions.
• SPEC_VR_ID — an additional specification version reference qualifying the mapping.
• TEST_ID — the quality test identifier associated with the specification.
• QC_REC_TYPE — the quality control record type that classifies the mapping.
• START_DATE and END_DATE — the effective date range for which the mapping is considered active.

The metadata does not document a surrogate primary key or unique business index, consistent with the table's transient nature. In practice QC_SPEC_ID functions as the principal business-key candidate because of its documented relationship to QC_SPEC_MST.

Common Use Cases and Queries

Because the table is temporary, use cases center on session-scoped processing rather than persistent analytics. Typical patterns include validating specification-to-test mappings, resolving effective-date windows, and joining back to master specification data. A representative query might join GMD_SPEC_MAPPING_GTMP to QC_SPEC_MST on QC_SPEC_ID to retrieve specification descriptions for the current session's working set:

• SELECT g.QC_SPEC_ID, g.SPEC_ID, g.TEST_ID, g.QC_REC_TYPE, m.SPEC_NAME FROM GMD.GMD_SPEC_MAPPING_GTMP g JOIN GMD.QC_SPEC_MST m ON g.QC_SPEC_ID = m.QC_SPEC_ID WHERE g.START_DATE <= SYSDATE AND (g.END_DATE IS NULL OR g.END_DATE >= SYSDATE);
• Filtering by QC_REC_TYPE to isolate a particular class of quality record during processing.
• Reconciling VR_SPEC_ID and SPEC_VR_ID values against version history to detect mapping gaps.

Reporting against this object should generally persist results to a permanent staging table before session termination.

Related Objects

The principal documented relationship is the foreign key from GMD_SPEC_MAPPING_GTMP.QC_SPEC_ID to QC_SPEC_MST. Other significant dependencies in the same functional area include GMD_SPEC_MST for base specification definitions, GMD_SPEC_VR for specification versions, GMD_TEST_MST for test master data, and quality control record structures such as GMD_QC_SPEC. Population of the temporary table is typically driven by GMD concurrent programs or API wrappers that resolve specification mappings before committing to permanent specification tables.