My Oracle Support Banner

Corporate Checker User (Authoriser) Is Not Able to View Transactions Initiated by Corporate Maker User (Initiator), and the Transaction Is Shown as "Expired" to the Maker (Doc ID 2590815.1)

Last updated on OCTOBER 30, 2019

Applies to:

Oracle Banking Digital Experience - Version 19.1.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Corporate checker user, i.e. the authorizer is not able to view Transactions initiated by corporate maker user, i.e. initiator. This is observed even when transaction is within grace period. When this happens, the transaction is shown as "Expired" to maker.

EXPECTED BEHAVIOR
-----------------------
When corporate initiator initiates a transaction, authorizer should be able to authorize it. Also for the initiator, the transaction should not be marked as "Expired"

STEPS TO REPRODUCE
-------------------------
1. As a corporate maker user, initiate one fund transfer.
2. As corporate checker, go to pending for authorization dashboard. Observe that the transaction is not listed in pending for authorization list.
3. When maker checks last 5 transaction, observes that the newly initiated transaction is marked as "Expired".

ENVIRONMENT
----------------

OBDX integrated with UBS/FCR.

 

 

Changes

 

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


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