PQSNSTPQ: For Incoming Txn In NSTP Q If We Modify And Authorize, The Txn Is Still In Unauth Status I (Doc ID 2917953.1)

Last updated on DECEMBER 26, 2022

Applies to:

Symptoms

On : 14.5.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------

PQSNSTPQ: For incoming txn in NSTP Q if we modify and authorize, the transaction is still in unauth status in the NSTP Q. But the txn gets posted successfully and accounting is success in the main screen.



EXPECTED BEHAVIOR
-----------------------
System should mark the record as authorized and move out of the NSTP Q once record is successfully authorized.

STEPS

---------

1) Upload a transaction into NSTP Q for inward swift

2) In the screen PQSNSTPQ use maker (non-autoauth) to modify some values in ulti beneficiary and save the record

3) Log in with authorizer and authorize teh modification in the PQSNSTPQ screen

4) System display the message successfully authorized. but the record is still un auth status.

But as we check the contract is getting released and accounting posted successfully.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, for incoming txn in NSTP Q if we modify and authorize, the txn is still in unauth status in the NSTP Q

Changes

 Fixed code to query normally without taking lock on entity.

Cause

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