My Oracle Support Banner

OBTR|Settlement Account Is Not Replaced With ISB GL In LIQD Event (Doc ID 3020633.1)

Last updated on MAY 09, 2024

Applies to:

Oracle Banking Treasury Management - Version 14.7.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.7.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Settlement account is not replaced with ISB GL in LIQD event

EXPECTED BEHAVIOR
-----------------------
ESN of SGEN should be before the ESN of LIQD in such cases so that Settlement account changes can be trigger.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a FX spot contract with booking, bought and sold value date as currency system date
2. As per the standard functionality, BOOK, LIQD, SGEN event will fire during contract booking itself and following shall happen:
a) Contract shall get liquidated. A part of LIQD event, system shall debt the customer account and credit ISB GL (replacing nostro settlement account with ISB GL maintained in IFSTREPM)
b) SGEN event shall fire. Payment message shall get generated and txn booked in OBPM
C) Accounting in OBPM shall debit ISB GL and credit NOSTRO settlement account of the receiver
3. We observe that system is not replacing NOSTRO settlement account of receiver with ISB GL in LIQD event of the FX contract due to which NOSTRO is getting credited twice (once in FX and second time in OBPM).
4. Our expectation is that system shall replace NOSTRO settlement account with ISB GL in LIQD event
5. Our expectation is also that ESN of SGEN should be before the ESN of LIQD in such cases
 

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.