Format Errors In Tag 41D For MT700 And MT710 Payments
(Doc ID 2921086.1)
Last updated on JANUARY 20, 2023
Applies to:
Oracle Financial Services Transaction Filtering - Version 8.0.8 and laterInformation in this document applies to any platform.
Symptoms
Steps to reproduce :
Step 1 : Import the sql of MT700 and MT710
Step 2 : Post the message
Step 3 : Check if alert is created.
User encountered issue with MT700 and MT710 payments in tag 41D in both cases
Error Encountered :
MT700 :
Parsed Tag Name : 41D
[ERROR] 2022-12-21 15:24:18.782 [sourceEntityListener-5] aai - com.oracle.ofss.sanctions.preProcess.rawMesssageTransformer.RawMessageTransformer Exception occured while parsing Raw Message in method doTransform with Message = Tag Name : Code Invalid Format , Format should be 14x, Value : is not matching
com.oracle.ofss.parser.swift.exceptions.SwiftServiceException: Tag Name : Code Invalid Format , Format should be 14x, Value : is not matching
MT710 :
[ERROR] 2022-12-21 15:23:20.264 [sourceEntityListener-3] aai - com.oracle.ofss.sanctions.preProcess.rawMesssageTransformer.RawMessageTransformer Exception occured while parsing Raw Message in method doTransform with Message = Tag Name : Name and Address Invalid Format , Format should be 4*35x, Value : x
x
x
x
BY ACCEPTANCE is not matching
com.oracle.ofss.parser.swift.exceptions.SwiftServiceException: Tag Name : Name and Address Invalid Format , Format should be 4*35x, Value : x
x
x
x
BY ACCEPTANCE is not matching
Changes
NA
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 |