Dm_fusa Core Dumps When Stored Credentials are Sent to Paymentech but None Received
(Doc ID 2662750.1)
Last updated on JUNE 02, 2020
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.21.0 and laterInformation in this document applies to any platform.
Symptoms
When Paymentech does not return a stored credentials record (e.g. MT record or PMT record) even though one was sent by Billing And Revenue Management (BRM) in the request, this causes dm_fusa to core dump.
This happens when the transaction is rejected by Paymentech (i.e. never gets to the issuing bank), specifically when any of the following response codes are received from Paymentech in the response: 201, 204, 225, 233, 238, 239, 241, 245, 253, 262, 275, 279.
Because the answer_s/answer_b simulators appear to return the stored credentials record when one is submitted, this problem did not show up until Paymentech certification caused this condition.
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 |