R12: AP: APXRMTCH Match to Receipts Window Shows Incorrect Received Value in Receipt Quantity Section When Unit of Measure Changed (Doc ID 2947549.1)

Last updated on MAY 10, 2023

Applies to:

Symptoms

 In the Match to Receipts window when performing a match, the Received value in Receipt Quantity Section is incorrect when the unit of measure had been changed.

Scenario below:

Based on data collection from invoice analyzer it was found that there was some data discrepancy based on four fields
data comparison of two different transactions QUANTITY, UNIT_OF_MEASURE, PRIMARY_QUANTITY, PRIMARY_UNIT_OF_MEASURE.

TRANS_ID TRANSACTION_TYPE TRANSACTION_DATE QUANTITY UNIT_OF_MEASURE PRIMARY_QUANTITY PRIMARY_UNIT_OF_MEASURE PO_UNIT_PRICE
1 DELIVER 18-Aug-22 8 PACK OF 50 8 EACH 6.99
2 RECEIVE 18-Aug-22 8 PACK OF 50 8 EACH 6.99
3 DELIVER 18-Aug-22 20 PACK OF 10 200 EACH 11.46
4 RECEIVE 18-Aug-22 20 PACK OF 10 200 EACH 11.46

The discrepancy was seen between the above fields found in the RCV_TRANSACTIONS table.

QUANTITY, UNIT_OF_MEASURE, PRIMARY_QUANTITY, PRIMARY_UNIT_OF_MEASURE

The shared data shows two scenarios where there are different UNIT_OF_MEASURE and PRIMARY_UNIT_OF_MEASURE for two transactions.

First case of UNIT_OF_MEASURE (PACK OF 10) Quantity and Primary Quantity are different. (QTY : 20 and Primary QTY : 200).
Second case of UNIT_OF_MEASURE (PACK OF 50) Quantity and Primary Quantity are same (QTY : 8 and Primary QTY : 8).

In first case of UNIT_OF_MEASURE (PACK OF 10 ) the invoice receipt match is giving expected values but in case UNIT_OF_MEASURE (PACK OF 50)
wrong values are found in received quantity field. Expecting a quantity received value of 8 but it is showing 0.16.

As per the calculation for 8 quantity it is calculating 0.16, therefore, for 1 it will show 0.02. to make it 8 we need 400 in primary QTY. (400*0.02 = 8).

Cause

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