My Oracle Support Banner

SW : DB_IN_TIME and DB_OUT_TIME Data Not Captured In SWTB_TXN_LOG (Doc ID 2798669.1)

Last updated on AUGUST 13, 2021

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
System is not capturing the DB_IN_TIME and DB_OUT_TIME data for ATM /POS transaction in table SWTB_TXN_LOG. It is critical for business to have this information to ascertain the performance of ATM/POS transactions getting processed in the Flexcube system. 

This is also mandated for Bank to report to other stakeholders exact processing time for each RRN in order to address complaints regarding transactions which failed at customer end (Code 91) with our Switch vendor and VISA/Mastercard about any delay in processing from either parties. Since it is expected from Flexcube to process each RRN transactions in less than 1-2 secs. This should be audited in the system per RRN transaction.

EXPECTED BEHAVIOR
-----------------------
System should log the transaction DB_IN_TIME and DB_OUT_TIME .

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Post a ATM Transaction.
2. Check the data in table swtb_txn_log for column DB_IN_TIME and DB_OUT_TIME

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.