My Oracle Support Banner

Inbound Payment Cancellation- Response Code Not Captured And Remains Recall Requested (Doc ID 2570611.1)

Last updated on MAY 22, 2020

Applies to:

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

Symptoms

ACTUAL BEHAVIOR  
---------------
Recall status stays in recall requested state, response status code in exception tab and recall response code in recall messages tab is blank.

EXPECTED BEHAVIOR
-----------------------
Recall status should be in accepted state, response status code in exception tab and recall response code in recall messages tab should be ACPT .

STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Inject a MTn92 inbound cancellation for incoming processed message
2. Check PXSICLBR screen with message reference
3. Verify transaction status is transaction locked
4. Go to inbound cancellation request queue and accept the response and authorize
5. Go to PXDIVIEW screen and query the transaction ref#
6. Verify the recall status field and the recall response code in both exception/recall messages tab

Changes

Program changes done to set recall response code.

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
References


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