My Oracle Support Banner

Unable To Override The Primary Remittance Bank Account On Automatic Receipt Batch (Doc ID 2474371.1)

Last updated on NOVEMBER 10, 2019

Applies to:

Oracle Fusion Receivables Cloud Service - Version 11.13.18.05.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.13.18.05.0 version, Receipts

ACTUAL BEHAVIOR
=================
Unable to override the primary remittance bank on Automatic Receipt batch

The customer is using Automatic Receipts to create receipts and apply to the transaction.
They defined one automatic receipt method for this purpose and add multiple remittance bank accounts. Although they select one bank account (not the primary) when creating the Automatic Receipts Batch, the system saves the primary bank account and
creates the receipt with this account instead of the one the customer needs.

Steps to Recreate the issue
=====================
1. Create Transaction and select a receipt method (including the correct remittance bank account)
2. Create Automatic Receipts selecting the same receipt method (including the correct remittance bank account)
3. Receipt Batch created with primary bank account attached to the receipt method

EXPECTED BEHAVIOR
=================
The expectation is to create receipt batches for transactions based on the remittance bank account selected

BUSINESS IMPACT
===============
Due to this issue the customer cannot create automatic receipts for bank accounts different than the primary bank account

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


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