My Oracle Support Banner

TRACK_LIABILITY is N in cstb_param and ST-LMT-007 is Override, then system is tracking utilization under liability (Doc ID 2817210.1)

Last updated on NOVEMBER 04, 2021

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
TRACK_LIABILITY is N in cstb_param and ST-LMT-007 is maintained as Override, then system is tracking debit under liability
 

EXPECTED BEHAVIOR
-----------------------

Expectation is that system should not push anything for the Liab utilisation in these tables.

System should try to utilize from other linkages, if any. In our case there is no other linkage. 



SIMULATION STEPS
-----------------------
1) In cstb_param the parameter TRACK_LIABILITY is "N". Expectation here is that liability util will not be pushed into sttb_limit_utils table , sttb_req_master table and getb_utils table
2) STDCUSAC- Created a new CASA account with no limit attached
3) DEDTLRON - Booked one Debit transaction marked as available bal check required N - so that the CASA will go into debit and it will try to check for utils.
4) Since error code ST-LMT-007 is maintained as Override, system is allowing us to save the transaction. 
6) When we check sttb_limit_utils, sttb_req_master and getb_utils tables, found that system is tracking this debit under liability


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, system is ignoring completely parameter TRACK_LIABILITY maintained and updating liability utilisation, even when the TRACK_LIABILITY is turned OFF.

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


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