QuerySinglePayment Is Failing With Error “PM-TXP-002 - Transaction Does Not Exists”.
(Doc ID 2938008.1)
Last updated on MARCH 29, 2023
Applies to:
Oracle Banking Payments - Version 14.2.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.2.0.0.0 version, Production Support
QuerySinglePayment is failing with error “PM-TXP-002 - Transaction does not exists”.
We have come across an issue while querying payment operation(QuerySinglePayment) from SOAP/WSO2 to the FLEXCUBE PMSinglePaymentService Service and we believe it is a MOS issue.
Issue : We are not able to query payment transaction details as QuerySinglePayment is failing with error “PM-TXP-002 - Transaction does not exists”.
Issue Description : In the FLEXCUBE PMSinglePaymentService – QuerySinglePayment Operation, we are sending valid transaction reference no as input, but the operation is always failing with error ‘Transaction does not exists’. We tried with multiple transaction reference number, but the results were same.
Please find the attached following:
Request xml for Query Payment
Response xml from Query Payment
Debug logs
Payment spool :
PXPR_INB_TRNDATA
PXPR_OUB_TRNDATA
Reference MOS : SR 3-28772973314
This issue was already raised as part of above MOS.
ERROR
-----------------------
PM-TXP-002
STEPS
-----------------------
N/A
BUSINESS IMPACT
-----------------------
Not able query transaction through web service
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 |