OMS Order status sent to WMS but haven't created in WMS

Creation date: 22/03/2022 07:50    Updated: 22/03/2022 07:50   #omsorder #ordernotcreated
Question:

Dear CSO,

There are some list of transaction id that OMS Order status sent to WMS but haven't been created in WMS, attach with the request time also:

  • PRD_SO_637425 - 2022-03-07 11:53:48
  • PRD_SO_637428 - 2022-03-07 11:57:48
  • PRD_SO_637440 - 2022-03-07 12:06:48
  • PRD_SO_637446 - 2022-03-07 12:07:48
  • PRD_SO_637452 - 2022-03-07 12:12:48
  • PRD_SO_637449 - 2022-03-07 12:12:48
  • PRD_SO_637455 - 2022-03-07 12:16:48
  • PRD_SO_637458 - 2022-03-07 12:16:48
  • PRD_SO_637464 - 2022-03-07 12:20:48
  • PRD_SO_637467 - 2022-03-07 12:23:48
  • PRD_SO_637470 - 2022-03-07 12:26:48
  • PRD_SO_637476 - 2022-03-07 12:40:48
  • PRD_SO_637482 - 2022-03-07 12:49:48
  • PRD_SO_637485 - 2022-03-07 12:50:48
  • PRD_SO_637488 - 2022-03-07 12:53:48
  • PRD_SO_637491 - 2022-03-07 12:55:48
  • PRD_SO_637500 - 2022-03-07 13:06:48
  • PRD_SO_637461 - 2022-03-07 12:17:48
  • PRD_SO_637473 - 2022-03-07 12:27:48
  • TOKOPEDIA --> INV20220307MPL2109359468 - 2022-03-07 13:01:48 
  • From this OMS order, we can see that the order hasn't been created in WMS but it is already 7 hours, please fast fix the issues, because Tokopedia order will be cancelled automatically when we not confirm the order in 18 / 24 hours, and there is the penalty when the order rejected.

Answer:

Investigation:

We have change a setting in OMS to push the order to WMS if the backend processing is unexpectedly hang or timer has stopped.

Currently in PROD, the UPLOAD ORDER module have the capacity to hold up to 20 orders before initializing the uploading process. That is why the 20 orders so happened did not get send.


We changed this to 1 order the same as in the TEST.


According to product team:


Q1: Batch set to 20, what will happen if there is only 1 order left?

A: If batch upload set to 20, it will upload only 1 order as well, do not wait until 20 orders.


Q2: Is it wait for another 19 orders OR still able to triggered to datahub within x mins?

A: If batch upload set to 20, it will trigger the request message to datahub even only 1 order, business as usual, it will not wait for it to reach 20 orders.



The problem below is with the “HOLD-state”, we changed it as we mentioned, it may looks into this setting for re-trigger of the request message. Therefore we change it to check if that is the case.

Files