Search Results gmd_uom_conversions_pk

Overview

GMD_UOM_CONVERSIONS is a GMD schema table belonging to the Oracle Process Manufacturing Product Development module. Its documented description, "UOM Conversions Based on Quality Results," identifies its purpose precisely: the table stores unit-of-measure conversion factors that are derived from laboratory or quality test outcomes rather than from static conversion setup. In process manufacturing, the relationship between an input quantity and an output quantity frequently depends on measured characteristics such as assay, potency, density, or concentration. Where a standard UOM conversion is insufficient, GMD_UOM_CONVERSIONS records both the conversion currently in force and a newly proposed conversion, alongside an indicator of whether the proposed value is recommended for adoption.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault model. In practice this suggests the table behaves as a standalone satellite-like construct with no upstream hub or link dependencies of its own; it anchors conversion records against event specification disposition and test identifiers. It is a transactional table with full WHO-column audit support and a soft-delete flag, characteristic of OPM application tables.

Key Information Stored

The table comprises 23 documented columns. The most significant are summarized below.

• EVENT_SPEC_DISP_ID and TEST_ID — Together these form the primary key GMD_UOM_CONVERSIONS_PK. They associate each conversion row with a specific event specification disposition and a specific quality test.
• COMPOSITE_RESULT_ID — Foreign key to GMD_COMPOSITE_RESULTS, tying the conversion to the aggregated quality result that justified it. This is the only documented foreign key relationship.
• RESULT_ID and RESULT_CONV_ID — Reference the individual quality result and the related conversion record.
• FROM_UOM and TO_UOM — The source and target units of measure for the conversion.
• CURRENT_CONVERSION and PROPOSED_CONVERSION — The conversion factor presently active versus the factor newly derived from quality data.
• RECOMMENDED_IND — Flag indicating whether the proposed conversion is recommended.
• FROM_UOM_BASE, TO_UOM_BASE, and PROPOSED_CONVERSION_BASE — Base-UOM equivalents of the corresponding conversion values.
• FROM_QTY_UOM, FROM_QTY_UOM_BASE, TO_QTY_UOM, and TO_QTY_UOM_BASE — Quantity amounts expressed in the respective UOMs and their base equivalents.
• DELETE_MARK — Standard OPM soft-delete indicator.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit columns.

A second unique index, GMD_UOM_CONVERSIONS_U1 (EVENT_SPEC_DISP_ID, FROM_QTY_UOM_BASE, TO_QTY_UOM_BASE), serves as a business-key candidate, ensuring that a given disposition and base-quantity pairing is unique. The surrogate primary key of EVENT_SPEC_DISP_ID and TEST_ID should be distinguished from this business-key constraint.

Common Use Cases and Queries

Typical reporting focuses on identifying where quality results imply a change to an established conversion factor. A straightforward query lists pending recommendations:

• SELECT event_spec_disp_id, test_id, from_uom, to_uom, current_conversion, proposed_conversion FROM gmd_uom_conversions WHERE recommended_ind = 'Y' AND delete_mark = 0;
• Join to GMD_COMPOSITE_RESULTS on composite_result_id to trace the underlying quality result that generated the proposal.
• Compare CURRENT_CONVERSION against PROPOSED_CONVERSION to quantify deviations, and use the base-UOM columns for a normalized cross-product view.
• Filter on creation and last-update dates to audit conversion changes across a period.

Because the table carries a DELETE_MARK, all production queries must include the predicate delete_mark = 0 to exclude logically deleted rows.

Related Objects

• GMD_COMPOSITE_RESULTS — The single documented foreign key target, joined via COMPOSITE_RESULT_ID.
• GMD_EVENT_SPEC_DISPOSITIONS (implied) — Referenced through EVENT_SPEC_DISP_ID in the primary key.
• GMD_QUALITY_TESTS (implied) — Referenced through TEST_ID in the primary key.
• GMD_RESULTS (implied) — Referenced through RESULT_ID.
• The GMD_UOM_CONVERSIONS_PK and GMD_UOM_CONVERSIONS_U1 indexes — enforced access paths for the primary and business keys.

Where metadata is limited, joins to quality and specification entities should be verified against the deployed schema, since the ETRM excerpt documents only the composite-results relationship explicitly.