My Oracle Support Banner

Charge Claim- MT199 Field 79 Is Referencing Incorrect Original Transaction Reference Details (Doc ID 2693460.1)

Last updated on JULY 25, 2020

Applies to:

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

Symptoms

On : 14.3.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
The Narrative field of MT199 is not correctly populated for 3rd and subsequent duplicate charge claim request.

EXPECTED BEHAVIOR
-----------------------
The field 79 on the 3rd and any subsequent MT199 should refer to field 20 of the first MT191, when Charge Claim was paid.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a MT103 with OUR as charge code.
2. Inject a MT191 with amount above the CAPAMOUNT against the MT103.
3. Once the MT199 and MT202 is triggered against the MT191, Inject another MT191 for the same MT103.
4. Once the MT199 is triggered against the second MT191, Inject another MT191 for the same MT103.
5. Verify the field 79 of the 3rd MT199

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the MT199, narrative is not correctly populated with Reference no.

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.