Issue with Incorrect Customer IDs Appearing in Count During Condition Screening

Hi CSO,



In our condition screening, the count should only include the Nivea customer ID. However, when we generate the count, other customer IDs appear, screenshot here.

Production:

In the Inventory Count raised, I saw that “NIVEA COUNT” was indeed a Zone. This zone does fall under Zone Group “STORAGE WAREHOUSE”. 

However, upon checking the other details in the Condition Screening for Cycle CountNo 0074658, they put a location as a parameter. Upon checking Location ID FFX-RTV, it falls under a different Zone and Zone Group. 

UAT:

Zone Group STORAGE WAREHOUSE exists. 

Zone NIVEA COUNT doesn’t exist. The Zone is added for proper recreation. 

During the customer’s UAT testing, they used ALASKA, which is not aligned with what was used in Production. 

Customers NIVEA and ALASKA both exist. 

Inventory Count:

As ZoneID NIVEA COUNT was just added in UAT, when used as a parameter in the Inventory Count, there will be no results. 

I tried generating an Inventory Count for Alaska, which is the one provided in the other screenshot by the superuser. From checking the Inventory Balance, I saw that the goods are in Zone SWH-A19 in Zone Group SWH. I used these as the parameters in the Condition Screening. 

In the MulSearch section, I put in ALASKA then chose Exact Query. 

When task was generated, the results still showed goods from other customers. 

I checked with the team, and it seems that only the upper portion of the Condition Screening works. This needs to be raised to Flux.

Hi Paul,

Upon initial checking of both Production and UAT environments, it seems that the data you used for the Inventory Count in Production doesn’t exist in UAT. Were you able to use the same data from Production? Upon checking, ZoneID NIVEA COUNT doesn’t exist.

Also, the initial screenshot provided is different from the one I saw in the Production environment. Please provide us the step-by-step procedure and details of what was done in Production so that it can be tested in UAT environment. During UAT testing, it is recommended to use the same data from Production so that we can see if it is a bug or not.

• Screenshot from first email: 

• Screenshot from Production environment investigation. 

Hi Hannah,

Yes, this is in production, and the IR has already been attached to the file.

INCIDENT REPORT

< [Customer name] Issue Description >

Affected Environment: TEST

Affected warehouse: GDEC-01

Screenshots of error messages:

Time when issue occurred: 2024-12-03 17:01:00

Affected module: Inventory Count

Detailed description of issue: During our generation of inventory count in the condition screening we would like to fill in zone group fm, zone group to, and customer ID. Which we input STORAGE WAREHOUSE, STORAGE WAREHOUSE, ALASKA respectively. When we generate count, order details show not just ALASKA customer ID to which we expected to only serve ALASKA since we input it in the customer ID condition screening.

Expected result: Order detailsof the cycle count number should only have SKUs/Products of the customer ID that has been put in the condition screening Customer Id tab.

First level investigation/troubleshooting taken: We tried filtering other condition such as location fm, location to, with the same customer ID (ALASKA) and order details still showed us SKUs from other customer ID.

Case replication in original warehouse:

< Details of replicated case >