Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

MT396 Copy of original message field is wrapping F89A

SA-4202

Summary



In Smart Investigate, the MT396 Copy of Original Message field is wrapping F89A and causing a NACK with SWIFT. Any template that contains the 11R or 11S Original Message field, if you enter any field tag and value that goes over 35 characters in length, pega is wrapping the text and moving the extra characters to the next line. This causes an error when communicating with SWIFT.

Error Messages



From SWIFT: "BIC incorrectly formatted or invalid"


Steps to Reproduce



Create an MT95 or MT96 fast correspondence. In the original message field, enter the following message

:15A:
:20:0159775064444444
:21:NEW
:22A:NEWT
:22C:DEUT2L2679WFBI6W
:82A:WFBIUS6WFFX
:87A:DEUTGB2LXXX
:15B:
:30T:20141008
:30V:20141010
:36:1,2679
:32B:EUR1000000,
:56A:CLSBUS33
:57A:SOGEFRPPTPB
:33B:USD1267900,
:53A:SOGEFRPPTPB
:57A:CLSBUS33
:58A:DEUTGB2LXXX
:15C:
:72:/SOURCE/EBS PLATFORM TRADES TAKER
/USI/
:15E:
:89A:/1130111810500000000111111111111134
PNBPHKH0

When you click preview or submit, filed 89A is adjusted to :89A:/11301118105000000001111111111
11134
PNBPHKH0

This is causing the message to NACK in SWIFT.


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules.



Resolution



This issue was resolved through a detailed local-change. Please contact GCS and reference this SA article should you have need of this information. 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us