MT568 Tag 70F with Line Break Generates Parsing Error (Doc ID 2849108.1)

Last updated on NOVEMBER 25, 2022

Applies to:

Symptoms

MT568 Tag 70F generates format errors with line breaks.

Error in rti-server.log

[ERROR] 2022-01-17 11:42:46.559 [sourceEntityListener-4] aai -
com.oracle.ofss.sanctions.preProcess.rawMesssageTransformer.RawMessageTransfor
mer Exception occured while parsing Raw Message in method doTransform with
Message = Tag Name : (Qualifier)(Narrative) Invalid Format , Format should be
:4!c//8000z, Value : :ADTX//

 Expected Behavior : But as per swift standard usage rules it should support 

https://www2.swift.com/knowledgecentre/publications/us5md_20210723/?topic=con_ifld_G_0AH9uqEeqF57jgqTEwJQ_-1056831707fld.htm

Usage Rules
Extreme caution must be exercised when using this field with format option F because all characters can be in a continuous string, that is, there are 'no number of characters per line' limitations. The characters (Cr) and (Lf) may stand alone, that is, empty lines are allowed.

. , - ( ) / + ' = : ? @ _ # Cr Lf Space { ! " % & * ; < >

Ex : when the text is followed in next line then it thows format error

 :70F::ADTX//

I.Submission and, as the case may be, approval of the reports referred to in Art

Cause

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