Manufacturing

Issues Resolved

Works Order Processing

• Fix to also update the works order object when updating an operation via the web API. Issue where project transactions weren’t updating correctly when operations were updated via the web API
• Fix for the stages drop down on the works order header was not showing all the stages set on the operations on the works order. The drop down was also not refreshing when an operation was completed.
• If no area has been set on the BOM operation line, then when creating a works order, we now check the operation on the operation register as well to see if there is an area set there. Also, when editing an existing BOM operation on the BOM, and no area has been set, we default the area to what is set in the operation register.
• Fix when booking batch finished items to correctly update the ‘Next Available Number’ on the stock item when the ‘Automatic Number Generation’ is either ‘Generate Using Sequence’ or ‘Generate Using Order Number And Sequence’
• Fix to default the starting number when ‘Auto Generating Serial Numbers’ when booking a finished item to the ‘Next Available Number’ on the stock item
• Fixed the SiconWOWIPView for calculating the correct cost of sub contract lines
• Fix when generating a works order from a sales order using the works order workflow option. To correctly split the works order up when using eco batch sizes. Issue where it would always suggest a works order quantity of 0
• Fix when creating an empty works order and adding a BOM finished item to correctly consolidate the lines if the user selects to consolidate them
• Fix to reload the ‘Manufacturing Attributes’ tab after a sales order line has been saved.
• Fix to store dates in the spare text fields on a works order without the time stamp
• Fix when resetting the works order number to make sure the number set is the next number that gets used. Issue where the number was set to 100 as an example however the next number that would have been used when a works order was created would have been 101.
• Fix for allow the ‘Materials’ tab on the works order settings screen to be scrollable

Material Resource Planning 

• Fix when using the ‘Calculate’ button on a sales order and calculating a built item that contains a phantom item. Now explode the phantom and calculate all the lines that are part of it [“Object Reference Error”]
• Fix when generating suggested kits for sales order lines to get the correct preallocated quantity. Issue where a kit would be preallocated to a sales order line and then deleted and MRP would not generate the suggestion again
• Fix when creating suggested kits from MRP and once they are created these lines wouldn’t be removed from the ‘Suggested Kits’ tab. This could then mean they get created multiple times
• Fix when generating warnings for purchase orders, to run through all items. Issue where some purchase order lines were being displayed as a warning but others on the PO were now

Kitting

• Fix when using the ‘Build Kit’ screen to build a kit without a template [“Cannot update field (ItemDbKey) with a null value, as it is marked as not accepting ‘Null’ values”]

Change in Functionality

Works Order Processing

• Updated the ‘Send to Excel’ form from the ‘Process Works Order’ screen to match all the columns that are on the ‘Process Works Order’ screen
  • As columns have been added, not all columns were previously captured when exporting to Excel.