Manufacturing

Back to release notes

250.0.3

Issues Resolved New Features Change in Functionality
New Features

Works Order Processing

  • [#15489] Added the ability to store scrap percentage on the Sicon WOP tab of a stock item.
  • [#16080] Added the ability for Sicon documents to fetch works order’s contact information when it is linked to a sales order.
  • [#15497] Added the ability to view legacy Sage 200 works orders within Sicon Works Order Processing.  To access this feature, the roles in Sage Admin must have “Sage 200 Works Orders” and “Sage 200 Works Order List” enabled.  This view is not intended to be a like-for-like replacement, its purpose is to retain historic reference information when Sage remove the legacy Manufacturing menu items.
  • [#15927] Added the ability to set a warehouse override at the BOM component line level.
  • [#13544] Improved the Works Order creation process to ensure consistency across these methods:
    – Create Works Order (Sicon works order processing menus)
    – Generate Works Order from Sales Order (Sicon works order processing menus)
    – Sales Order workflow (when saving a finished item and Sicon workflow is enabled)
    As part of this development, operations with a delay configured will now display the delay as a separate line on the Operations tab of the Works Order to improve visibility.

For sites with the “Always ask before creating sub-assembly” setting enabled, all prompts will now appear during the initial creation stage. This allows users to review each sub-assembly in sequence before confirming how they should be created.


Issues Resolved

Works Order Processing

  • [#15492] Fix for ‘Miscellaneous’ items being deleted when using the ‘Update From BOM’ routine.
  • [#15547] Fix to allow works order lines be unissued when they are linked to an undespatched sub contract line. Issue where there would be other sub contract lines which are desptached and it would require them all to be undespatched.
  • [#15683] WOP – Improve query for retrieving Works Orders in the Complete Works order window.
  • [#15995] Fix for the view used when running the Project ‘Health Checker’ tool when getting the committed costs transactions on a project to only include the ‘WOP’ and ‘WOP-COS’ transactions. Issue where it would appear it would double cost by including the ‘COS’ transactions incorrectly.
  • [#15994] Improved cancelling the Projects health checker tool part way through more gracefully. [“Cannot access a disposed object.
    Object name: ‘List’.”]
  • [#15502] Fix to allow serials to be selected from multiple bins when selecting traceables at allocation and the setting ‘Display Traceable At Allocation’ is enabled.
  • [#15773] Fixed issue when backflushing from barcoding or web API and the sub assembly would book the full quantity in even though the parent works order was only part booked.
  • [#15870] Allow repeated works order unbooking for traceable items when duplicate numbers are permitted.
  • [#15870]: Fix for when unbooking the same traceable item for a second time on a works order, a message would pop up saying the traceable item is unavailable. Duplicate numbering for the stock item would have to be on for this to happen.
  • [#15924] Fix to ensure “Picked” works order lines allocations cannot be reduced on the ‘Reduce Allocation Form’.
  • [#15967 Fix when closing the amend stock item form and the BoundObjects collection is set to null when Sicon Documents is installed. [“Value cannot be null”]
  • [#16693] Fix ‘Unable to cast object of type ‘Sage.Common.Controls.Panel’ …’ when the View Stock Item Details screen is opened.

Material Resource Planning

  • [#15765] Fix to honour the ‘Create selected works orders only’ setting when there is a batch item in the selection and there is no grouping of sub assemblies.
  • [#15765] Further fix to also ensure the correct sub assembly quantities are passed through when creating the works orders.
  • [#15694] Improve performance of ‘Load Usages’ button and apply fix for ‘A database timeout has occurred …’ error when SQL Server is running at compatibility level ‘SQL Server 2022 (160).
  • [#15863] Fix to update suggested purchase order reason when for suggested works orders after they have been created. Issue where a suggested works order would be created and then the suggested purchase order would get created after and it would not correctly preallocate to the works order line.
  • [#15863] Fix to ensure we have the correct reasons for suggested POs at the point we create them so that the ‘Material Planning’ tab on the PO shows the correct reason. If the reason was a different suggestion (Works order for example) then the works order is created first and the user doesn’t filter the PO tab before creating, it would mean incorrect reasons were shown.
  • [#16073] Fix for “deferred” suggestions being deleted when getting processed later and here is some free stock, but it may not fulfil the whole demand. This can lead to incorrect ‘Min Stock’ reasons being created.
  • [#16094] Fix to ensure the full variance posting from all booking transactions is reversed out when unbooking the works order.

Kitting

  • [#15686] If the allocated quantity on a sales order line is increased, the linked kit quantity is now reduced. If the sales order line is fully allocated, then the linked kit is deleted.

Barcoding

  • [#16691] Fixed issue where overhead postings were duplicating when backflushing a works order via barcoding. This is because the postings were created when booking in, and when completing the works order. This is also dependent on setting ‘Allow booking in before issuing components’ and unconfirmed costs.

Change in Functionality

Works Order Processing

  • [#15667] Added the ability to add a reason when adding works order lines via the web API method ‘Create New works order line’ (api/WorksOrderLineAPI/CreateNewWorksOrderLines).

 


Date applied: October 10, 2025