E1: 43: P4310 Should Search For UOM in a Join Between F41002 and F41003

(Doc ID 1993040.1)

Last updated on NOVEMBER 05, 2015

Applies to:

JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

When P4310 searches for unit of measure first in F41002, if it does not find it then looks in F41003 and if it still does not find it then displays UOM error, P4310 should also join the data from F41002 and F41003.

 

Example:

conversion set in F41002: 1UN=1LT

conversion set in F41003: 1MP=1000UN

 

Current behaviour:

If item is set with first UOM=LT, second UOM=UN and purchasing UOM=MP then, when creating order, P4310 returns error due to the fact that the conversion between MP and LT is not defined in any of F41002 or F41003.

 

Desired behaviour:

If item is set with first UOM=LT, second UOM=UN and purchasing UOM=MP then, when creating order, P4310 should search the conversion between MP and LT in a join between F41002 and F41003 (in both tables in the same time).

Cause

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