Having upgraded from 12.5 to 15.2 we find that some count sheets stop with the status In Process
How do we change this to Roll Forward - line looks OK:
I do the Gen II - but this does not help
Solved
15.2 - why does count status stop at In Process
+12Best answer by Phil Seifert
Hi Bjørn,
This does not look right. You have a count that is still in process but the only count sheet has been completed and rolled forward. When all the sheets are rolled forward, the count should also have moved to roll forward completed.
I suggest you log a ticket for this as there is not a method to change the status from within the application other than completing the count. I presume you did do the check variances actions and there were either none or you accepted all the variances.
Important also to check the stock in the warehouse is no longer frozen which you should be able to do from the warehouse module.
+24Hi Bjørn,
This does not look right. You have a count that is still in process but the only count sheet has been completed and rolled forward. When all the sheets are rolled forward, the count should also have moved to roll forward completed.
I suggest you log a ticket for this as there is not a method to change the status from within the application other than completing the count. I presume you did do the check variances actions and there were either none or you accepted all the variances.
Important also to check the stock in the warehouse is no longer frozen which you should be able to do from the warehouse module.
I have a couple of counts that are in the same status and situation as well. Please post resolution here if support is able to help.
+24Hi Leann,
Is it really exactly the same? The count is in process but all the count sheets are roll forward completed?
I did resolve the specific data issue with Bjørn by updating the inv_count.count_status_id to 100 which is Roll Forward Completed but we did not go so far as to determine exactly WHY it happened.
Yes, that’s correct (screenshot below). I have had this happen previously and the only way I found to get around it was to delete the count afterwards, but I prefer not to as we no longer have the history at that point. It has not seemed to affect the inventory as far as I can tell.
+12We ended up changing the status manually in the database
UPDATE inv_count
SET count_stat_id = 100
where inv_count_id = ‘PC2202150001’ [change as necessary]
We did a count in the Astea Browser (back office only) in our UAT, and that worked as expected. So next we’ll do a count using mobile to see if we can recreate the error (and possibly determine if it is a user error or system error/setup issue)
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.