My Oracle Support Banner

Possible Bug In Wire Transaction BDF With Respect To Secondary Originator Internal Account Flag (Doc ID 2901720.1)

Last updated on APRIL 24, 2023

Applies to:

Oracle Financial Services Behavior Detection Platform - Version 8.0 and later
Information in this document applies to any platform.

Goal

OFSBD Version: 804

We have observed null in secondary originator internal account flag in wire transactions. It was observed NVL function is missing in WireTransaction_FrontOfficeTransaction.log for secondary originator whereas it is used for other parties. 

Condition for Secondary Beneficiary

NVL(SUBSTR(b.INTRL_SCND_BENEF_ACCT_FL,1,1),'N')

Condition for Secondary originator

SUBSTR(b.INTRL_SCND_ORIG_ACCT_FL,1,1)

 

This problem potentially impact behavior detection. Mantas scenarios (For example, SCNRO_IDs 114000060,114000073,114000074,114000082,114000083,116000089) make use of the condition INTRL_SCND_ORIG_ACCT_FL <> 'Y'
 

Solution

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