My Oracle Support Banner

58 D of Incoming MT 202 is Not Converted to 58 A in Outgoing MT 202 (Doc ID 2702589.1)

Last updated on AUGUST 21, 2020

Applies to:

Oracle FLEXCUBE Universal Banking - Version 12.0.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.0.3 version, Production Support-SET

ACTUAL BEHAVIOR
---------------
The 58D tag details from Incoming message are not converted into 58 A tag in the Outgoing Message

EXPECTED BEHAVIOR
-----------------------
System is expected to populate 58 D tag in the Outgoing MT 202 message from the values present in 58 A tag

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Maintain Bic codes in D to A converter screen
2. Check for tag 58 A in the Outgoing Message generated by the flexcube in MT 202

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot have MT 202 outgoing message generated with the BIC code as per the D to A conversion maintenance

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.