RACUST: Bank Account Assignments of the Same Bank Account to Different Customer Accounts but All have Primary Flag set to Yes. (Doc ID 1469541.1)

Last updated on AUGUST 04, 2016

Applies to:

Oracle Trading Community - Version 12.0 to 12.2 [Release 12 to 12.2]
Information in this document applies to any platform.

Symptoms

Duplicate primary bank account assignments in Customer Master File after import of bank account data via customer interface (RACUST).

Multiple bank account assignments of the same bank account to different customer accounts but all have the primary flag set to Yes.  These records have been created through the customer interface.  This is causing funds capture to fail and the direct debit transactions can not be generated for the effected customer accounts.

If more than one customer has the same bank account then all bank accounts have primary flag set to Yes.

Example:
1. Customer Account 123 exists in Oracle.  It has no bank account assigned.
2. We run the customer interface with data to assign a bank account to this customer account 123.  This bank account already exists and is assigned to other customers
3. The bank account get assigned to the new customer BUT... the interface seems to update/insert multiple records into Iby_Account_Owners for this bank account with all set with the primary_flag = 'Y'.  

This is a corruption of the database by the interface because it is not possible to do this through the customer maintenance screens.  Only one owner can be the primary owner of the bank account.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms