Delivery Order details not correct - Investigation path

We found that the Delivery Order report (export code : NEW_LOADING_LIST) has incorrect information.

Loading list LDL21121900009

Wave Plan W21121900027

Point number 3 = Total number of Green Tote.

In the report showing = 36 Tote.

But when I checked in sub report details = 37 Tote.

Then I have checked again in Loading List details, there are 37 Tote for this order SO21121900128.

So I have queried the Loading List details from DB directly, So weird there are only 36 Tote.

This tote TG2108027386 was missing in Loading List details from DB.

After investigation, customer is correct to say that in the database table DOC_LOADING_DETAILS, this traceID TG2108027386 does not exists for load LDL21121900009.

However, on the front end UI as you can see from below, pic the traceID exists in the loading details.

Running the Delivery Order report details query in the backend database, I discovered that the allocationDetailsId for this record is as per below ie. 211219003953.

Further checking in the allocation detail tab for the order revealed that the actual picktoTraceId of this allocationDetailsId is indeed TG210027386.

However, if I was to query for this allocationDetailsId from the table DOC_LOADING_DETAILS, then you will see that the traceId captured there is different and instead it is captured as TG2108026616.

This is WRONG. It should have been captured as TG2108027386. BUT I am not able to investigate further as the logs are no longer available so I do not even know if user was using RF Standard Loading or RF Load by Tote/SKU function to perform this loading. Hence not able to trace at which point did it go wrong. So for this, we can only monitor when it happens the next time and client can quickly identify is the same cause, then we can look at the logs immediately.

To further explain why the report header shows 36 totes while the UI and report detail shows 37, it is because they both are retrieving the traceId info from different tables.

Report header retrieves the traceid from DOC_LOADING_DETAILS.traceId (which only has 36 traceIds) while report detail and UI Loading List retrieves the traceid from ACT_ALLOCATION_DETAILS (which correctly has 37 traceIds).