OBLM: Sweep Execution Not Saved In Lms_tb_sweep_log Table During Two-way Sweep From Parent To Child
(Doc ID 2808359.1)
Last updated on NOVEMBER 08, 2021
Applies to:Oracle Banking Liquidity Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
OBLM: Sweep execution not saved in lms_tb_sweep_log table during two-way sweep from parent to child
We have created a structure - XXXXXXXXX with a/c as header with 0 balance and with two way sweep enabled. It has 3 child a/c's with the below mentioned priority.
xxxxxxxxxx -- AED 10,000 --- Priority 1
yyyyyyyyy -- AED - 15000 --- Priority 2 (negative balance)
zzzzzzzzzz -- AED 10,000 --- Priority 3
In the lms_tb_sweep table the entry for XXXXXXXX is missing. On analysing the debug, its found that, after the 1st sweep (xxxxxxxxxxx ), the parent balance of 10000 is moved to yyyyyyyyyyy because of the negative balance in child(zzzzzzzzzzzz)In this case the entry for movement between xxxxxxxxx to yyyyyyyyy should be present in the lms_tb_sweep_log table. Attaching the table details and logs for reference.
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