My Oracle Support Banner

OBPM| Future Dated C2B Initiated transactions Are Getting Stuck In FV Queue (Doc ID 3060387.1)

Last updated on DECEMBER 05, 2024

Applies to:

Oracle Banking Payments - Version 14.7.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.7.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Future dated C2B initiated transaction are getting stuck in FV queue 


EXPECTED BEHAVIOR
-----------------------
transactions must be cleared from warehouse queue

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Initiate a C2B (sdmc/sdsc) file upload
2. Requested execution date is in future
3. Consolidated batch ref number as well underlying txns are with status "Future Dated"
4. Branch date moves to next date
5. FV auto job runs
6. Batch and txns are still stuck in warehouse queue
7. Expectation is that such batch and underlying txns shall get released from warehouse queue

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, c2b transactions not processed

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.