EOD could not start or aborts due to pending unauthorized contracts or maintenance
(Doc ID 2678187.1)
Last updated on JUNE 08, 2020
Applies to:Oracle FLEXCUBE Universal Banking - Version 7.0 and later
Information in this document applies to any platform.
This KM highlights the possible conditions that leads to mentioned situation.
1. Users left for the day without clearing their pending transactions or maintenance. Hence EOD couldn’t start.
2. EOD operator attempted to start the EOD, without noticing the pending transactions/maintenance.
3. After Mark EOTI, any upload type transactions/batch transactions remained in unauthorized state, so the abort in Mark EOFI stage.
4. To address any batch processing failure, need to mark problematic transactions or contracts to hold status.
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