My Oracle Support Banner

Determinant Resolver in Customized Code Returns "01" Instead of Correct Determinant Value "OBDX_BU" After Applying Patchset 18.3.5.0.0 (Doc ID 2702290.1)

Last updated on AUGUST 20, 2020

Applies to:

Oracle Banking Digital Experience - Version 18.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Bank has customized Domestic Payout extension. Requirement is to get beneficiary bank name for sending customized alert. Below code is being used:
  DeterminantResolver.getInstance().fetchDeterminantValue()

On 18.3.2.0.0, above code returns "OBDX_BU", which is as expected. However, after applying quarterly patch-sets till 18.3.5.0.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.



EXPECTED BEHAVIOR
-----------------------
Customized code that depends on DeterminantResolver.getInstance().fetchDeterminantValue(), and which was working fine in OBDx 18.3.2.0.0 should work in OBDx 18.3.5.0.0 as well.



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
References


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