My Oracle Support Banner

PM: PE_RETRY Problem For Inbound Payments That Were WAITING_COV_MATCH. (Doc ID 2652556.1)

Last updated on APRIL 21, 2020

Applies to:

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

Symptoms

On : 14.3.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Unsuccessful in processing the inbound payments while retrying for those payments which were WAITING_COV_MATCH

EXPECTED BEHAVIOR
-----------------------
The inbound payment should be successful during retry for those payments which were WAITING_COV_MATCH

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Attempt an inbound payment to be moved to Inbound Messages STP Queue.
2. Observe that after being released, the payment is moved to Process Exception (PE) Queue due to Customer Payment Restrictions maintenance
3. Use Retry in PE queue for that transaction although the customer payment restriction is still in place
4. Observe that the payment is moved out of PE queue but the inbound Transaction Status = Exception and Exception Queue = Process Exception Queue
5. Notice that payment cannot be processed

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot process the inbound payment with retry option for those payments which were WAITING_COV_MATCH.

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.