My Oracle Support Banner

Inbound Cancellation- Tags 76,77A And 79 Format Issues Mtn96 Messages (Doc ID 2579598.1)

Last updated on AUGUST 29, 2019

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
Tag 79 for inbound Mtn96 should come with / in LIne1 .. and line 2-35 should have // for every line - hence should be in 2nd line and splitting the char for 50 char each line)

Tag 76 issue: /is not getting added if alone response code is provided

Tag 77A issues: Its coming in one line and it should be 20 lines with 35 character each line


EXPECTED BEHAVIOR
-----------------------
Tag 76: We should start and end with forward and backward slash of 35 Char inclusive then all lines will display as per standard swift format - Corrently no issue with this.

Tag77A: All char seems to be displaying but in a single line (not in different lines) under 'Exception' tab

Tag79: All char seems to be displaying but in a single line (not in different lines) under 'Exception' tab

STEPS
-----------------------
1. Load inbound cancellation response.


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.