Aid To Understanding Why Debit Memo Are Not Generated by Receiving Returns (Doc ID 1376433.1)

Last updated on JULY 01, 2024

Applies to:

Goal

The aim of this document is to assist in understanding why a Debit Memo is not automatically generated when a Return To Supplier is performed in the Receiving module.

When a Return To Supplier is entered on the Receiving Return form (RCVTXERE), the Receiving Transaction Processor (RTP) is called.
The RTP is constructed of libraries, one of which is rvtuq.lpc.
The library contains the function rvtuqdebitmemo which then calls the AP API AP_AUTO_DM_CREATION_PKG

It is this API that is responsible for generating the Debit Memo.

There are seven conditions that must be meet for a Debit Memo to be generated:

1. The supplier site has to be marked to allow RTS transactions.
2. There must be an original invoice already in AP for the item being returned.
3. The PO and the original Invoice must be to the same Supplier Site.
4. The Supplier Site must be marked as BOTH a Pay Site and a Purchasing Site.
5. The return quantity cannot cause the quantity invoiced to go negative and the return quantity must be equal to or less than the quantity invoiced.
6. The Create Debit Memo check-box must also be turned on in the Receipt form.
7. The return must be to the Supplier, and not to Receiving.

To assist in checking some of these conditions, the following SQL may be used which will prompt for the Purchase Order number in question:

The SQL will return values for three of the seven conditions:

1. The supplier site has to be marked to allow RTS transactions (PVS.Create Debit)
2. There must be an original invoice already in AP for the item being returned. (AP.Invoice Num)
4. The Supplier Site must be marked as BOTH a Pay Site and a Purchasing Site (PVS.Is a Pay Site & PVS.Is a Purchasing Site)

Solution

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