Last updated on MARCH 22, 2016
Applies to:Oracle Payables - Version 12.1.3 and later
Information in this document applies to any platform.
The void payment list of values contains the void payments that are already been referenced on another payment.
Steps to Recreate
1. Apply <patch 20359347> 'R12GTAS-CTA CHANGE REQUEST FOR TP BETC LOV AND EXCEPTIONS CR8Delete Reference' and <patch 20930361> 'CTA-PAYMENT RECLASS INCORRECT WHEN RECLASS IS DONE AT THE INVOICE LINE LEVEL' to enable the CTA Process enhancement.
2. Complete the stesp for payment reclassification per MOS <Note 1943006.1> as followings:
Entry through Payables: On the Payment form, the user voids a payment and then create a new invoice with new TAS/BETC information. The user creates a manual or refund a payment for the new invoice and references the voided payment document number in the Void Payment field on the new payment. The Void Payment list of values enables the user to select a payment if it meets the follow criteria:
-The referenced payment has been voided
-The referenced void payment is in the same GL Period as the new payment
-The referenced void payment has not already been referenced on another payment
-The Supplier and Supplier Site on the new payment are equal to Supplier and Supplier Site for the referenced void payment
-The Internal Bank Account for the referenced void payment has the same ALC defined as the Internal Bank Account for the new payment
-The referenced void payment amount must equal the new payment amount
3. See that the void payment list of values contains the void payments that are already been referenced on another payment. Also, there is no check to prevent selecting already referenced payment either and the actual CTA process reports them as duplicate reclassification.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms