I discussed with Arvin the findings and checked as well the data using the query with him, as per checking, found out that there are fields that are NULL in the extracted data of each query, when checked where it is coming from, it is from the product master list table, checked the table, as per checking, the product master list table is empty. Checked the cron logs and the created CSV, as well as the query and process on how the master file is updated, as per checking, the script is extracting from JDA tables (INVMST, INVUPC, INVDPT, TBLCOL, PRCPLN1), export it into CSV file, then truncate the master list table in MySQL then import the data from the CSV file. We re-executed the script but encountered an error, the error indicating that the data inserted is too long for the description field, checked the data in CSV and found out that 3 SKUs have descriptions that consist of letters and too long characters causing them to exceed the set limit for the description fields in MySQL table, checked the data in JDA using a query, as per checking, it has no character on it. I checked with sir Rey if the said SKUs description has no spaces that might not be seen in the query result, as per sir Rey, the description in JDA has no problem though he edited it to fix the problem on our side. We executed the query again to check if it is now OK, but the same problem is encountered. Reported it to sir Rey again, this will be checked again tomorrow. This problem is what we suspected for now as this is the only problem we see on the data. Updating the table manually is not advisable as the updating of the master list table has a schedule, the updating of the textfile is not recommended as well as the exporting and importing of the textfile is on one process only, also the same error will be encountered when the updating of master list executed again. The data should be fixed, the checking and fixing will continue tomorrow.