My Oracle Support Banner

R12: AP: Remit-To Bank Account for Outstanding Invoices is Not Replaced with an Another Bank Account as Expected When Setting the End Date to the Bank Account (Doc ID 2392734.1)

Last updated on NOVEMBER 09, 2018

Applies to:

Oracle Payables - Version 12.0.0 and later
Information in this document applies to any platform.

Symptoms

The Remit-To bank account(Remit-To Bank Account Name, Remit-To Bank Account Number) for an outstanding invoice is set to Bank Account A. When setting the end date for Bank Account A, the Remit-To bank account for the invoice is expected to be replaced with an another Bank Account B. But the Remit-To bank account for the invoice is updated to null.

ACTUAL BEHAVIOR
---------------
Existing Bank Account A (Remit-To Bank Account Name, Remit-To Bank Account Number ) was changed to null.

EXPECTED BEHAVIOR
-----------------------
Existing Bank Account A (Remit-To Bank Account Name, Remit-To Bank Account Number ) was changed to other available Bank Account B.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. On the Invoice Workbench, confirm invoice created with Existing Bank Account A.
2. Add a new Bank Account B to the same supplier.
3. End-date Existing Bank Account A, see the following Warning message:
   This bank account is attached to 1 documents payable.Would you like to replace the bank account in the documents payable with other available bank account as per priority?
4. Click "Yes", but Existing Bank Account A not be changed to B, changed to Null.

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
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.