Checked the cause of the issue encountered by the user, the MTS is not displaying in the reverse logistics putaway, as per checking, the data is on the reverse logistics receiving table, but it is not on the reverse logistics putaway table, checked the queries used in the web application to confirm the findings, and as per checking, it confirmed that the MTS is not on the putaway table, suspected that the screen scrape for reverse receiving might be unsuccessful again and there might be temporary file lock again, as per checking, there is no file lock, meaning there is no unsuccessful process, executed the cron job again to process the screen scrape, on the receiving job, the MTS is successfully extracted but not successfully updated JDA table, as per checking of the cause, there is a message on the process that the transfer batch in JDA is not shipped status. Checked the batch/MTS data in the JDA, as per checking, the status on it is C meaning received status while on the MySQL, the jda_status on it is S meaning shipped status, suspected that this status has an impact in updating the table but still not sure thus this is needed to be clarified with JDA team. Advised Arvin on the findings and the clarification needed from the JDA team.