Performance Issue || In The Payment Status Inquiry Screen, The User Is Unable To Fetch The List Of Transactions If Using Account Number Filter Only. (Doc ID 2924008.1)

Last updated on JANUARY 31, 2023

Applies to:

Symptoms

ACTUAL BEHAVIOR

Performance issue || In the payment status inquiry screen, the user is unable to fetch the list of transactions if using the account number filter only.

The below service got failed with status 503 after 12 mins
https://XXX.XX:XXXX/digx-payments/payment/v1/payments/outwardRemittances?accountId=6099ABDDC782E455D92C4A6153C3956D33CE65EB7FD3D67F5D9F3992BCF850B159&accountType=CSA&locale=en

EXPECTED BEHAVIOR

In the payment status inquiry screen, the user is able to fetch the list using the account number filter only.

STEPS

The issue can be reproduced at will with the following steps:
1. log in to an application as a corporate maker user
2. Payment status inquiry screen -> search the transaction only with the account number -> Above mentioned error observed


BUSINESS IMPACT

The issue has the following business impact:
Due to this issue, users cannot search for the transaction with the account number only on the PSI screen.

Changes

 
No changes done to hardware/product or environment cause this issue.

Cause

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