Search Results gmd_uom_conversions_u1




Overview

GMD.GMD_UOM_CONVERSIONS is a table in the Oracle E-Business Suite Process Manufacturing (OPM) schema GMD that stores unit-of-measure (UOM) conversion factors derived from quality laboratory results. The table supports the "UOM Conversions Based on Quality Results" feature, in which a measured test result is used to calculate or propose a conversion factor between two units of measure and, when approved, to reflect that conversion in OPM Inventory. It resides in the APPS_TS_TX_DATA tablespace and holds 23 documented columns in the ETRM 12.2.2 physical schema. The table is part of the GMD quality management family, which includes specifications, tests, results, and dispositions.

Based on the foreign-key structure mined from the schema, this object is heuristically classified as a standalone table for Data Vault modeling purposes. It is not a hub, link, or satellite in the strict sense, because it does not exhibit the multi-parent integration pattern typical of a link; its foreign key to GMD_COMPOSITE_RESULTS is a dependent reference rather than an integration relationship. Analysts modeling the quality data domain could nonetheless treat the disposition-and-test combination as a natural business key and the conversion attributes as descriptive satellite data.

Key Information Stored

The table records both the conversion currently in effect and a conversion proposed by a quality result. Its primary key, GMD_UOM_CONVERSIONS_PK, is a composite of EVENT_SPEC_DISP_ID (the sample group specification disposition identifier) and TEST_ID. A second unique index, GMD_UOM_CONVERSIONS_U1, enforces uniqueness on EVENT_SPEC_DISP_ID combined with FROM_QTY_UOM_BASE and TO_QTY_UOM_BASE, establishing a business-key candidate that prevents duplicate base-UOM conversion pairs per disposition. This U1 index is the object most commonly searched for as "gmd_uom_conversions_u1."

The most significant columns include:

Common Use Cases and Queries

The principal use case is reviewing quality-driven conversion proposals and approving them for inventory. A typical query lists pending proposals for a disposition:

  • SELECT event_spec_disp_id, test_id, from_uom, to_uom, current_conversion, proposed_conversion FROM gmd.gmd_uom_conversions WHERE recommended_ind IS NULL AND delete_mark = 0;
  • Joining to quality results on RESULT_ID or COMPOSITE_RESULT_ID to trace the measured value behind each proposal.
  • Auditing approved conversions by filtering recommended_ind = 'Y' and reviewing the WHO columns for the approving user and timestamp.
  • Reconciling conversion pairs against the U1 business key to detect duplicate FROM/TO base-UOM combinations within a disposition.
  • Reporting current-versus-proposed variance by computing the difference between CURRENT_CONVERSION and PROPOSED_CONVERSION.

Related Objects

  • GMD.GMD_COMPOSITE_RESULTS — Referenced by the foreign key on COMPOSITE_RESULT_ID; join to retrieve composite result values.
  • GMD.GMD_SPEC_DISPOSITIONS — Likely parent of EVENT_SPEC_DISP_ID, linking conversions to the specification disposition.
  • GMD.GMD_SPEC_RESULTS — Source of RESULT_ID values referenced by this table.
  • GMD.GMD_TESTS — Provides TEST_ID context for each conversion row.
  • INV.MTL_UNITS_OF_MEASURE — Validation source for FROM_UOM and TO_UOM entries.
  • OPM Inventory conversion tables (INV.MTL_UOM_CONVERSIONS) — Target of RECOMMENDED_IND updates when proposed conversions are implemented.

Because the table is standalone per the mined relationship data, no additional parent-child integration joins are documented beyond the composite results reference.