My Oracle Support Banner

OBTF | Cross CIF Liability /facility Linkage And Utilisation Issue (Doc ID 3008501.1)

Last updated on MARCH 19, 2024

Applies to:

Oracle Banking Trade Finance - Version 14.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
When a user makes copy of an existing contract of CIF#A and changes CIF number on Main Tab, in Parties Tab against party Type APP & in parties limit tab under column Customer No to CIF#B without changing CIF#A in Liability Number column. System saved the entry with CIF#B and Liability and facility of CIF#A .

EXPECTED BEHAVIOR
-----------------------
System should validate incorrect liability no following incorrect facility against used CIF just like the validations available for parties tab and customer no in parties limit tab.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. AN OBTF contract is created.
2. After authorization, a copy of this contract is created , only customer no on main tab, applicant in parties tab and customer no in parties limit tab is changed, liability number is not changed.
3. System allows to save the entry for invalid liability number of this CIf and also posts utilization for this facility.  

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
References


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