12.2 Submit Offline Transactions Wkr Gives Errors "Duplicate transaction. Transaction has previously completed successfully" (Doc ID 2484102.1)

Last updated on JUNE 13, 2024

Applies to:

Symptoms

Submit Offline Transactions Wkr Failed, however, funds were actually received for the transaction. Getting the following error message.

ERROR

The transaction for TangibleId : ONT1234567 may have failed.Please look at the debug log for more details.

The Stack Trace is -
oracle.apps.iby.exception.CreditCardProcessorException: Duplicate transaction. Transaction has previously completed successfully.
at oracle.apps.iby.payment.CreditCardProcessor.processTrxn(CreditCardProcessor.java:988)
at oracle.apps.iby.payment.CreditCardProcessor.captureCC(CreditCardProcessor.java:2441)
at oracle.apps.iby.payment.CreditCardProcessor.perform(CreditCardProcessor.java:147)
at oracle.apps.iby.payment.OnlineCreditCardPayment.captureZero(OnlineCreditCardPayment.java:636)
at oracle.apps.iby.payment.OnlineCreditCardPayment.capture(OnlineCreditCardPayment.java:651)
at oracle.apps.iby.scheduler.SchedCoreCC.schedPmt(SchedCoreCC.java:343)
at oracle.apps.iby.scheduler.Scheduler.doProcess(Scheduler.java:326)
at oracle.apps.iby.scheduler.Scheduler.init(Scheduler.java:425)
at oracle.apps.iby.scheduler.SubmitOfflineTransactionsWkr.runProgram(SubmitOfflineTransactionsWkr.java:68)
at oracle.apps.fnd.cp.request.Run.main(Run.java:156)

OTHER SYMPTOMS

SOT first gives error "Communication error. The payment system, the processor, or iPayment electronic commerce servlet is not available/accessible.".

Failed ORAPMTCAPTURE record(s) are in STATUS=1, one ORAPMTCAPTURE record has STATUS=0 (success).

Then Next run of SOT these transactions fail with "Duplicate transaction. Transaction has previously completed successfully."

Query on the IBY_TRXN_SUMMARIES_ALL for problem transaction(s) SQL>select * from iby_trxn_summaries_all where tangibleid='&tangibleid';

Query results show the first ORAPMTCAPTURES fail with STATUS=1 , the SETTLEDATE is populated only for these failures, the PAYMENT_CHANNEL_CODE is NOT populated (blank) and success records have values , the CALL_APP_SERVICE_REQ_CODE has a value such as AR_85150 ONLY for these failed records and not populated for the Successful ORAPMTCAPTURE records.

STATUS UPDATEDATE TRXNTYPEID ERRORLOCATION BEPCODE BEPMESSAGE BATCHID SETTLEDATE
0 11/16/2018 23:45:55 8 0 0 Approved
0 11/15/2018 13:37:09 2 0 0 Approved
1 11/15/2018 23:47:07 8 10/15/2018 00:00:00 

Cause

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