In Nav 5.0
I was working on a large item journal adjustment which involved an item with a few hundred serial numbers. While in the process of selecting the serial numbers using the "select entries" function, I had to open a second session of Nav to make a small adjustment to another item. Upon returning to my original adjustment and backing out of the serial # selection screen, all my work had been lost. I decided to delete the batch and start over.
Now when I try to use the select entries function again, all the serials I had previouly selected do not show up, even though I deleted the batch. The serials show unavailble because they have a "prospect" requested reservation against the earlier item journal lines. When I drill into the requested qty (1) in the serial table and go to "show document" it's blank. No open Item journals to support the serial #s that have the requested reservation.
I can still select the serial #'s 1 by 1, but they give an availability warning and stay in the serial table at -1 after the adjustment.
How do I clear the requested qty reservation against this non-existent item journal entry?
Thanks in Advance,
Scott
*This post is locked for comments
I have the same question (0)Hello Scott,
Thank you for posting on the Microsoft Dynamics Community Forum. I am currently looking into the issue to see if I can identify whether an issue has been previously reported related to this scenario and if a correction exists. We don't officially support Version 5.00 any longer, so there would have to be an already published change to address this. Otherwise, it would require upgrade to NAV 2009 SP1/R2.
My first inclination is that this is an issue where the deletion of Item Journal lines results in Prospect Lines remaining that should have been removed from the Reservation Entry Table. Just to make sure that this is the case, please confirm that there is not a filter set in your Item Journal where the Lines are not showing but are actually still residing in the Item Journal Lines (Table 83).
I will update this posting as I gather any further information. For now, it may be required to test a workaround process in a backup copy of the database. You would run Table 337 and delete the Prospect Records that are no longer valid. However, I always recommend testing such a process to insure that no negative ramifications are generated from such as step.
I will update the post as further research is completed.
Best Regards
Tom