PGDITONL Screen Transaction Creation Failing Via API/GW Request.
(Doc ID 2874180.1)
Last updated on JUNE 05, 2022
Applies to:
Oracle Banking Payments - Version 14.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.5.0.0.0 version, Production Support
PGDITONL screen transaction creation failing Via API/GW request.
Users are using "http://100.76.135.131:8705/PMWeb/PMClearingInService" as part of request building and it is failing with error "Value for field Bank Routing Number is not valid" , all the maintenance are in place
ERROR
-----------------------
"Value for field Bank Routing Number is not valid"
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Send a web service request for PMClearingInService
2. Verify if transaction is getting processed successfully
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot post PMClearingInService web service request
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 |
| References |