Checked the cause of why the scanned qty for MENS TL did not synch with JDA, checked the logs and screen scrape, but there are no pending processes and the logs cannot tell if there is unsuccessful execution or if the processed did not finish successfully. Checked on how the portal is synching the data to JDA, as per checking of the query in the screen scrape, the data is extracted from MySQL letdown list and details table, once extracted all the TL with close status and with jda_status equals to N, it is updated into JDA, once JDA is updated, the screen scrape will update the MySQL letdown list table, the jda_status value will be Y and the is_synched value updated from 0 into 1. As per checking the data, there are SKUs in the letdown details table that are not synched to JDA, as the is_synched field is not updated into 1. suspected that the execution of the screen scrape did not finish thus resulting in MENS scanned qty did not synch to JDA. There is no telling if the exact reason why some of the scanned qty did not synch to JDA. Discussed with Arvin the findings, there is no option on the portal for the screen scrape to be executed again, and even if the cron is manually executed to the server the cron will not extract any data, as the jda_status is updated to Y and the is_synched is updated to 1 in the letdown list table, we are not sure at the moment if updating this in MySQL side will not return more problems, the solution, for now, is to manually fix this. This has been fixed by sir Rey on the JDA side. as this TL will be picked tomorrow.