My Oracle Support Banner

Pay on Receipt Creates Duplicate Invoice After Transfer to Consigned (post Consumption advice) , Nullifying the Effect of Debit Memo (Doc ID 2568779.1)

Last updated on JULY 23, 2019

Applies to:

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

Symptoms

On : 12.2.4 version, Consigned Inventory

ACTUAL BEHAVIOR
---------------
Issue in Return to Vendor Process in Consignment Model

"Transfer to Consigned" (post consumption advice) process is going through fine and Debit Memo is also created. However, when Pay on Receipt runs later, a standard invoice is getting generated for the same quantity (transfer to consigned) that is nullifying the debit memo issued to the Vendor. This means no credit is received for the Transfer to Consigned / Return to the Vendor that was once paid to Supplier.

EXPECTED BEHAVIOR
-----------------------
 Pay on Receipt should not create duplicate invoices for Transfer to consigned transactions (after consumption advice)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Perform transfer to Consigned (after consumption Advice) > See debit memo is created (Expected)
2. Run Pay on Receipt > See it is creating another invoice from the consumption record that was processed for a Debit Memo. (mtl_consumption_transactions.consumption_processed_Flag = 'D' )

This is incorrect.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


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