Check to See If Any Item is Locked Before Performing Reset Quantity Allocation
Many users perform an I/M Reset Quantity Allocation overnight as a deferred processing action. However, if an item is locked by a user (for example, should a user bring up the item file maintenance without exiting), then the reset allocation will not complete successfully and will cause the quantity allocation to be incorrect. This can have a profound impact on the 24x7 activities, such as in the case of Web sites where people may order online overnight.
What follows are two possible solutions.
(a) Educate users how to avoid locking. Teach users not to lock the item file in Item File Maintenance for extensive periods of time. Tell your users to exit Item File Maintenance quickly after changes are made. If users do not intend to change items, they should go to Item File Inquiry instead; or
(b) Make a programming change so the system will read every single item to make sure none of them are locked before committing to the reset process. If any one item is locked, then abort the reset routine and indicate so on the report. A possible event can be created so users can subscribe to such an event and know that the reset did not take place successfully due to record locking.
This change is done. The reset quantity allocation program will now check if any item is locked before proceeding to reset quantity allocation. This will avoid locking waiting in the loop during defer processing at night time. This feature is in the latest Elliott update.
The same change is also applied to Reset Quantity on Order.