Manufacturing

Issues Resolved

Works Order Processing

• The generate works order from sales order screen was not showing stock unit quantity. It was incorrectly showing the line quantity, which is in that particular unit of measure.
• Fix to not allow the projects control to be enabled when a works order has been part booked and it is not associated to a sales order.
• Fix when amending the dates of a works order where there are no operations but there are sub assemblies to allow the user to update the dates of each sub assembly too. Issue where it would appear this screen wouldn’t honour the WO setting to ‘Add an extra day when creating sub assemblies’.
• Fix for ongoing issue when upgrading Manufacturing and update companies wouldn’t run successfully [‘Invalid object name ‘xxxx”]
• Fix to calculate the outstanding quantity to be booked instead of the ‘IsReceived’ flag. Issue when attempting to book in a works order when there is an outstanding quantity and the book button would not do anything.
• Fix to correctly set the works order status from ‘New’ to ‘Allocated’ to ‘Issued’ when there are bulk issue items on the works order.
• Fix to also ‘Unconfirm’ a bulk issue item when unissuing a works order.
• Fix to set the correct source and destination warehouse when booking a finished item in that is preallocated to a works order/sales order in another warehouse.
• Fix when creating works order from the ‘Generate Works Order from Sales Order’ screen to honour the ‘Default delivery buffer’ setting from MRP settings.
• Fix on the ‘Process Works Order’ screen to handle multiple finished items.
• Fix when creating an empty works order [“Object reference error”]

Material Resource Planning

• Fix to allow suggested purchase orders to still be created when there are no period exchange rates setup.
• Corrected the filtering on the ‘Suggested Works Order’ tab on MRP to be able to filter sub assemblies
• Fix when running MRP with items that are batch split and grouping sub assemblies is set. When creating the works orders create the parent works orders first and update the sub assembly reasons with the correct works order ID’s to allow them to be correctly preallocated once created. Fix to also correctly preallocate the batch split sub assemblies when creating the works order.
• Fix to handle not splitting by eco batch size for parent works orders as this now gets done at the point of creating works orders.
• Fix an issue when over ordering is turned off and suggestions were getting incorrectly deleted.
• Fix to correctly suggest works orders to be created in the correct warehouse dependant on the ‘Default Finished Item Warehouse’ stock setting.
• Fix to disable the ‘Run’ button on MRP when the user has no run options selected.

Kitting

• Fix for auto allocating kit lines when using the ‘Build Kit’ menu item and saving the kit
• Fix to correctly set a kit’s status when all lines are allocated and the kit would still get given a status of ‘Part Allocated’

Change in Functionality

Works Order Processing

• Added a ‘Max Batch Size’ column to the ‘Generate Works Order from Sales Order’ screen.
  • Previously only the minimum batch size was visible. This enables users who are also using the function to Split by Max batch size to more easily see the levels configured on the stock item. Creating a Works Order from this screen will honour these settings if not overwritten.
• Updated the ‘Booked Finished Goods’ web API endpoint to now accept a ‘Warehouse Name’ and ‘Bin Name’ to allow the bin to be selected for the item to be booked into.
  • Previously it was not possible to specify the location and bin that an item would be booked into using this API. Further information is available on the WebAPI Documentation – https://webapidocs.blob.core.windows.net/published/Documentation.html
• Added a destination warehouse field the works order form to view where the finished item will end up.

• • See https://www.sicon.co.uk/user-guide/additional-manufacturing-information/ for further information.
  • To improve visibility of when a Works Order will ultimately be transferred to another warehouse. For example, if a Sales Order will be despatched from Warehouse B, but the manufactured item is always built in Warehouse A. Historically it has not been easy to see this on the Works Order linked with the Sales Order.
  • Now, the linked Works Order will show as “Warehouse A” as usual for the production warehouse, but there is also an additional field showing Destination Warehouse as “Warehouse B” (parent WO/SO warehouse).

Material Resource Planning

• Added the ability to filter by multiple products group when viewing MRP results. This has been added on all three (Kitting, Works Orders and Purchase Orders) tabs.
  • It has always been possible to filter by one product group at a time on the Suggested Works Order tab. Now this has been extended so it is possible to select multiple product groups at a time to filter results by.
