MT199 71F Field Not Populated Correctly When Charges Are SHA/beneficiary
(Doc ID 2899664.1)
Last updated on OCTOBER 10, 2022
Applies to:
Oracle Banking Payments - Version 14.5.0.0.0 to 14.5.0.0.0 [Release 14]Information in this document applies to any platform.
Symptoms
On : 14.5.0.0.0 version, Production Support
ACTUAL BEHAVIOR
---------------
MT199 71F Field not populated correctly when charges are SHA/beneficiary
Please be informed that we are having an issue with the generation of MT199 when the charge account is different than the creditor account and charges are SHA/beneficiary, MT199 should not show charge details under 79 field and the amount should be full amount, for example as below.
:79://2206241917+0300
//ACCC
//EUEBLT22XXX
//EUR32129,94 (Full amount should be populated)
//:71F:EUR0,00
//:71F:EUR0,00
//:71F:EUR20, (Charge should not be populated)
EXPECTED BEHAVIOR
-----------------------
expected for MT199 should not show charge details under 79 field and the amount should be full amount,
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.We receive an incoming MT103 where the creditor account is different from the charge account and the charges are of type SHA or beneficiary.
2.We release the transaction from Non-Stop queue.
3.We approve the transaction from Sanction check queue.
4.The generated MT199 has the field 71F with the charges taken from the bank, and the transfer amount is transfer amount - charges, which should not be the case since creditor account is different from the charge account.
Changes
provided fix for charge amount when charge account is different than the creditor account
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 |