Manufacturing

Issues Resolved

Works Order Processing

• [#18555] Updated tree views to help with intermediate database timeouts.
• [#17333] Fix to not allow works orders to be created when they contain operation without a resource or a subcontract. Display this as a warning to the user when setting up BOMs with operations too. This is because it can lend to further issues further down the line when booking in the works order.
• [#18815] Fix when using the ‘Update from BOM’ feature and it would appear to not to update all the lines. Report any errors back to the user. Issue here was a sub assembly line without a sub assembly works order [“Sequence contains no elements.”]
• [#18357]: Fixed issue where the issued quantity of a component line would be set incorrectly when adding time to an operation. This is if the component line was linked to the operation. This would only occur sometimes.
• [#18847] Fix to add an active lock when a works order is being created to avoid other users entering the works order when it has not fully been created.
• [#17333] Fix to improve the error handling when generating a works order from a sales order and when using the workflow options in WOP. Also no longer give the option to add an operation without a resource to the BOM.

Material Resource Planning

• [#18286] Fix for incorrect suggested PO quantities being raised when an item uses ‘Usual Order Quantities’.
• [#18879]: Added warehouse lookup to ‘Suggested Purchase Order’ tab.
• [#18820] Fix for the ‘Include suggestions from last MRP run’ filter not working correctly on the ‘Future Stock Movements’ screen.

Kitting

• [#18598] Fix when building a kit from a sales order line that is a batch type. [“Cannot set the value of field (.TraceAvailForDespatch) to x”]
• [#18598] Fix to correct display the required amount to be allocated for batch kit component lines when it has been part allocated. This can happen when allocating the lines, then increasing the it quantity and allocating again.