ENTRIES HIT TO SUSPENSE IN BATCH UPLOAD THROUGH IT WHEN ACCOUNTS ARE DORMENT
(Doc ID 3017220.1)
Last updated on MAY 01, 2024
Applies to:
Oracle FLEXCUBE Universal Banking - Version 14.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
ENTRIES HIT TO SUSPENSE IN BATCH UPLOAD THROUGH IT WHEN ACCOUNTS ARE DORMENT
When we Try to Credit in Dormant accounts through IT Support Via Batch Upload, then ALL Dormant related entries going to Suspense instead of Post the Credit in Dormant accounts. As you Know that Credit is allow in Dormant accounts at front end option in Flex cube, than Why entries goes to Post in Suspense through IT Support Batch Upload functionality. Please check this issue and take fix accordingly. (Batch Upload Logs are attach with Dormant account Batch).
Error Code DE-UPLD-21 is populated in Batch Upload logs.
can we mark this error code as Override? Please confirm.
ERROR
-----------------------
DE-UPLD-21
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Perform Batch Upload
2. Credit the dormant account
3. Verify whether its successful
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot credit amount to dormant account
Changes
Bank expectation to handle the dormant account posting based on the type of transaction (debit or credit)
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 |
Changes |
Cause |
Solution |
References |