My Oracle Support Banner

CL_AUTO-AUTORIZATION ID CLDPYMNT (Doc ID 2651538.1)

Last updated on MARCH 26, 2020

Applies to:

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

Symptoms

On : 14.1.0.0.0 version, Implementation Support,SET in UAT Environments

ACTUAL BEHAVIOR
---------------
While performing CL payment under CLDPYMNT screen with Auto-AUTH user, the system is displaying the record as saved and auth, but the authorize id is not getting updated in the system and still the system is showing the record as unauthorized

EXPECTED BEHAVIOR
-----------------------
While performing CL payment under CLDPYMNT screen with Auto-AUTH user, when the system is displaying the record as saved and authorized, both checker id and maker id should get auto authorized with the same user and the system should not show the record as unauthorized

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.launch SMDFNDSC Screen.Check the auto auth checkbox for the function id CLDPYMNT
2.launch SMDUSRDF Screen.Check the auto authorisation required checkbox for the user
3.Login with that user
4.launch CLDACCNT Screen.Create an account 
5.launch CLDPYMNT Screen.Do payment with the auto auth user and validate payment authorization status, the system is not auto authorizing with the same user and the system is showing the record as unauthorized in the system.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot able to auto auth the CL account Successfully.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.