Skip to main content
Question

Cleanup of Inventory not clearing all stock when 0 are on hand

  • November 23, 2023
  • 9 replies
  • 590 views

Forum|alt.badge.img+2

We are running the cleanup of inventory background job daily, we have this set to 0 days before current date so it will clear everything with an old activity date. The job is running each day as I can see that it is clearing out inventory, however I am left with lines that will not clear. These lines have 0 on hand quantity, 0 in transit, are not frozen and the last activity date is prior to the job being executed. 

 

The transaction history for these parts are also showing as old dates.

 

 

Is there anything else that would block these lines from clearing when the cleanup background job is executed?

 

Thanks

9 replies

Forum|alt.badge.img+4
  • Do Gooder (Customer)
  • November 23, 2023

In the settings of the scheduled tasks there is the option how often and for which sites you want to perform this task.

Furthermore at the bottom you can find the option to exclude some specific location types.

Make sure that the option with “No” is selected and the Days before current date is set to your wanted clearing date.

 

In our configuration we are clearing all 0 values from the stock everyday from yesterdays transactions.

 

 

Best regards,

Thomas


Forum|alt.badge.img+2
  • Author
  • November 23, 2023

Hi @Thomas Prügl 

 

The scheduled task is set to 0 days and ‘no’.

 

Many thanks


Forum|alt.badge.img+4
  • Do Gooder (Customer)
  • November 23, 2023

From the Documentation the following criteria should be applicable to the job:

Once you run the record you should be able to see that inventory part records with on-hand quantity of zero and a last transaction date prior to the number of days specified in the Days Before Current Date field, are removed from the Inventory Part In Stock, Receive Inventory Part and the Issue Inventory Part windows.

 

On the screenshot from above Ive seen that the frozen Checkbox = FALSE.

Also that the last transaction date of those records are quite old.

One try would be to start the job manually with an offset of 400 to see if there is a restriction of the maximum date of the past, the job is considering

 

 


Forum|alt.badge.img+2
  • Author
  • November 24, 2023

Hi @Thomas Prügl 

 

Unfortunately this has not cleared them either.

 

Thanks


Forum|alt.badge.img
  • Do Gooder (Customer)
  • November 28, 2024

Delete the task and re do it with the same parameters, had the same issue as above. I recreated the job and all lines were deleted as expected.


Forum|alt.badge.img+10
  • Hero (Customer)
  • February 3, 2025

Did you find a solution to this?  I am having the same issue.  Most locations clear, but some will not clear.


Forum|alt.badge.img+2
  • Author
  • February 12, 2025

Hi ​@TosohLBlum 

 

A few were stuck because they were showing on count reports as 0 and they had not been approved and cleared. For the rest, I raised a case with IFS and they ran a script through our system which removed the 0 lines as there was no way to do it myself.

 

Many thanks


Forum|alt.badge.img+13
  • Hero (Partner)
  • February 21, 2025

If the transactions occur on the same day you are running the Cleanup job, you can input a negative number in Days Before Current Date field (i.e. -1).  

 

 


Forum|alt.badge.img+7
  • Sidekick (Employee)
  • June 10, 2026

If you have rows in the inventory part in stock, where the qty on hand = 0, no transit quantity, the part is not frozen for counting and no availability control connected and the last activity date was more than a year ago and the nightly cleanup of inventory (or the cleanup of inventory run on demand) does not clean it up, here are other possible reasons:

  • Check if the part exists in Count per count report and the column called Confirmed is unchecked. This is one of the reasons why the Cleanup of inventory will not consider this record for cleanup. (it is held up because a count per count report for that part/site/location/lot batch etc has not been confirmed).

     
  • Now if you go ahead and confirm this line in the count per count report screen, it will update the inventory part in stock’s equivalent row with today’s last activity date. 
    If your Cleanup of inventory is set to remove 0 quantity rows from inventory part in stock with a default of 365 days, the recently updated record will not be eligible for cleanup until one year later. You can run the cleanup of inventory for the site on demand (from the navigator) and change the days from 365 to zero (which could remove the row which recently got updated in addition to other 0 quantity rows from inventory part in stock which are not existing in the count per count report. ).
    Or if you are only interested in purging the record which got updated when you confirmed the count per count report, you can go to the Count per inventory part screen, query for the problematic part, find the 0 quantity on hand row and hit the Delete option on the toolbar. This should remove the inventory part in stock record.