My Oracle Support Banner

Swift Incoming Message Is Failed And Moved To Repair Due To Character Validation Failed (Doc ID 2678993.1)

Last updated on JUNE 10, 2020

Applies to:

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

Symptoms

On : 14.3.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------

Swift Incoming message is failed and moved to repair queue due to character validation failure.
The message has tag: 77T (Envelope Contents) and contains only allowed SWIFT characters. But still it resulted in failure.
Transaction moved to repair queue with below error.
"PM-MS-10-CHARACTER VALIDATION FAILED"

Actual Result:
Message is moved to repair queue due to "character validation failure".

 

EXPECTED BEHAVIOR
-----------------------
Message should not be moved to repair queue when the table: maintained with the disallowed characters are NOT in the message

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Process SWIFT Incoming MT103 REMIT (Should Include Tag: 77T in MT103 msg)
2. Check if it is processed successfully in PXSIVIEW.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot process the message

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


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