Currently, If an allocation of a Batch/Serial numbered item gets &stuck&, the Balance Ledgers Routine will not fix the problem. The problem can only be fixed manually through SQL by deleting the corresponding TraceableAllocationBalance/AllocationBalance entries and adjusting the allocated quantity in the TraceableBinItem/TraceableItem Tables (SOPAllocationLine entry may also need to be removed) then running Balance Ledgers which will handle the rest. If manufacturing is involved, there are a host MFG tables that need to be adjusted too. This takes up a lot of resource time to resolve so would be great if this could be sorted using the Routine that is designed to fix these kinds of things. Alternatively, rolling back the transaction fully if it encounters a problem would stop the allocation from getting &stuck& in the first place.
Guest
