ASNI UOM Code Conversion Not Working When Using ASN_TYPE as Key (Doc ID 2097157.1)

Last updated on FEBRUARY 05, 2016

Applies to:

Oracle Inventory Management - Version 12.0.0 to 12.2.5 [Release 12.0 to 12.2]
Information in this document applies to any platform.

Symptoms

PO is using Each, Supplier is using EA

ASNI data file comes in with EA

Code conversion setup between Each and EA

However, RCV_TRANSACTIONS_INTERFACE.UNIT_OF_MEASURE is still populated with EA

Here are the Steps:
1) using an existing Conversion Category (UOM) for which one key checked.

2) On the Assign Category form, ASN_TYPE as Key1

3) On the Define Conversion form

    ASNI as the Key1 Value
    Internal Value is Each. External is EA

4) Data File:

    record# 2000, position# 90 with null   ===> SHIPPED_UNIT_CODE_INT  
    record# 2000, position# 100 with EA  ===> SHIPPED_UNIT_CODE_EXT1

5) Run ASNI inbound

6) RCV_TRANSACTIONS_INTERFACE.UNIT_OF_MEASURE is getting populated with EA

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