The resolution is to find the related transaction(s) causing the failure and attempt to fix them. If it is not fixed, then any attempt to XOG in any new transactions with the same groupId, none of the transactions will get processed by the PTF job.
In summary, if PAC_IMP_TRANSIMPORT_HEADER did not have any errors for the certain groupId, the issue would not have occurred.
Please contact the Support team to review the transactions as the DBA team will need to be provided queries to reset the import status on the Invalid Transactions table.
Steps to Resolve:
0. Backup table IMP_TRANSACTIONIMPORT
1. Review transactions:
select * IMP_TRANSACTIONIMPORT
where transdate between '<date1>' and '<date2>';
2. Review columns: importstatus and pac_imp_header_id.
3. Analyze and use one or more of the following queries. Review with Support team.
--Set transactions to New
update IMP_TRANSACTIONIMPORT
set importstatus = 'N',
pac_imp_header_id = 0
where pac_imp_header_id = ???
and transdate between '<date1>' and '<date2>';
commit;
--Set transactions to Hold
update IMP_TRANSACTIONIMPORT
set importstatus = 'H',
pac_imp_header_id = 0
where pac_imp_header_id = ???
and transdate between '<date1>' and '<date2>';
commit;
--Ignore rejected transactions
update IMP_TRANSACTIONIMPORT
set importstatus = 'H',
pac_imp_header_id = 0
where errorcode not in ('<ERROR LIST>') ;
commit;
4. . Run PTF job in specific date ranges, targeting specific financial transactions.