My Oracle Support Banner

OBPM| Event Code And Amt Tag Should be Different For Original Transaction And Reversal Transaction In MX (Doc ID 3060013.1)

Last updated on DECEMBER 05, 2024

Applies to:

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

Symptoms

On : 14.7.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Event Code And Amt Tag Should be Different For Original Transaction And Reversal Transaction In MX

EXPECTED BEHAVIOR
-----------------------
Expectation is that system shall use event code like SRDR/SRCR and amount tag like RTN_STTLMT_AMT as used in other types of return. Please note we have this expectation as there is no reversal as such in MX.

The only difference in return type as RETURN and return type as REVERSE is that no Pacs004 would be send out in the latter.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Initiate reversal of a processed incoming MX/RTGS txn
2. System opens return screen PSDCBRT with return type as REVERSE
3. Reversal is successful
4. Original transaction status is RETURNED
5. System uses the same event code as of the original txn to reverse the payment ( SIDR, SICR)
6. System uses the same amount tag XFER_AMT as original txn
7. Our expectation is that system shall use event code like SRDR/SRCR and amount tag like RTN_STTLMT_AMT as used in other types of return. Please note we have this expectation as there is no reversal as such in MX.The only difference in return type as RETURN and return type as REVERSE is that no Pacs004 would be send out in the latter


 

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
References


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