My Oracle Support Banner

Incoming Target2 Payment Repeat Auth Limit Cycle After Placed In Sanction Next Working Date (Doc ID 2908780.1)

Last updated on NOVEMBER 11, 2022

Applies to:

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

Symptoms

On : 14.5.0.0.0 version, Production Support

ACTUAL BEHAVIOR
---------------
Incoming Target2 payment repeat Auth Limit cycle after placed in Sanction next working date

1. Incoming Target2 payment placed in Authorization limit queue.
2. User approves from AuthLimit1/AuthLimit2 next working date. Transaction placed in Sanction check queue.
3. User approves the payment from Sanction queue. Transaction is wrongly placed AGAIN in AuthLimit queue.


EXPECTED BEHAVIOR
-----------------------
Incoming Target2 payment should not repeat Auth Limit cycle after placed in Sanction next working date



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.