Yantra 4.0 SP3 : executeCollection : YFSCollectionCreditCardUE : Charge Transactions in status Error : need to re-process

Resolving The Problem

Referring to Yantra 4.0 SP3 Java docs :

executeCollection API calls a userExit "com.yantra.yfs.japi.ue.YFSCollectionCreditCardUE"
This UE can also place a request to try again later if the interface to the payment system (CyberSource, PaymentTech, or an accounts receivable database) is inoperable.

The user exit has three options for processing a request:

1. Authorize/charge online and return details related to the interaction (default).
2. Request for retry later, which means the request remains as is and the request is resent to the payment interface through this user exit on the next run.
3. Request for asynchronous processing which means that Platform never contacts the payment system for this order. The payment interface (custom extension) is expected to update details corresponding to payment through the recordCollection() API. This is typically the case when interfaces to the payment system are run in batch mode.

Customer will need to implement Option 2 appropriately so that similar situation is handled without any intervention in future.

====
Temp fix in 4.0 SP3, refer to Case 20987:
Following query gives distribution of Error transactions for charge_type and across days.

select substr(charge_transaction_key,1,8) CHG_DATE, charge_type, status, status_reason, modifyprogid, count('1')
from yfs_charge_transaction
where charge_transaction_key like '2003&MON_MM%' -- To activate index
and status = 'ERROR'
group by substr(charge_transaction_key,1,8), charge_type, status, status_reason, modifyprogid