B - Production Support » PayNet RPPBO Support

Hi All,

Please refer below for the finding and resolution. New package had been uploaded to SIT server, pending user to retest.

Finding:
- All affected data happened from update dispute status from status code 7(Initiate Close) to status code 5(Closed), which required a checker maker process.
- Found database table RPP_DISPUTE_MANAGEMENT status code still in status code 7 with pending status, but table RPP_DISPUTE_HISTORY recorded activity had been successfully changed from status 7 to 5.
- Found transaction had been approved by the checker in the audit_log table.
- Found no further update by user for the affected dispute data after approved by checker, but status code still remains 7 and pending status.
- Found batch job SLA Maintenance running at 5:20pm approaching the timestamp checker approved the transaction.
- Suspect batch job override the approved object, but batch job log didn't log the updated dispute id into log file.

Resolution:
- To update the batch job running at night time like 11:30pm or 1:00am.
- Adding more logger in batch job and back office to further investigate/prove the dispute object isn't overridden by the batch job.
- To fixed the duplicate audit log category id used in difference activity (Issue found in audit_log data in database)
- execute sql script to updating the existing affected records in database.

Issue closed in SCP.