OBP 14.5.0.9.0 TARGET2MX: Special Character Not Replaced
(Doc ID 2997567.1)
Last updated on JANUARY 22, 2024
Applies to:
Oracle Banking Payments - Version 14.5.0.0.0 to 14.5.0.0.0 [Release 14]Information in this document applies to any platform.
Symptoms
On : 14.5.0.0.0 version, Production Support
OBP 14.5.0.9.0 TARGET2MX: Special Character not replaced
ERROR
-----------------------
special character not replace properly
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. We have maintained a special character in OBPM for the network TARGET2MX.
2. When a payment is inputted manually, on Enrich the character is replaced correctly with the one we have maintained.
3. When the payment is received from a service, it enters directly in Sanction Check and it does not Enrich the contract, thus the special character is replaced by a question mark '?'
Changes
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 |