My Oracle Support Banner

UOM Mismatch In Quality Specifications When UOM Is Defined Only At Collection Element Level (Doc ID 3071844.1)

Last updated on FEBRUARY 12, 2025

Applies to:

Oracle Quality - Version 12.2.9 and later
Information in this document applies to any platform.

Symptoms

After selecting the specification, the following error occurs if the UOM is not explicitly set in the Specification Element form but only at element and plan level:

The system cannot convert the specification element's UOM into the collection plan's element UOM <UOM Code>. The UOM Conversion rule is not properly setup.


Steps to reproduce:
1. [R] Quality
2. [N] Setup > Specifications form
3. query/create new specification
4. Click on Elements and associate an element and a target value without entering the UOM.
5. Save.
6. [N] Setup > Collection Elements
7. Query the problematic element and make sure there is an UOM associated.
8. [N] Setup > Collection Plans
9. Query or create a new plan. Associate the specification to the plan and add the problematic specification element.
10. [N] Workbench > Collection Results
11. Enter Org and query the plan
12. Add data and select the specification
12. Error occurs.

WORKAROUND: Set the UOM manually at the specification elements level or use the Enter Quality Results form which is not affected by this issue.

 

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.