In Miscellaneous Transaction Form (INVTTMTX) , the UOM LOV Opens Even When a Valid UOM is Entered or Defaulted - How Do We Prevent This? (Doc ID 2150625.1)

Last updated on JULY 14, 2016

Applies to:

Oracle Inventory Management - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

Item "AS1111" is defined with primary unit of measure (UOM) code BaP.

There are conversions setup to convert BaP into 2 other UOM codes named bAP and BAp.

Note that all 3 UOM codes use the same letters but with different letter case.

When entering a Miscellaneous Transactions (issue or receipt) for this item, the primary UOM BaP defaults into the form.
Even though a correct/valid UOM is already populated, the UOM LOV still opens displaying the 3 UOM codes BaP, bAP and BAp.
As a result, users are sometimes choosing the wrong UOM.

Why is this occurring and is there a way to prevent it?

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms