Wrong stockout days calculations for the products with 0 values in period

Description

Pre-conditions:

  • Find a Facility with program that has at least 1 requisition period available to initiate and submit;

  • Make sure the Enable Stock on Hand to populate from stock cards option is checked for the program in Requisition Templates configuration;

  • <Optional> Change the home facility of the user and add roles to the Stock Management for programs if needed;

  • Log into the application as user that has access to make stock movements and creating requisition (e.g. Administrator);

Reproduction steps:

  1. Go to Stock on Hand Page and find any item which haven’t been updated for few months and its SOH = 0 (if there isn’t any make a physical inventory with proper date).

2. Make sure that the requisition template is calculated basing on stock.

3. Initiate the requisition for the next period (after the last product update, in this case June 2017) - the SOH is calculated as a difference between the last and first day between this period, delete this form.

4. Make Physical Inventory - make sure that you entered the 0 for tested product (I chose the 15.06.2022).

5. Initiate the requisition once again.

6. The Stockout days changed to 15 what is the difference between the last day of reporting period and the day from the last PI proceeded in this month).

Expected behavior

If the product stock was 0 for the whole month the SOD should be displayed as a difference between last and first days of reporting period regardless the inventory was made or not.

Environment

None

Attachments

3

is cloned by

Checklists

Activity

Artur Lebiedziński 
May 23, 2023 at 12:27 PM

Thanks for the clarification. In that case, I’m closing the ticket

Aleksandra Hinc 
May 23, 2023 at 12:24 PM

the scope is “Fix stockout days calculation bug that appeared after recent changes.” and this bug is relating to this. In the first comment of Szymon mentioned 2 bugs and one of them is , which is exactly the same as this one, it is cloned. I think that Szymon may not seen the bug that I’ve created, so he didn’t link it.

However in summary, this bug is fixed.

Artur Lebiedziński 
May 22, 2023 at 11:22 AM

Scope of the is different that this one. It should go to backlog instead

Aleksandra Hinc 
May 18, 2023 at 1:27 PM

I’m moving this ticket to “canceled” status, since it is included in the scope of this ticket:

Unresolved
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Priority

Time Assistant

Created April 19, 2023 at 11:18 AM
Updated May 23, 2023 at 12:27 PM