Account BIC Is Not Resolving Properly For SDD Transactions. System Is Deriving Default Branch BIC.
(Doc ID 3004703.1)
Last updated on MARCH 11, 2024
Applies to:
Oracle Banking Payments - Version 14.7.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.7.0.3.0 version, Implementation Support
Account BIC is not resolving properly for SDD transactions. system is deriving default branch BIC.
Branch code are:
XXX - Default Branch BIC
YYY- second branch BIC
Scenario 1)
ACTUAL BEHAVIOR
---------------
issue - Credit Bank Code is populated with XXX , instead of YYY.
EXPECTED BEHAVIOR
-----------------------
Credit Bank Code is populated as YYY.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upload pain008 - SDD with Creditor BIC code as YYY of creditor IBAN.
2. SDD transaction is generated in OBPM.
Scenario 2)
ACTUAL BEHAVIOR
---------------
Issue - Debtor Bank Code is populated with XXX, instead of YYY.
EXPECTED BEHAVIOR
-----------------------
Debtor Bank Code is populated as YYY
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upload incoming SDD collection with Debtor BIC code as YYY of Debtor IBAN.
2. SDD transaction is generated in OBPM.
Please note - in both cases System is resolving Default Branch BIC. instead of account BIC.
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 |