Checked the data inserted in the 1.171 in zara_edi database, as this is where the data is inserted from the XML before it is created in the blue yonder, as per checking the sample transfer is not seen in the tblTransfer table in the database, discussed this with Sir Law and requested for a different transfer number as this is impossible, as the created transfer in the blue yonder should be located in MySQL, checked the data again in the MySQL with the new given transfer, as per checking, it existed in the database but the status is NULL, meaning it is not created in the blue yonder, checked with Sir Law if there is an error encountered in the execution of screen scrape, as per sir Law, there is no error encountered and the screen scrape is not displaying any encountered error, when they encounter this, they will re-run the transfer.php to create the transfer that is not created and allocate transfer that is not allocated. Advice to sir Law that the possible problem is the data is too big but the transfer.php execution time is not enough, thus other transfer is not created and allocated, and the reason when it is re-run again, all the transfer is created as the extracted data for the second execution is not that too big as some are created in the blue yonder already. Advice sir Law that I will apply some changes in the execution time and deploy to their side for testing tomorrow.