"Move Confirmation" Does Not Complete if "Period" is Closed Accoring to System Time. This Window/and the backing database table/ does not provide meanse of specifiying document date.
Windows /PostgreSQL 8.4/9.1
To my understanding the two Physical Inventories are not a problem.
The Scrap Quantity is Adjusted at Destination Locator while the Difference is Adjusted at Source Locator thus not Summed up to Zero, for example if we send 415 units, Confirmed Quantity of 405, Scrap of 7 – the two Phy. Inventories are about to adjust Quantity 7 at Destination & Quantity 3 at Source Locators.
To give more emphasis on this facility, if taken by others too, I have an experience with supply chain companies where Transporter/Shipper is quested for the difference (under give allowance/loss factor 0-to-0.05%). In this case invoice is raised at the amount of loss/scrap to the transporter even if that the person is staff of the company.
How can this easily be implemented?
Thank you for the patch.
Ah yes - I see, what is modified is the difference (QtyCount-QtyBook) - and as QtyBook is zero there is no problem (there is a little risk in case somebody push the button on header that changes the qtybook).
So, what must we use to check period open?
(4) check (1) always and check (2) just if the inventory document is being created
Changed priority from Blocker to Minor - the problem has a known workaround, it has an explanation of why this happens.
About my previous question I think the right option must be to implement option (4).
Well the issue can be taken minor, because can be done with some workarounds. The option you choose makes sense but my recommendation is to have the inventory document created but not automatically completed. Because in some environments some historic records may be captured while the period aligned to current time closed.
Potential-Idea - create the movement and check the period against the Login @#Date@