• Added a new screen when viewing the ‘Suggested Works Orders’ to allow the user to see what split is going to happen when they create the works order.
  • For sites who are using Min/Max batch sizes on stock items, together with the setting to split by Max batch size, it is now highlighted with an additional icon to show that a split will be made. Double-clicking the icon takes the user into this extra information.
  • Further information is available in the “Stock Item Settings” section of the MRP user Guide, and also in the Manufacturing Additional Information – https://www.sicon.co.uk/user-guide/additional-manufacturing-information/
• When running MRP and grouping sub assemblies to create the grouped sub assemblies as works orders on their own and no longer preallocate to just one parent.
  • Essentially this has updated to simplify how subassemblies are grouped and displayed on the Suggested Works Order screen in MRP. If users are not grouping subassemblies when running MRP this will not impact them.
  • Previously when running MRP and grouping subassemblies, although subassemblies were grouped, they were linked with the first parent found when running through stock demand. There was confusion around this, particularly when users are using the Split by Max Batch functionality.
    How the subassembly was displayed and preallocated was confusing. The subassembly quantity required for the first parent would be preallocated to the parent, but the rest of the subassembly would be booked into free stock. For some sites, they would want all of the subassemblies to go into free stock. For others, they would all subassemblies preallocated to all the relevant parents so the stock isn’t used elsewhere. In addition, this made tracking stock movement more difficult.
  • At the core, Group Subassemblies is designed for sites who wish to make a bulk of their subassembly(ies) to cover multiple works orders. Therefore, if subassembly grouping is applied when running MRP, these will now be created as individual works orders when actioned. They will be preallocated to the parents (if the parent is also created at the same time, and preallocating to reasons is enabled).
  • It is recommended that the MRP setting to “create selected works orders only” is enabled for users who are grouping subassemblies.
• We now show Suggested Auto Stock Transfer out and Suggested Auto Stock Transfer In in the stock movements screen for suggested works orders that are going to be transferred to another warehouse based on warehouse settings on the stock item.
  • If a production warehouse is configured on the Sicon tab within the WOP menus of a stock item, but demand is in a different warehouse, an automatic stock transfer will be completed at the point of booking in the Works Order. This is shown in the Future Stock Movements screen.
    For example, a Sales Order for a built item will be despatched from Warehouse B, but the stock item always needs to be made in Warehouse A.
    Once the Works Order is booked in, it will be preallocated to a stock transfer to move the stock from the Production Warehouse A to the Despatch Warehouse B.
• Reasons on the suggested transfer out are now showing on the stock movements screen.
  • Historically reasons have not shown for Stock Transfers. With the work done on improving visibility of warehouse movements, reasons will now be populated as well.
• Suggested stock transfers now appear for where there is free stock in the production warehouse instead of suggested works orders in the demand warehouse.
  • In the example where a Sales Order for a Built Item is despatched from Warehouse B, and the built item itself is always built into Production Warehouse A, if there is free stock in Warehouse A to cover the demand in Warehouse B, users will no longer see a Works Order suggestion into Warehouse A, but instead a Suggested Stock Transfer of the free stock from Warehouse A to Warehouse B.
• Added the ability to create a ‘Warehouse Stock’ preallocation for suggested purchase/works orders that are for ‘Min Stock’ suggestion for a different warehouse to the warehouse that it will be purchased into.
  • In line with the other Warehouse and Stock transfer changes outlined in this document, this is a new preallocation method for when there is a Minimum Stock demand in a different warehouse to where the stock will be purchased/built into.
  • For example, where there is a minimum stock level in Warehouse A, but purchased/built stock is always received/built into Warehouse B. When running MRP now, a minimum stock suggestion will be made for Warehouse B, and it will be preallocated to a Warehouse Stock transfer. This will be shown as an Auto Stock transfer from Warehouse B (Production/Purchasing Warehouse) to Warehouse A (Minimum Stock demand warehouse).
  • If the Purchase/Works order is created, at the point of booking/receiving in the item, an automatic stock transfer will be created to move the minimum stock requirement from the Production/Purchasing warehouse to the Demand warehouse.
  • Previously this kind of scenario would have been booked free stock into Warehouse B, and users would then manually need to create a stock transfer from the Production/Purchasing warehouse to the demand warehouse. (JS to confirm this bit).