Scribd
Upload
1K views2 pages

Applies To:: R12: IBY: Unable To Void Payment (Prepayment) From Workbench or Payments Manager (Doc ID 1326421.1)

The document discusses why payments made against prepayments cannot be voided in some cases in Oracle Payables. It provides the symptoms when this issue occurs and the solutions to fully unapply any prepayment applications and account the unapply events before retrying the void.

Uploaded by

r.n.pradeep
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1K views2 pages

Applies To:: R12: IBY: Unable To Void Payment (Prepayment) From Workbench or Payments Manager (Doc ID 1326421.1)

The document discusses why payments made against prepayments cannot be voided in some cases in Oracle Payables. It provides the symptoms when this issue occurs and the solutions to fully unapply any prepayment applications and account the unapply events before retrying the void.

Uploaded by

r.n.pradeep
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.

R12: IBY: Unable To Void Payment (prepayment) From Workbench Or Payments Manager (Doc ID 1326421.1)

In this Document

Symptoms
Cause
Solution
References

APPLIES TO:

Oracle Payments - Version 12.0.0 and later


Oracle Payables - Version 12.0.0 and later


platform.
Information in this document applies to any
grayed out

greyed out

SYMPTOMS

Unable to void a payment paid to a Prepayment from Actions window in the Payments Workbench (APXPAWKB).  The void checkbox is disabled / grayed out.

Or from Payments Manager, the following error is received:


    

Source product of payment xxxxx will not allow the payment to be voided. Please refer to the source product documentation for more information

CAUSE

The inability to void a check could be related to a prepayment in following cases:

Case 1: The check to be voided pays a standard invoice which was applied to a prepayment. 
The prepayment application has not been fully unapplied and accounted.

Case 2: The check to be voided pays a prepayment invoice and there is a standard invoice that was applied to the prepayment invoice.
The prepayment application has not been fully unapplied and accounted on the standard invoice.

Reference:

Oracle Payables User's Guide


Section: Void Payment Restrictions



INVOICES PAID BY ANOTHER PAYMENT:



cancel a related invoice if it was partially paid by a second payment. Instead, when you choose Cancel
When you void a payment, you cannot
Invoice, the system applies an "Invoice Cancel" hold to the invoice for your reference. You can release the hold manually in the Invoice Holds
tab.

CANCELLING ASSOCIATED INVOICES.


If you attempt to cancel an invoice that has been partially paid by another payment by using the Cancel Invoice Action, instead of cancelling
the invoice, Payables applies an Invoice Cancel hold to the invoice. This hold is manually releasable.
CLEARED PAYMENTS:

You cannot void a


payment that the bank has already cleared.
PREPAYMENTS:

You cannot void payment on a payment document that pays a prepayment that you have applied to an invoice. You must first unapply any
prepayments, and then you can void the payment.

SOLUTION

PREPAYMENTS

Solution for above cases.

Case 1:

1. In Invoice Workbench, verify that any prepayment application for the standard invoice has been fully unapplied.
2. If the invoice is in status Needs Revalidation, run validation for the invoice.
3. In Invoice Workbench, verify that the prepayment application has been accounted.  If not accounted, run accounting for the prepayment unapply event.
4. Retry Void of payment from Payments Workbench or Payments Manager

Case 2:

1. Identify the associated Standard Invoice.


2. In Invoice Workbench, verify that any prepayment application for the standard invoice has been fully unapplied.
3. If the invoice is in status Needs Revalidation, run validation for the invoice.
4. In Invoice Workbench, verify that the prepayment application has been accounted.  If not accounted, run accounting for the prepayment unapply event.
5. Retry Void of payment from Payments Workbench or Payments Manager

If unable to account prepayment unapplied events, refer to Doc Id 1281980.1 for solution.

CLEARED PAYMENTS

If the payment is reconciled in Cash Management statement, it is not possible to void a payment that the bank has already cleared.  So the payment should be unreconciled in Cash
Management to void the payment.
If the payment is manually cleared in Cash Management, the payment should be uncleared manually in Cash Management to void the payment.
For instructions on unclearing payments, reference Doc Id 2163932.1

 
If still cannot void payment and logging a Service Request, please upload the following:

1. Run MGD Doc Id 1360390.1 and see if any known data problem is found.

2. Run the Payments Funds Disbursement Analyzer (Doc ID 1587455.1) for the payment (check_id) trying to void, and invoice returned by below second query.
Below queries are run in the analyzer.

Query #1:
SELECT SUM(NVL(aid.amount,0))
FROM ap_invoice_payments_all aip,ap_invoices_all ai,
  ap_invoice_distributions_all aid,ap_invoice_distributions_all aid2
 WHERE aip.check_id = &CHECK_ID
  AND ai.invoice_id = aip.invoice_id
  AND ai.invoice_type_lookup_code = 'PREPAYMENT'
  AND ai.invoice_id = aid2.invoice_id
  AND aid2.line_type_lookup_code = 'ITEM'
  AND aid.prepay_distribution_id = aid2.invoice_distribution_id;

-> If amount returned <> 0 then it means that prepayment has not been unapplied completely.
Solution would be to unapply the prepayment and account that event.

Query #2:
SELECT aid.*
FROM ap_invoice_distributions_all aid_prepay,
  ap_invoice_payments_all aip,
  ap_invoices_all ai_prepay,
  ap_invoice_distributions_all aid,
  ap_invoice_distributions_all aidp
WHERE aip.check_id = &CHECK_ID
AND aip.invoice_id = ai_prepay.invoice_id
AND ai_prepay.invoice_type_lookup_code = 'PREPAYMENT'
AND aid_prepay.invoice_id = ai_prepay.invoice_id
AND aid_prepay.invoice_distribution_id = aid.prepay_distribution_id
AND aid.prepay_distribution_id IS NOT NULL
AND aid.parent_reversal_id IS NOT NULL
AND aid.amount > 0
AND nvl(aid.posted_flag, 'N') = 'N'
AND aid.invoice_id = aidp.invoice_id
AND aid.invoice_line_number = aidp.invoice_line_number
AND aid.parent_reversal_id = aidp.invoice_distribution_id
AND aid.prepay_distribution_id = aidp.prepay_distribution_id
AND nvl(aidp.posted_flag, 'N') = 'Y';

-> If this query returns data that means Prepayment unapplication event on the invoice has not been accounted.
Solution is to make sure the standard invoice, on which the Prepayment is applied, has been validated and create new accounting.

To obtain &CHECK_ID, you can run following sql:


   SELECT check_id,invoice_id FROM ap_invoice_payments_all WHERE check_id in
    (SELECT check_id FROM ap_checks_all WHERE check_number = &check_number ORDER BY check_id, invoice_id);

3. Run and upload output of APList for any invoice_id returned by the second query above or the invoice you have problem with.

REFERENCES

BUG:13687434 - CAN'T VOID PAYMENT OF PREPAYMENT INVOICE WITH STATUS NEGOTIABLE IN AP_CHECKS_ALL
Didn't find what you are looking for?

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy