Currently, Regional IT is sending out the ESB error report to Regional eCommerce Team everday at around 2pm. Below is the email sample.
Our job is to email Regional IT to clear the ESB error report daily. There are several kinds of error in the ESB.
1. SKN not found: 0
It was mainly due to duplicate process previously which we changed the product SKN to 0 in PIM. Therefore the SKN will then update to 0 in Comestri and when a customer purchase that item it sends back the ESB to AS400, it will show the Error Reason with “SKN not found: 0” for that transaction.
So what we need to do is go to Comestri and search for the order (the order no. is appear on column F in the report, for China you can look at the column “SHIPID”), then use the Product description and search in PIM and find the correct SKNs and send back to Regional IT.
This is probably happening less right now since we have improved our duplicate process to avoid customer can purchase that item on the website when the SKN change to 0.
2. Order level transaction total mismatch
This error reason appears more frequently due to the rounding issue in China (T-mall) and Taiwan. Currently, if the TRANSTYPE is Returns, it cannot be marked off in the report. So we can only send the sales back to Regional IT to correct it and once it is corrected by Regional IT, it will be then marked off in the report on the next day.
For instance, we have 5 ESB errors that need to be corrected in the report.
So we can just simply copy those errors and reply to Regional IT in that daily ESB error email.
Then Regional IT will manually correct those errors and probably they will be marked off in tomorrow’s report.
3. Header Sequence number mismatch
This can be ignored.
For China T-mall orders, we may have different process but China IT is dealing with the vendor for some issue currently. This will be updated in the coming future.