Question:
Affected Environment:
PROD
Affected warehouse:
WH-HQ
Screenshots of error messages:


Time when issue occurred:
18/8/2022 11:03AM
Affected module:
WAVE
PLAN RULE
(ATOMY- EC)
Detailed description of issue:
1. EC
wave creation (customer: ATOMY) took a longer time than usual.
As per screenshot 1
11.29AM- only 6 wave created (start time is 11:03AM)
As per screenshot 2
Total orders: 1288
11.29AM- still balance 1141 orders not yet added to wave.
By waiting around 30 min, only 100++ orders added to wave
Answer:
Investigation:
Raise a customer ticket: 20220913184330000431
Cannot find any co-relation between the slow
performance and the SP.
In this case we would like to suggest the following because
we could only guess what could happened that can cause the performance to be
slow.
First of all, you may need to advice the operation on the
following:
- Wave creation can only
be run one at a time. There should not have concurrent process for wave
creation. User needs to wait for the wave creation process to complete
first before starting another one.
- During wave creation
process, all the orders without wave no. (*) should not have any changes
e.g. cancel soft-allocation or allocation or triggering soft-allocation
and allocation that can effect on the order selection during wave
creation.
- During wave creation
process, all the orders with wave no. should not have changes that can
remove the wave no. such as cancel soft-allocation and trigger
soft-allocation again for it to be selected for new wave. This can affect
the order selection during wave creation.
Investigation:
The performance has improved and customer said to closed the ticket.
Investigation:
Flux changed the SP - SPCUS_CreateWave to improve performance.
Investigation:
According to DBA, this should not due to the amount of orders but rather indexing and probably deadlock. Need to monitor further. Currently DBA put in 2 -3 indexes to improve the SP.