Discussed with Arvin the findings in checking for the cause of the error in the barcode in the label, the category with the previously created TL have an upper case value for the category but the recently created TL have a camel case, advised to asked Ms. Sally or user from warehouse if the category is manually inputted, as per Ms. Sally, it is not manually inputted. Included Ms. Sally on the google meet to discuss further the process of it why does the category value changed from the upper case into camel case, explained to Ms. Sally the findings on the checking for the cause of the error, as per Ms. Sally, the data came from the EDI file uploaded using Pentaho in JDA, then the web portal will extract the data from JDA, for now, requested files uploaded from Ms. Sally for checking of the data inside the file. Ms. Sally is excused in the call, I and Arvin discussed the checking to do and the solution on it included Pentaho team and Sir Rey in the meeting for checking of the process in Pentaho as it is used in uploading the file, as discussed, the Pentaho is inserting the data in JDA staging as is, thus discussed that the updating of the data in the database now can be done for the user to continue to process the TL and we discussed as well the solution on this, as per checking of the file with the team, found out that the changes are on the file, the sent file came from the principal or merchandising, the previously sent file has upper case category but the recently sent file has camel case thus not having a problem on the label. Discussed with the team the solution on this, as discussed, all of the data inserted in JDA by the Pentaho from the files will be set into the upper case this will eliminate the possible repetition of this error, but before the changes are applied confirmation from Payless team should be requested first as this will make changes on the Pentaho. Arvin and I remain on the call and discuss if the updating of the web portal database(MySQL) will