Determinant Resolver in Customized Code Returns "01" Instead of Correct Determinant Value "OBDX_BU" After Applying Patchset 188.8.131.52.0
(Doc ID 2702290.1)
Last updated on AUGUST 20, 2020
Applies to:Oracle Banking Digital Experience - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Bank has customized Domestic Payout extension. Requirement is to get beneficiary bank name for sending customized alert. Below code is being used:
On 220.127.116.11.0, above code returns "OBDX_BU", which is as expected. However, after applying quarterly patch-sets till 18.104.22.168.0, above mentioned code is returning value "01". This results in the FinancialInstitutionBranchDirectoryKey having wrong values and when we pass this key in DomesticClearingCodeDirectory.read(), bank does not get the correct value for the beneficiary bank.
Customized code that depends on DeterminantResolver.getInstance().fetchDeterminantValue(), and which was working fine in OBDx 22.214.171.124.0 should work in OBDx 126.96.36.199.0 as well.
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