Inventory Transaction Based On Secondary UOM Is Not Possible In Mobile (MSCA - Handheld Device)

(Doc ID 2106249.1)

Last updated on FEBRUARY 16, 2016

Applies to:

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

Goal

How to transact in the secondary unit of measure (UOM) on mobile supply chain applications (MSCA)? 

User gets error "Required Field" attempting to skip primary quantity.

Error
Required Field

Steps
1. Navigate to a transaction on mobile (like Account Alias Receipt).
2. Enter account, item, subinventory.
3. User now wants to enter secondary quantity, but the primary is first and required.

What is working
In the application front end the User can transact in either primary or secondary unit of measure (UOM).

Business Example
Primary unit of measure on most finished good items is a weight (like Tons) while Secondary is quantity (like Each).
Users want all inventory transactions to be done in secondary UOM, but on handheld the Primary quantity field comes before the secondary quantity and primary quantity is required.
User can never get to the secondary quantity field to enter a value.
They must enter Primary Quantity.

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