Sicon Manufacturing is a set of additional modules for Sage 200, integrated with Stock, BOM, Sales and Purchase Order Processing. Including modules for Job Costing, Works Order Processing and Estimating, this package can be configured for one-off job costed manufacture or high volume repeat production manufacture. Material and Resource Planning provides suggested works orders and purchase orders plus a rough cut capacity plan at labour and machine levels.
221.0.77
Issues ResolvedIssues Resolved
Works Order Processing
- Fix backflush add stock button not adding new stock when warehouse hierarchy is enabled.
- Works orders no longer recalculates costing for non labour operations from the timesheet save on the labour tab.
- Fix when adding a new finished item to a works order and adding materials with a sub assembly and this would cause sage to hang.
- Fix to display the correct ‘Labour’ and ‘Machine’ costs on the ‘WIP summary’ report dependant upon labour/machine costing settings.
Material Resource Planning
- Fix for ‘Direct PO’ suggestions being missed when running MRP.
- Fix for standalone MRP displaying the company id of 0 when it has connected to a company.
Date applied: October 2, 2024
221.0.76
Issues Resolved Change in FunctionalityIssues Resolved
Works Order Processing
- Works orders improved date validation on the process works order screen.
- Fix to auto populate the quantity for a works order via the bill of materials when switching between Bill of Materials to create before creating a works order.
- Works orders tab data will also be refreshed on the projects enquiry screen when the refresh button is hit.
- Fix when using unconfirmed costs and receiving a purchase order where the component has been used on a works order line and it would incorrectly recalculate the cost. this would happen when issuing and unissuing the line multiple times.
- Fix to add some validation before printing the ‘Expediting’ report to check that ‘Expediting’ form has been run against this works order so that the colours appear correctly in the report.
- Fix print picking list ‘No data was returned for this report’ error after a works order number has been updated following preallocation creation.
- Fix to display works orders with no finished items on the ‘Process Works Orders’ and ‘Complete Works Orders’ screen.
- Fix ‘Process Works Orders’ screen buttons automatically selecting subassemblies, despite not checked/ticked in the list.
- Allow the project on a works order to be changed when it is linked to a sales order and the project is ‘N/A’. Also pull the same project as the sales order when using the ‘Generate Works Orders for Non Built Items’ menu option.
- Fix when completing works orders associated to projects and attempting to post a variance to the project [“Unable to reconcile project transaction. can’t find nominal record (urn: nl: // value:)”].
- Fix when adjusting a works order quantity and changing the works order lines, if the lines are allocated and we increase the line quantity to not unallocate and the reallocate the line. if the line is reduced and the allocation setting ‘Select Bin’ is true handle reallocating the line [“dicbinsandqtys object was returned as null by method sicon.sage200.worksorder.objects.coordinators.allocationcoordinator.getbinsandquantitiesforallocation()”].
- Fix to correctly update the ‘Completed Quantity’ of an operation when removing/deleting a timesheet line from the ‘timesheet entry’ screen.
- Fix for correctly calculating the ‘Future Buying Price’ of a part issued works order line when updating the quantity of the line.
- Fix for the ‘Update from BOM information’ incorrectly removing ‘Failed’ updates.
- Fix to reset the ‘IsIssued’ flag when an issued line has been increased from the ‘Update from BOM’ routine.
Material Resource Planning
- Improved integration with MRP and Approvals requestions for receiving orders through Sage as well as via Approvals.
- Fix for incorrect ‘Warehouse Stock’ preallocations being created in MRP, which would lead to incorrect ‘auto stock transfers’ being displayed on the ‘future stock movements’ screen.
- Fix to correctly filter the ‘Future Stock Movements’ screen when changing which warehouses to be displayed.
- Fix for MRP creating suggestions to arrive too late and grouping them into larger suggestions for ‘Min Stock’ or ‘Reorder Level’ only suggestions when the setting ‘Separate Suggestions per Warehouse’ is disabled.
- Fix for MRP not producing any ‘Suggested Purchase Orders’ when ‘Rescheduling’ is enabled.
- Fix to correctly set the ‘Default Purchasing Warehouse’ from warehouse hierarchy as the warehouse for a suggestion when the suggestion type is ‘Min Stock’ or ‘Reorder Level’ when running MRP with ‘Warehouse Hierarchy’ enabled.
- Fix to validate whether a purchase order line that is associated to a sub contract line has been despatched before the user attempts to receive that line in when attempting to receive the sub contract from ‘Purchase Order Processing’ in Sage.
Change in Functionality
Works Order Processing
- ‘Process Works Orders’ and ‘Complete Works Order’ screens now have new selection filters to allow you to list the works orders with unissued and unconfirmed works order lines
- Removed the sorting on the ‘Process Works Order’ and ‘Complete Works Order’ screens.
Material Resource Planning
- Updated the ‘split’ po function for ‘suggested purchase orders’ so that the user can split a new purchase order out with a greater quantity than was originally suggested and if there is no reason for this new purchase order line then it will be given the reason ‘split purchase order line’ allowing this line to still be created.
Date applied: September 18, 2024
221.0.75
Issues Resolved Change in FunctionalityIssues Resolved
Works Order Processing
- Fix when filtering the ‘Suggested Works Order’ tab, ‘Process Works Orders’ or ‘Complete Works Orders’ screens by ‘Stock Item Analysis Codes’ and the user would get an error. [“Invalid Object Name SIWorksOrderProcessView”]
- Fix when using the web API ‘Update Sage BOM’ where components are removed that are currently allocated to a sage BOM build, to allow these components to be deleted . [“‘the delete statement conflicted with the reference constraint \”‘fk_wopbomcomponentlinelink_bomcomponentline\”‘. the conflict occurred in database \x\”‘, table \”‘dbo.wopbomcomponentlinelink\”‘, column ‘bomcomponentlineid’.\r\nthe statement has been terminated.”‘]
- Fix when unissuing a works order line where the original bin it was issued from has been deleted. [“Object Reference Error”]
- Fix to enforce that the ‘Appointment Calculation Interval’ setting on the ‘Dates’ tab can only be ’15’, ’30’ or ’60’.
- Fix to allow finished item preallocations to be deleted from the works order ‘Preallocation’ tab, if the works order is not linked to a sales order or has has some booked.
- Reintroduced the route ‘api/operationworksorderline/{sioperationid}’ for updating works order operations.
- Fix to allow ‘Miscellaneous’ item quantities to put updated when using the ‘Edit All Quantities’ screen on a works order.
- Fix to not allow the ‘Yield’ value on a BOM record to be above 100.
Material Resource Planning
- Improved the handling of closing the MRP screen while it is still running and give the user the option to not close the form if it is still running. [“‘Thread was being aborted.”‘]
- Fix when viewing the ‘Future Stock Movements’ screen [‘Unable to update the object(sicon.sage200.materialplanning.objects.simrpsuggestedpoline, ), as the object has been deleted”]
- Fix for when viewing the ‘Future Stock Movements’ and ‘Auto Stock Transfers’ were appearing to be too low when there was a purchase order for multiple reasons.
- Fix to give the user a message when cancelling the creation of works orders from MRP so that it will stop creating them after the one it is creating. issue where after closing the screen it would continue to create the works orders.
Kitting
- Fix to correctly set the ‘Kit Cost’ field on a sop quote when a kit is linked to the quote line.
- Fix when building traceable kit items on the fly and then attempting to allocate them to a sales order when they are built. [“The quantity to allocate is greater than the quantity available at the location.”]
Shop Floor Data Capture
- Fixed issue when booking in finished item for a copied works order via SFDC, the identification number of the batch was the previous works order number, and not the new works order number.
Change in Functionality
Works Order Processing
- Added bespoke setting to show inspection templates when amending a component stock item.
Material Resource Planning
- Expanded the ‘display waring on MRP has results if new orders have been placed for stock items since MRP has run’ to work with suggested kits.
Date applied: September 4, 2024
221.0.74
Issues Resolved New FeaturesNew Features
Works Order Processing
- Added the ability to to convert estimates to works orders when converting quotes to sales orders from Sicon CRM.
Issues Resolved
Works Order Processing
- When completing an operation, the area on the works order is moving to the next area (linked to the next operation). But it wasn’t excluding deleted operations. It now does exclude deleted operations on the works order.
- Fix when changing the ‘Promised Delivery Date’ on a sales order line and the works order popup to update works order dates would cause Sage to be ‘Minimised’ or go to the back of the desktop.
- Fix to set the ‘Finished Item Warehouse’ to be same as the demand warehouse if this has been set for sub assemblies after looking at the stock item settings first.
- Fix when issuing traceable components and the setting ‘Show Traceable Issue Adjustment Screen’ is enabled and the user would get an error [“Object Reference Error”]
- Fix to filter out deleted works orders to be selected when entering a timesheet.
- Fix to allow the sales order dropdown to be filtered by the users inputted text on the ‘Generate Works Order from Sales Order’ screen.
- Fix when amending a purchase orders status from ‘Amend Order Status’ which has a sub contract associated to it and this would in turn remove the link between other sub contracts and their purchase orders.
- The inspection tab on the Amend stock item screen was not appearing for some stock items, and appearing for others that are not built items.
- Fix when using the ‘Update From BOM’ routine where an item appears multiple times on a BOM and this would incorrectly calculate the lines new quantity.
Improved logging messages displayed to the user when lines have not changed. - Fix when updated the run time for a labour item and the ‘Estimate Quantity’ on the ‘Labour’ tab would not update or refresh after save.
- Fix to filter ‘Deleted’ works orders when viewing an ‘Item Balances’ so the correct value is shown in the ‘Quantity on WO’ column.
- Fix to fetch the latest ‘Unit Cost’ for operation lines (Labour/Machine) when copying works orders.
- Adjust Works Order Booking checks for Works Orders created with Create Empty Works Order.
- Fix to honour the setting ‘Only use Production Lead Time for Works Orders’ when changing the due or start date of a works order when the works order has operations on it.
- Fix when the setting ‘Book Finished Item when receiving Sub Contract’ is enabled and booking in a works order after receiving the purchase order for a sub contract, to include the cost of the sub contract in the finished goods cost.
Material Resource Planning
- Adjust forecasts form to force dd/mm/yyyy format.
- The machine demand on the overall tab on the rough cut screen was showing labour demand instead of the machine demand.
- Prevent error when calculating a Sales Order you have created by converting a Pro Forma [“Index out of Range”]
Date applied: August 21, 2024
221.0.73
Issues ResolvedIssues Resolved
Works Order Processing
- Fix to allow completed purchase orders to be viewed from sub contracts.
- Fix to allow preallocations to be amended when a works order is associated to a Sicon Project. Only the ‘Finished Item’ preallocation will be locked down if the works order is associated to a sales order and Project OR if the works order is associated to a project and some of the works order has been booked in.
- Fix re apply the users chosen sort columns after refreshing the datasource for the components and finished items list.
- Fixed error that would appear when allocating misc stock item works order line and warehouse hierarchy is on. ‘Specified argument was out of range of valid values’.
- Fix to display the purchase order document number on the sub contracts tab. This will allow PO numbers to be visible on the works order at all times, including completed.
- Fixed issue where the delay time was not added to the remaining hours on the operations screen when editing the run time fields.
- Fix for the ‘Production Date’ not saving when it is amending on the ‘Additional Info’ tab.
- Fix to allocate sub assembly lines after operations have been added, when the sub assembly setting ‘Allocate sub assembly from free stock is available’ is enabled, so that if the line is required for an operation it can be split for the operation.
- Fix Allow user to unbook a Works Order where the returned traceable build item quantities cannot be retrieved from history using the finished item.
- Fix to not allow ‘Warehouse Hierarchy’ and ‘Show allocations screen to split allocations across multiple warehouses’ settings to be enabled at the same time.
- Fix to display the correct ‘Free Stock’ on a works order when ‘Warehouse Hierarchy’ is enabled.
- Fix for correctly validating whether a line can be allocated when using ‘Backflush’.
- Fix Process works orders screen now allows multiple works orders to be selected for label printing.
- Fix Update the Works Order Start Date when modifying the Works Order Due Date from SOP Order Line form.
- Fix to display the purchase order document number on the sub contracts tab. This will allow PO numbers to be visible on the works order at all times, including completed.
- Fix Exclude deleted Works Orders when retrieving by Works Order Number to prevent APIs from adding lines and operations to the deleted WO rather than the live WO.
Material Resource Processing
- Fix to filter out any deleted supplier quantity breaks when getting the price of a suggested purchase order line and using ‘Sicon Enhancement Pack POP008: Supplier Price Lists with Quantity Breaks’.
- Fix for ‘Suggested Auto Stock Transfers’ displaying to high of a quantity for the required demand.
- Fix to also display the ‘Preferred supplier lead time’ when viewing the ‘Future Stock Movements’ screen.
- Fix for duplicate entries on the ‘Future Stock Movements’ screen for ‘Project Issue’ lines when the setting ‘AutoIssueAfterGoodsReceived’ is enabled and the associated purchase order.
- Fix Move the Show Confirmed Checkbox setting to its own Advanced Features tab and use it to control when it appears and is populated on the Purchase Order Line form.
Date applied: August 7, 2024
221.0.72
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix to display the ‘Customer Name’ when a works order is linked to a sales order on the ‘Process Works Orders’ screen.
- Labour cost and quantity processing when apportioning quantity and remove labour lines from the Labour Items Actual Transactions Panel.
- Fixed issue where the works order created from a sales order line was not using the warehouse of the sales order line for the finished item of the works order. The sales order line warehouse will now be used unless there are warehouses set on the stock item to override.
- Fix for calculating the correct cost and variance when scrapping finished items that are ‘Standard Cost’.
- Disable Complete button if finished item added on an empty works order, disable Add if components or labour/machine lines are issued.
- Fix for the Start time reverting to 9AM on works order settings.
- Fix for incorrectly highlight the WO BOM Version on the works order desktop list when the columns are rearranged.
- Fixed issue where allocating with warehouse hierarchy on, would return a message saying no stock available, as it was trying to allocate against the incorrect warehouse.
- Populate Works Order Comment with the Order Number, Stock Item Description (including and amendment) and the Stock Item Code when generating a Works Order from a Sales Order.
Material Resource Planning
- Fixed error when running MRP and using warehouse hierarchy when the warehouse required is not found on the stock item. It will now use the first warehouse on the stock item if a warehouse to use is not found. [“Object Reference Error”]
- Fixed issue where allocating with warehouse hierarchy on, would return a message saying no stock available, as it was trying to allocate against the incorrect warehouse.
- Fix to load selected warehouses correctly when opening the ‘Future Stock Movements’ screen.
- Fix to also make sure the ‘Future Stock Movements’ screen opens with the correct selected warehouse when using ‘Warehouse Hierarchy’ in MRP from the ‘Suggested Works Order’ tab and the ‘Suggested Purchase Order’ tab.
- Fixed rescheduling to work for items that have no suggestions. Also made sure that we checked the ‘Production lead time calculation in working days’ setting when calculating the works order completion date for suggestions.
- Fix for duplicates appearing on the ‘Suggested Works Order’ tab when there are multiple units of measure.
- When creating a WO Approvals Requisition form MRP, the Description column is populated with the Item Description on the Stock Item line.
- Fixed when running MRP and using warehouse hierarchy when the warehouse required is not found on the stock item. It will now use the first warehouse on the stock item if a warehouse to use is not found. [“Object Reference Error “]
Kitting
- Fix to correctly update the cost of a kit line when the item is FIFO. Issue where it would set the ‘Total Cost’ using the ‘Average Buying Price’ of the stock item instead of using the actual ‘Issued’ cost of the kit line component.
- Fix when building a kit which has components that are ‘Miscellaneous’ to multiple the cost of these components by the quantity of the kit line.
- Fix to correctly display the ‘Actual Cost Per Kit Line’ when a kit is fully built.
Change in Functionality
Works Order Processing
- Added a new setting to handle if a purchase order lines item description should use the associated works order lines comment or use the stock items name or description dependent on the stock items settings
Material Resource Planning
- Added a new setting to handle if a purchase order lines item description should use the associated works order lines comment or use the stock items name or description dependent on the stock items settings
Date applied: July 24, 2024
221.0.71
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Allow WIP Summary data to be exported via the context menu.
- Extended the length of ‘SiWorksOrderLine’ ‘LineText’ to 4000 characters.
- Fix when using ‘Unconfirmed Costs’ to include traceable items when the goods have been received and then filter the purchase order transaction types so there is not duplicate when the purchase order has been invoiced on the ‘Traceable Enquiry’ screen.
- Fix to not allow the user to set a works order line quantity to 0 when using the ‘Edit All Quantities’ feature.
- Fix to move the warning “Please add a location first.” to the stock item tab itself. Issue where this would keep being displayed on a new stock item when there is a combination of just Contracts and Manufacturing installed.
- Fixed issue where the quantity on the operation was changing/set incorrectly when viewing a works order operation when it should equal the quantity of the works order. Also disabled the expected hours text box.
- Fix for opening a works order screen speed when warehouse hierarchy is enable for works orders.
- Fix to update the quantity and expected hours of an operation when the works order quantity changes.
- Fix to correctly display the ‘Line Cost’ and ‘Machine Cost’ of a machine line on the ‘Machine’ tab of a works order.
- Disable Complete button if finished item added, Disable Add if components issued on an empty works order.
Material Resource Planning
- Fix to display ‘Suggested Auto Stock Transfers’ on the ‘Future Stock Movements’ screen when there is a suggested purchase order that has been generated for a different warehouse to where the demand is as when the purchase order has been received the preallocation will move the stock to a Sicon stock transfer to be transferred to the original demand.
- Fix to add reasons to ‘Suggested Stock Transfers’ in MRP.
- Fix for creating suggested stock transfers for any movements before the earliest movement date. Issue where it would appear suggested stock transfers were including the supplier lead times in the transfer date.
Kitting
- If a kit quantity is increased, and there is a linked preallocation, then the preallocation will increase as well.
- If the sales order line quantity is increased, and the kit quantity is increased, then it would leave a reserved quantity on the WarehouseItem and the StockItem.
- Fix issue where there is no free stock, and the sales order line quantity is increased, the user would be asked if they wanted to create a new kit for the sales order line instead of increasing the quantity of the already linked kit.
Change in Functionality
Works Order Processing
- Added new menu item to add inspection results for booked in works orders.
Date applied: July 10, 2024
221.0.70
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix when part completing a part booked works order and it would generation an incorrect and inflated variance posting (‘Book in difference in cost’). This would be due the works order line cost being incorrectly recalculated.
- Fix to also not change the ‘IsIssued’ status of ‘Misc’ item works order lines when editing quantities or using the ‘Reduce Lines to Issued Quantity’ buttons.
- Fix when confirming costs of a purchase order line when they are linked to a works order line and unconfirmed costs is turned on and the line has been issued and unissued and this would recalculate the LineCost incorrectly and therefore when completing the works order it would generate an inflated ‘Variance’ posting.
- Fix to allow works order to be booked in when the setting ‘Reduce line quantity when booking’ is enabled and ‘Allow book before issue’ is not enabled and not all the works order lines have been issued. [“To book in the last item on this Works Order, all components must be issued”]
- Fix archive tab on the View Traceable History screen to retrieve the grid details. [“Unable to cast object of X to type Y”]
- Prevent user from modifying the Finished Goods Quantity for “Booked” Work Orders, but this check will be bypassed when the Works Order is flagged as ‘Continuous’.
- Reduced Current Stock level by to show only the free stock, not the in stock figure. Issue when viewing stock running balances.
- Improved the speed when creating works orders with operations. Can also get stuck when creating multiple works order from MRP.
Material Resource Planning
- Fix for suggested POs suggesting a larger quantity than is required when the stock item uses ‘Minimum and Usual order quantities’ and the quantity is for the minimum order quantity however it would then add the ‘Usual order quantity’ onto this incorrectly.
- Fix to make sure the MRP setting ‘Separate suggestions per warehouse’ is enabled when ‘Warehouse Hierarchy’ is enabled. Issue where this was not enabled and then suggested stock transfers were not being created.
- Corrected the link to the latest help and user guide.
- Exclude stock items where they are marked as “Do not include item in Materials Planning” for the warnings checks for Suggested Purchase Orders section of MRP process.
- Fix when grouping sub assemblies in MRP to correctly update the reason to the new grouped works order line so that it can be correctly preallocted when they are created.
- Fix to also correctly updated the reason document numbers when a works order has been created. This allows parent works orders to be created before the grouped sub assembly and then once the sub assembly has been created it will correctly preallocate to the parent works order line.
Kitting
- Corrected the link to the latest help and user guide.
- Allow for Kit Component Quantities to be recalculated when the Quotation Line Quantity has changed.
Change in Functionality
Material Resource Planning
- View Future Stock Movements – show Purchase Order buffer days in the Summary section when PO or Suggested PO lines are selected.
Date applied: June 26, 2024
221.0.69
Issues Resolved New Features ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Works Order Processing
Added the ability to complete ‘Empty Works Orders’ and therefore post ‘Actual’ transactions for non stock items against a project.
Within Sicon Works Order Processing, it has always been possible to create an empty Works Order (Sicon Works Order Processing – Works Orders – Create New Empty Works Order). This might be used to track stock that has been issued as part of another process (that doesn’t require building a finished item). Once all the components have been issued on an empty Works Order, the Works Order status changes to Booked and that’s how it stays…. until now!
For sites integrating Works Order Processing with Sicon Projects, this could be confusing in terms of viewing actual and estimated costs on the project. As there is no finished item to book in, there was no trigger to move the costs from estimated to actual, like there is on a standard works order, so a booked Works Order can still show committed costs:
There is a bit more to it than just moving the costs to actual, so have a look through the “Create New Empty Works Orders” section of the Works Order Processing Help & User Guide for more information on the postings that will be made, along with some recommended settings, before using this feature.
Issues Resolved
Works Order Processing
- Fix to correctly export the ‘Type’ field when exporting the works order history tab.
- Fix when viewing the ‘Works Order Expediting’ screen to exclude suggested movements when calculating the free stock. Issue where to would display not enough free stock on lines when there was enough free stock.
- Changing the Timesheet Entry Type in Project settings now updates the ‘Use hours instead of start and end time in timesheets’ tick box in WOP settings.
Kitting
- Fix to use the kit reference for batch numbers when the stock item is set to use ‘Order and Sequence’
Date applied: June 12, 2024
221.0.68
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix to remove the project transaction if the user sets the Project to ‘N/A’.
- Fix when multiple works orders for the same sales order are associated to the same project and then it would incorrectly only post 1 committed transaction. This can happen when a works order has a max batch size associated to it.
- Fix when creating PO’s from a works order to honour the suppliers ‘Pricing Source’. Previous issue where it would only set the price as the suppliers ‘List Price’ and not ‘Last Buying Price’.
- Fix to truncate the works order history reason when it is above 2000 characters long [“Cannot set the value of field (.Reason) to ‘xxxx’]
- Fix to auto uncheck sub assembly options on the ‘Sub Assembly Creation’ form if these have not been manually entered and another option has been selected so that selection will auto populate with the required quantity. This will also select this option and auto populate with the amount left that is required if the user has set values in another sub assembly option.
- Fix for duplicate ‘Sicon Stock Attribute’ entries being made when amending a works order.
- Fix to exclude estimates from the ‘Process Works Order’ screen.
Material Resource Planning
- Sicon Tab on Amend Customer Account and Create Customer Account includes the MRP tab (rather than having a separate MRP tab)
- Fix when selecting items on the ‘Suggested Purchase Order’ tab on MRP and it would select multiple lines at once.
- Fix when generating a suggested purchase order to set the date to the earliest time the stock goes below minimum when the only movements in a warehouse are ‘Suggested Stock Transfers’.
- Fix when viewing the ‘Future Stock Movements’ screen to correctly get the ‘Earliest PO Arrival’ date.
Kitting
- Enable the Build Kit button when you set Qty to Allocate to zero on SOP Create New Order Item line for a kit item, and also disable if you then override it back to match the Order Line Quantity.
- Fix to allow allocation if kit item selected by item name.
- Quantity field is disabled and greyed out after selecting the kit, but still enabled when selecting by stock code.
Date applied: June 5, 2024
221.0.67
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Prevent users from editing quantities if their user permission do not allow them to.
- Force batch attributes to be entered when they are compulsory and default values exist when backflush from Barcoding.
- Operation Scheduler will no longer display deleted works orders.
- Also Deleting operations from the scheduler should function correctly without erroring [“Object Reference Error”]
- Null entries in SiWorksOrderStage preventing area from being selected. Prevent a row with no department from being added.
- Fix when competing works orders and it would incorrectly display ‘Unconfirmed Lines’ and therefore would not complete if the sub assembly was also to be completed. The ‘Unconfirmed Lines’ popup would also appear blank.
- Fix when viewing the ‘Works Order Cost Summary’ tab and the ‘Overhead’ values would be massively inflated.
Material Resource Planning
- Fix for the ‘Previous MRP Results’ screen not displaying as an open window in Sage.
- Fix to only include out transaction types of ‘Sales Order’ and ‘WO/BOM Issue’ out types when calculating stock item sales over lead time.
- Fix to loading the sales over lead time screen.
- Fix to not require a supplier when using the MRP stock item settings import.
- Fix to allow the user to select the top parent when completing works orders and it will also complete all sub assemblies if they can be completed.
- Updated the ‘SiconWorksOrderProjectCostsView’ so that it now includes a date to be used for reporting
Kitting
- Prevent picked kits from being unallocated.
Change in Functionality
Works Order Processing
- Added ability to issue to works order after receiving a purchase order.
- Updated the works order line import to the new import format.
Material Resource Planning
- Added new ‘Stock Item’ and ‘Warehouse’ filters to the ‘Sales Over Lead Time’ screen.
Date applied: May 22, 2024
221.0.66
Issues Resolved New Features Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Material Resource Planning
- Added the ability to delete suggestions;
- It is now possible to delete a suggestion in MRP. This can be helpful for sites with large volumes of suggestions, who wish to physically remove the suggestions on screen until MRP is run again. Selecting the item(s) and then clicking ‘Delete Suggestion’ will remove the suggestions from the MRP results view (current or previous, if viewing retrospectively). When MRP is run again, if the demand still exists the suggestions will return.
- Added a new warning icon when MRP has run to flag any items with a warning icon where a new order has been raised against that item. Currently behind a new setting (Display a warning on MRP results if new orders have been placed for stock items since MRP has run).;
- From Sicon Material and Resource Planning – Utilities – MRP settings, the new setting is called “Display a warning on MRP results if new orders have been placed for stock items since MRP has run”. In case it’s not obvious, what it does (if enabled) is display a little warning triangle on any stock items that have had an order raised since MRP was last run. It’s nothing too sophisticated, it doesn’t reduce any suggested quantities or tell a user what’s been raised. It is simply a way of illustrating that something has changed since MRP was last run.
- Grouping Subassemblies Display change in Material & Resource Planning: We’ve made a change to the way MRP groups subassemblies when this setting has been applied (in MRP Options). Previously, if MRP was run using one of the settings to Group Subassemblies, MRP would have first gathered all stock demand and then preallocated the first subassembly, and any child subassemblies, with the first parent demand found. The remaining parent works orders would not have a subassembly linked with them and instead the excess subassembly stock would go into free stock, (which could then later be consumed on those parent works orders). Why have we made this change? : Ultimately, linking all subassemblies with one demand goes against the intention behind grouping subassemblies. In addition, this approach could be confusing to track and explain the logic to new users. In certain scenarios, it could even result in an excess quantity of stock being suggested if used with the Sicon stock item settings to split by maximum Economical Batch sizes. So now, when using Group Subassemblies in MRP, each grouped subassembly is presented in a flat structure and any suggested works order actioned will create its own Works Order.
NB: if grouping subassemblies when running MRP, it is recommended to enable the MRP setting to “create selected works orders only”.
Issues Resolved
Works Order Processing
- Fix when entering a timesheet against an operation and the user would get an error when there is no quantity remaining [“The Quantity entered is above the remaining quantity to complete this operation. Quantity Remaining: 0.00000”]
- Fix when associating a works order to a sales order and the works order comments on a sales order line would get overwritten to blank.
- Fix when filtering on the ‘Process Works Orders’ screen for a sub assembly with multiple prealloctions and it would group the quantities together incorrectly.
- Fix when adding a new component line to a works order and the selected warehouse would get overridden if the stock item had a ‘Default Component’ set against it.
- Fix when filtering an ‘To’ date on the ‘Process Works Orders’ and it would include works order for the next day where the time is set to ’00:00:000′.
- Disallowed amending component line allocations if the component line is fully issued.
- Fix when booking a works order that has a project on it and is preallocated to a slaes order. If the user then cancels the preallocation to issue the item to the project. [“Object Reference Error”]
- Fix when creating works orders from ‘Trial Kitting’ to auto generate the works order number at the point of creation to make sure the works order format is consistent when ‘Auto Generate Works Order Numbers’ is enabled.
- Fix to correctly update the actual quantity of a labour line when adding a timesheet line.
- Fix when updating a works order quantity that is associated to a sales order line and the quantity of the sales order line changes to calculate the new net values of the line and sales order.
- Fix when creating works order from the ‘Generate Works Orders from Sales Orders’ to check whether the assigned works order number is in use before attempting to create the works order [“Works order with the WoNumber ‘xxxx’ already exists”]
Material Resource Planning
- Fix to create works orders from the lowest BOM level first when the setting ‘Create Selected Works Orders’ is false and grouping sub assemblies is on.
- Fix when creating a new works order and it would update to check when the last MRP run to validate MRP has run once otherwise there will be no date [“String was not recognized as a valid DateTime.”]
- Fix for items not appearing as suggestions when there is a min max/reorder level set against the stock item and no free stock available.
- Fix when creating suggested works order and the user would get an error once they have been completed [“Index out of range”]
- Fix when running MRP and incorrect ‘Warehouse Stock’ type preallocations were being created and this would then lead to ‘Min Order’ or ‘Reorder Level’ suggestions to not be created [“Object Reference Error”]
- Fix for the ‘Previous MRP Results’ screen not displaying as an open window in Sage
Change in Functionality
Works Order Processing
- Added the ability to just create a works order line without a sub assembly and without using any stock when creating a works order. This option is would mostly be used when creating works orders from MRP.
Kitting
- Updated the ‘Import Kits’ screen to use the new import format
-
-
Why have we changed the format?
Various reasons;- Consistency across the Sicon modules.
- You don’t need Excel installed to generate and save the import template.
- You can easily see if a record is invalid and split out the invalid entries into a new template to work with later.
- If there’s a simple change required, that change can be made in-screen and the system will save the import file.
No more navigating to the old Excel, finding the incorrect row(s), making the adjustment, re-importing, pressing validate and hoping-and-praying you’ve updated the right record… just change it then and there.
-
Date applied: May 8, 2024
221.0.65
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Corrected the filtering of the ‘Generated Date To’ filter on the ‘Process Works Orders’ screen.
- Corrected the namespace of the ‘Process Works Orders’ screen for third party scripting
Material Resource Planning
- Fix for the ‘Calculate’ button on sales order always returning today’s date.
- Fix when running MRP for phantoms where there are the same item and it was creating a suggestion for the wrong quantity. If a suggestion got decreased on the second line of the works order it would not take this into consideration and therefore give the wrong quantity.
General
- Compatibility with DevExpress v23.2
Date applied: May 1, 2024
221.0.64
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Updated the works order view to pull the ‘LineComment’ through so that when viewing the ‘Works Order’ tab on a project the description for non-stock items is displayed in the tree view
- Fix to not show the sub assembly popup form when the setting ‘Always Ask Before Creating Sub Assembly’ setting is turned off.
- Fix to exclude deleted operations when getting the next sequence number for new operations. Issue where the sequence would jump numbers and then would not allow for the operations to be reordered.
- Fix when the setting ‘Always ask before creating sub assembly’ is off and ‘Allocate subassembly it from free stock if available’ is turned on and there is some free stock but not enough to fulfil the works order line. No longer popup with the sub assembly form and instead use the free stock available and create a sub assembly for the remaining amount.
- Fix when deleting a purchase order line that is linked to a sub contract line and this would then incorrectly unlink all sub contract lines from PO lines.
- Fix when posting credit notes. [‘Incorrect syntax near ‘S’. Unclosed quotation mark after the character string ”.”]
- Fixed problem when issuing stock after a pre allocation is fulfilled, and the traceable details were missing. [“Object Reference Error”]
- Fixed object reference error when part allocating a works order line and warehouse hierarchy is enabled.
Material Resource Processing
- Fix when running MRP and no suggested works orders would be created when the reason for the line is a Sicon Stock Transfer.
- Fix when using the ‘Calculate’ button on a sales order and it would return dates in the past and then that would also mean the ‘Production Date’ from WOP settings would not get correctly added.
Kitting
- Prevented error messages from appearing if cancel disassembly half way through disassembly. Also added warning messages.
- Prevented the user from attempting to continue the disassemble process by not entering any traceable item details when adding traceable component items, and thus cause problems with the disassemble of the kit.
Date applied: April 17, 2024
221.0.63
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix when using the ‘Generate Works Orders from Sales Orders’ screen to get the ‘Default Finished Item Warehouse’ and ‘Default Component Warehouse’ from stock item settings.
- Fix to allow operation times to be updated when they have no duration time and the works order ‘Due Date’ gets updated.
- Fix to allow operation times to be updated when they have no duration time and the works order ‘Start Date’ gets updated.
- Added further validation when selecting how to fulfil a sub assembly when the ‘Sub Assembly Creation’ popup appears [‘Input string not in correct format’]
- Removed inspection questions from popping up when issuing a component line on a works order. Also made sure that the inspection template options are only available on the amend stock item screen for BOM items.
Material Resource Planning
- Fix when running MRP to get the correct finished item warehouse for nested sub assemblies where the reason hasn’t been generated yet but the demand warehouse has been.
- Fix to set the correct component warehouse on a works order suggestion otherwise when viewing a suggestion on FSM it would only display the ‘Out’ and not the ‘In’ as no warehouse would be set on the parent works order line.
- Fix to correctly display the finished item warehouse for MRP suggestions.
- Fix to get the correct quantity for a sub assembly works order when it is part of a phantom and there are multiple of these phantoms on a BOM.
- Fix when creating works orders from MRP and it would try to update a suggestion link to a works order that doesn’t exist and would throw an error silently so it looks like the screen had froze [‘Object Reference Error’].
- Fix the validation when selecting a direct delivery suggested PO if the sales order has ‘Use Invoice Address’ checked.
Change in Functionality
Works Orders Processing
- Improved inspection templates to be stored at multiple levels, not just at a global level. Inspections can also be recorded at a traceable item level.
Date applied: April 10, 2024
221.0.62
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix to highlight any traceable items where the ‘Use by’ or ‘Sell by’ date is before today’s date when amending a works order lines allocation.
- Fixed problem with error ‘Stock item with id 0 cannot be found’ when selecting the Issue button on the Process Works Order screen.
- Fixed issue where a stock analysis code is mandatory, but analysis code on the stock item is not set, and we using auto numbering, then an error would occur: ‘Analysis Code is mandatory and does not have the value specified in its list of allowable values.’
- Fixed works order settings for spare text fields where a ‘:’ was left in the label, and thus would display the spare text field on the additional info tab on the works order incorrectly.
Kitting
- Fix when a kit already exist for a sales order line to update the kit quantity and it’s component when the setting ‘Prompt for kit creation for sales order line shortage’ is not enabled.
Change in Functionality
Works Order Processing
- Added new setting to always use the works order numbering when creating works orders. Therefore, if the user creates a works order from a sales order, it will use the works order numbering format, not the sales order number.
Date applied: April 3, 2024
221.0.61
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
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
- 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.
- Added a ‘Max Batch Size’ column to the ‘Generate Works Order from Sales Order’ screen.
- Added a destination warehouse field the works order form to view where the finished item will end up.
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.
- 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.
- 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.
- 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.
- Reasons on the suggested transfer out are now showing on the stock movements screen.
Suggested stock transfers now appear for where there is free stock in the production warehouse instead of suggested works orders in the demand warehouse. - 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.
Date applied: March 27, 2024
221.0.60
Issues Resolved New Features Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
- Significant Speed Improvements | Sicon Works Order Processing
- These speed improvements, predominantly in the Process Works Orders Screen, will assist sites who use complex, layered BOMs and we’ve also given the screens a facelift in the process. Subtle changes, but columns such as the “Unconfirmed” and “Unissued Lines”, (which a user cannot edit) now show with a different icon compared to columns such as “Printed”, which the user can manually override.It is now significantly faster to load. With this facelift we’ve rewritten the code underneath. For sites with complex multi-layered BOMs that historically can take a long time to load, users should notice a significant improvement loading and working with this screen.
- We have done similar with the Complete Works Order Screen within Sicon Works Order Processing, and the Suggested Works Order view within Sicon Material and Resource Planning, Material Planning results.
- For more information, please refer to the WOP Help & User Guide; https://www.sicon.co.uk/user-guide/works-order-processing-help-and-user-guide/#3-3
- Enhanced Update from BOM Functionality | Sicon Works Order Processing
- Within Sicon Works Order Processing, it is possible to use the Update from BOM feature to update a Works Order with any amendments that have been made to the linked BOM since the Works Order has been created. We have now enhanced the functionality so this feature works with more scenarios.
- Why have we made this change?
Previously, only Works Orders with a status of New or Allocated could use this feature. This is because once a component has been part or fully issued, the stock item may have been consumed, so quantities could not be updated on the Works Order.
This logic still applies however, we recognise that for some sites they may want to add more stock, or reduce just part of the works order quantities. As such, from Sicon v221.0.60 it is now possible to update Works Orders with a status of New, Allocated, Issued and Part-issued, if the below criteria is met;- If the component quantity has been increased on the BOM | On the Works Order, increases will be reflected in line with what has already occurred, e.g. if 10 were required and fully issued on the Works Order, updating the quantity to 15 would set the line so it no longer shows “Issued”.
- If the component quantity has been decreased on the BOM | Decreases will only be allowed down to the already-allocated/issued quantity on the Works Order, e.g. if 10 were required and 6 have been issued on the Works Order, updating the quantity to between 6-9 would be updated, but anything less would remain as it is.
- If component lines have been removed on the BOM | Component lines will only be removed on the Works Order if they have not already been allocated/issued and the Works Order setting to allow removal of lines is turned on.
- Changes will be recorded to the History Tab of the Works Order as well to improve visibility of the success of the Update from BOM routine.NB: Update from BOM still does not work with operations, only material items.
- For more information, please refer to the WOP Help & User Guide; https://www.sicon.co.uk/user-guide/works-order-processing-help-and-user-guide/#3-4
Issues Resolved
Works Order Processing
- Fix when adding a sub assembly line to a works order and Sage would just hang. Included a new progress bar to update the user when exploding these BOM lines out
- Fix when un-issuing a works order line when the works order is associated to a project to create a ‘WOPRTN’ transaction to reverse the cost out of the Project
- Fix when issuing stock to a project upon booking and the setting ‘Use Project Header when Issuing’ is true to use the project header nominal code override
- Fix when deleting a ‘Labour’ or ‘Machine’ line to correctly display this type and code on the works order history
- Fix when opening the ‘Generate Works Orders from Sales Order’ screen [“Cannot find specified Warehouse”]
- Fix to disable the control on the WOP stock settings to configure ‘Bulk Issue’ items when they are not a component or are of a traceable stock type
- Fix when unbooking a works order where a variance has been posted when booking and then once un-booked an extra unbook variance would get posted. This then leaves a value within WIP incorrectly
- Corrected the works order name to following the conventional “ItemCode (ItemName)” format when creating works orders from the ‘Generate Works Orders from Sales Orders’ screen
- 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 backflush error ‘Serial selection failed on item ‘xxxxxx’, identification no ‘x,x’, bin ‘xx’ – Of x.xxxxx supplied, x.xxxxx were unavailable.’ if multiple allocations exist for the same traceable item
- Fixed issue with issuing stock during backflush where the allocated works order line is allocated across multiple bins. It was also popping up asking for the traceable items when the stock items are set to auto select the traceable items
- Fix when adding multiple BOM lines to a works orders [“Invoke or BeginInvoke cannot be called on a control until the window handle has been created”]
- Fix to allow ‘WO Comments’ on a new sales order line to be saved and then edited again without saving the line
- Fix when closing without saving a sales order line [“Unable to update object, due to it’s state”]
- Fix when completing a works order to and works order would incorrectly reset the ‘Average Buying Price’ of a stock item when there are unconfirmed costs. The movement balance for a works order should be deleted before we query the database, and we only want to look for records that are associated to this works order
Material Resource Planning
- Fix to correctly set the ‘ Default Component Warehouse’ on a works order when it has been created from MRP
- Fix when running standalone MRP and it would leave a disconnected login
- Fix when creating suggested works orders [“Value does not fall within the expected range”]
- Fix to correctly calculate the unit cost for a purchase order line when using multiple units of measure and the purchasing unit is overridden on the stock item settings
Barcoding
- When writing off stock in dynamic stocktake and the stock was allocated on the works order component line, then allocated quantity and the status of the works order was not updated until the works order was opened in Sage. We now update these straight away
Change in Functionality
Works Order Processing
- Added more logging when running ‘Update From BOM’ methods to inform the user of changes made. Also allow works orders that have a status of ‘Part Issued’ or ‘Issued’ to also be updated
- Improved the performance of the ‘Process Works Order’ and ‘Complete Works Order’ screens
Material Resource Planning
- Improved the performance of the ‘Suggested Works Order’ tab
Date applied: March 20, 2024
221.0.59
Issues Resolved New Features Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Works Order Processing
Added the ability to complete ‘Part Booked’ works orders via the ‘Complete Works Order’ screen: This may seem like an obvious feature, but with the potential for complex Work in Progress (WIP) nominal postings, it was historically safer to force users to raise a final booking that would trigger a reconciliation of WIP. This was to ensure that the final item was booked in at a value that would bring the WIP nominal postings back to zero for the Works Order in question. For example, if 10 items had been created, but only 9 have been booked in, historically a further booking for the final 1 would have been required (it is still possible to process this way, so no obvious changes are required by users). It is now also possible that instead of booking the final item as above, the option to Complete a Part Booked Works Order can be used to trigger a posting of any outstanding WIP. This will be posted to the Finished Item Variance and then mark the Works Order as Completed. Therefore, to use this feature users must have a nominal configured in the Finished Item variance setting within the Works Order Settings:
Information around this feature can be found in the Complete Works Order section of the Works Order Processing Help and User Guide.
Issues Resolved
Works Order Processing
- Fix to filter out deleted operation lines on timesheets.
- Fix on the complete works order screen for using the ‘Expand All’ button and this making the screen fall over after a period of time.
- Fix to operation rate being used for actual labour time instead of employee rate on Works Order.
Material Resource Planning
- Fix when running MRP for suggested purchase orders to be raised for stock items that are ‘Built/Bought’ ‘Default Bought’ when the demand is for a works order/ suggested works order.
- Fix when using the ‘Generate Works Orders From Sales Orders’ screen to correctly filter by the ‘Promised Delivery Date To’ field and to also allow the columns to be sorted.
- Fix when using the ‘Generate WO From SO’ screen and changing the filters without using the clear filter and it would filter using some of the old filters.
- Fix when running MRP for it to honour the ‘Fixed Quantity’ setting for BOM lines.
- Fix when running MRP with dynamic forecasts to also adjust the demand of a forecast for built items
Kitting
- Fix when adding standard lines to a sales quote/proforma to populate the ‘Unit/Kit Cost’ field upon creation.
Change in Functionality
Works Order Processing
- Added the ability when attempting to complete part booked works order to allow the user to reduce the works order line quantities down to the quantity that has been issued on that works order at that time
Date applied: March 6, 2024
221.0.58
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix when deleting a works order [“Object Reference Error”]
- Fix to correctly update the actual quantity of a labour line when adding a timesheet line.
- Fix to correctly set the ‘Ultimate Parent WOID’ when adding new sub assemblies to a works order via the ‘Update From BOM’ routine.
- Fix to exclude works order templates when displaying the ‘Quantity on WO’ and ‘Unallocated on WO’ values on the ‘View Stock Item Balances’ screen.
- Fix when unbooking an works order with overhead and Sage will look to use an exchange rate nominal and this may not be set and this is incorrect [“The account specified does not exist”]
- Fix to allow the user to update just the ‘Quantity’ field when editing a machine transactions.
- Fix to update the existing transaction when editing a machine transaction and not create a new line each time
- Fix to also display ‘Non-Stock’ works order lines if they are included in the cost of the works order when viewing the works order tab on the ‘Project Enquiry’ screen
Date applied: February 28, 2024
221.0.57
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fixed problem with duplicate actions on adding operations to a works order in web API.
- Fix when reducing the quantity works order lines when reducing the finished item quantity of a works order, to correctly set the allocated amount to 0 and set lines correctly to ‘IsIssued’ if the reduction in the finished item quantity is the same as the quantity booked (The works order will be changing to a ‘Booked’ state)
- Fix to allow works order lines that are issued to be changed as long as the quantity doesn’t decrease below the issued amount.
- fix to also check whether there is a max batch set against a stock item to create the min/max batch split when using the ‘Generate Works Order from Sales Order’ screen
Material Resource Planning
- Fix to include ‘Suggest supplier via stock purchase orders’ and ‘Suggested direct delivery purchase orders’ into the ‘Future Stock Movements’ screen
Change in Functionality
Material Resource Planning
- Added a ‘Suggested Header’ column for suggested purchase orders that will come from default settings or operations dependant on the reason for the suggestion. This information is then passed through when creating the suggested purchase order or Approvals purchase requisition
Date applied: February 21, 2024
221.0.56
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix if Backflush from Barcoding/Web API fails only un-book fished goods if some stock has been added
- Fix to maintain the link when creating a link between a quote and an estimate
Material Resource Planning
- Fix when generating works orders in MRP and the sub assembly group is set to ‘All’ but the parent is set to ‘Never’ and this would not generate the correct quantities. Also a further fix to make sure max batch sizes are considered when creating these works orders and to also allow grouping when these are set
- Fix when creating ‘User Suggested POs’ and there are already suggested PO’s that the line can be linked to. However the user does not select one and hits OK. [“Index out of range”]
Change in Functionality
Works Order Processing
- Added a new setting to display the traceable allocation selection at the allocation part of a works order line when the allocation setting ‘Use Stock Fulfilment’ setting is enabled
Date applied: February 14, 2024
221.0.55
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix Internal Issue ‘Incorrect syntax near ‘S’. Unclosed quotation mark after the character string ”.’ error
- Removed the setting to ‘Show message to allocate/issue bulk issue items’ as they are now ‘Confirmed’ and then issued at booking when the setting ‘Issue bulk issue items at booking’ is turned on.
- Fix to also correctly confirm bulk issue items when using back flush so that it correctly books the back flushed items in
- Fix when copying a sales order when there was linked works order [“Execution timeout”]
- Fix to reset the picked quantity when unallocating a works order line
- The line cost of a works order line was incorrect if the works order line was issued multiple times, and then the cost was updated via an invoiced purchase order. Unconfirmed costs need to be on.
- Fix to remove already scrapped (written off) serial or batch numbers when scrapping components on a works order
- Fix to only create a scrap log for lines that have been scrapped. Issue with traceable items where a log was being created with 0 quantities and cost. Also added further detail to the reason if it is a traceable item to display the traceable number
Material Resource Planning
- Fix when running MRP and the suggested works order contains phantoms and within these phantoms contains the same sub assembly. The suggested works order quantity would add all these quantities together for each individual suggested sub assembly incorrectly.
Date applied: February 7, 2024
221.0.54
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix to return the stock item default component warehouse for a sub assembly suggestion so the correct demand warehouse is checked when running MRP. Issue when sub assemblies were being incorrectly suggested when there is stock available
- Added scripting to the ‘Timesheet (Single User) ‘ screen within the Projects menu, so that the user can select ‘Works Orders’ when entering a timesheet
- Fix to correctly filter the traceable enquiry when selecting ‘Sicon Works Orders’ and component traceability is turned on
Material Resource Planning
- Fix when opening the ‘Future Stock Movements’ screen from MRP when the use has selected to use ‘Warehouse Hierarchy’ to also pass through the dates selected otherwise the information outside of the MRP run dates will be displayed
Date applied: January 31, 2024
221.0.53
Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Change in Functionality
Works Order Processing
- Enhanced the ‘Generate Works Orders from Sales Orders’ screen to give the user more feedback and progress when generating the works orders. Improved the loading speed when displaying the works orders that need to be created.
Date applied: January 24, 2024
221.0.52
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Works Order Operations methods/endpoints error handling will now write to Web API Log + Validate timesheet creation team/resource is set to avoid error generated if SiconResource is NULL.
- Fix when using the ‘Update from BOM’ routine and not all works orders were getting updated. This could have happened if the ‘Default Component’ warehouse was not set on the works order.
- Fix to disable the ‘Update From BOM’ button when a works order is ‘Part Issued’, ‘Issued’, ‘Part Booked’, ‘Booked’ or ‘Completed’
- Fix when creating a works order and the stock item using min and max batches to correctly create the works orders with the correct quantities that are calculated using these settings.
- Fix to filter the works order drop down to only display works orders that have sub contract lines associated to them
- Fix for a rounding error when viewing a stock items balances on the ‘Unallocated on WO’ column
- Fix when viewing the ‘Unallocated on Works Order’ to filter out works orders that are ‘Suggested’, ‘Templates’ or ‘Estimates’
Material Resource Planning
- Fix to correctly display the reason when a suggested kit is for an operation line.
Kitting
- Added a message when receiving a purchase order when there is a preallocation to a kit line and setting ‘Use allocations’ is turned off, to inform the user that preallocations will be completed upon receipt however will not be allocated to the kit line.
Change in Functionality
Material Resource Planning
- Added a project column when create a approval purchase order. This now stores the project so that approvals can then assign this project to the purchase requisition
Date applied: January 18, 2024
221.0.51
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix when ‘Allocating’ and ‘Issuing’ bulk issue items from the ‘Process Works Orders’ screen to no longer allocate and issue at this point and only ‘Confirm’ the bulk issue items
Material Resource Planning
- Fix for correctly adjusting the unit cost when using ‘Unit of Measure’. This should get done at the point we create the ‘Suggested Purchase Order’ as this sets the ‘Unit Price’
Date applied: January 10, 2024
221.0.50
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
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
Date applied: January 2, 2024
221.0.49
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix to update works order from BOM where not all component lines were updating.
- No longer allow works orders that have been ‘Issued’ or ‘Booked’ to be updated via ‘Update from BOM’
- Fix to keep the link between a works order (SOPOrderReturnLineID) when the works order is booked and the preallocation is completed. Issue when viewing the ‘Works Order’ tab on a sales order and once complete this works order would not appear in the list of works orders for the sales order
Date applied: December 12, 2023
221.0.48
Issues Resolved New Features ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Works Order Processing
- Added ability to select/deselect and delete multiple operations. Included a progress bar to track progress of deletion.
Issues Resolved
Works Order Processing
- Store the works order ID in the ‘Second Reference’ field on the movement balance table to help identify them easier when coming to confirm them upon completion of a works order. Issue when confirming works orders with unconfirmed costs where the works order number is longer than 20 characters long.
- Fix for an issue when booking ‘Unconfirmed Costs’ works orders and they would get set to complete incorrectly.
- Fix to remove warehouses from being selected dependant on whether the current user has that access to that warehouse from the works order settings on the works order line allocation screen.
- Fix when despatching sub contract purchase order lines and it would duplicate the despatch popup box after despatching the first line.
- Fixed issue where if a traceable item was setup for auto number generation, and custom traceable numbers were entered on the works order, then extra numbers were appearing when booking in the finished items on the works order.
- Fix when calculating the next available date and switching between the radio buttons to keep hold of the calculated date.
- Fix when drilling down into this date to not recalculate the information again and instead load the screen with the calculated lines
Material Resource Planning
- Fix to override the warehouse for suggested purchase orders with the ‘Default Purchasing Warehouse’ set on the stock item if there is one set.
Date applied: December 6, 2023
221.0.47
Issues Resolved New Features ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Material Resource Planning
- Added the ability to select multiple follow up types when filtering the MRP results screens
- Added a new setting for production lead times to allow suggested works orders generate for weekends
Issues Resolved
Works Order Processing
- Fixed issue where the cost of the works order line was not updating if when an purchase invoice is recorded for the stock of the works order line. This is if unconfirmed costs is on and we are updating at invoice, and if nominal integration is off.
- Refresh on amend works order screen was not updating the issued cost field after a purchase order was invoiced.
- Fixed the persistence of setting ‘Print Labels when items are reserved serials’
- Fixed update BOM record via web API when version control is enabled. It wasn’t finding the correct BOM version.
- When the description of the labour resource was changed in Sage manufacturing register, then the description on the Sicon team was not updated.
- Fix to correct the labour/machine postings made to a project when there is no finished item
- Fixed issue with project costing using new single project cost transaction, where the committed cost was calculated incorrectly if there was labour estimate and actual transactions involved.
- Fix when reducing a works order quantity to default the batch allocation quantity for a works order line to the reduced quantity when there is only one batch
- When creating a sub assembly on a works order, the popup to create the sub assembly was appearing multiple times if the user had changed companies multiple times.
- When deleting the preallocation for a works order to sales order on the amend works order screen, the link from the works order to the sales order line was not removed. It now removes this link and therefore no longer displays the sales order number on the works order header.
- Fix to correctly set the sub assemblies due date when the parent works order start date (which can be set through operations)
Date applied: November 29, 2023
221.0.46
Issues Resolved Change in Functionality ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
- fix to correctly subtract the sum of all the preallocations for a sales order line to get the corect quantity required when generating a suggested works order. Issue where it was giving the incorrect sales order as the reason as this would join to the SiconPreallocation table multiple times (per preallocation) and this would give confusing results
- Fix for when a sub assembly was pre allocated to multiple parent works orders and the warehouses on the parent are different, it was creating sicon stock transfer with the lines the quantity of the booked in quantity, not the pre allocated quantity. This was therefore creating stock transfer lines with the incorrect quantity on it.
- Fixed object reference error when saving a sales order after selecting the Payment tab just before saving.
- Fix when using the ‘Copy Lines’ feature in Sicon Distribution when on a sales order to also copy the Manufacturing attributes that have been set on the original line that got copied
- Fix when creating a works order either through ‘Generate Works Order from Sales Order’ or ‘MRP’ to also copy the attributes from the sales order to the works order
- Fix when querying the works order issue history table to get the current allocated and issued batches for each works order lines
- Fix when querying the works order issue history table to get the current allocated and issued batches for each works order lines
- Fix Booking Finished Goods with auto-generated batch/serial numbers jumping sequential numbers if the batch/serial already exists without order number prefix
Change in Functionality
- Added new tab to add bom drawings to a works order
- Added options to print bom drawings
- Added new settings to set the format of the traceable numbers when booking in traceable numbers.
- Made sure the settings were on a hidden features tab in settings screen. Also made sure we didn’t get an error if the number of #’s entered in the format was something other than 4 #’s
Date applied: November 22, 2023
221.0.45
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
- Fix when getting the estimated cost for a works order when associated to a project to filter out the deleted Sicon Prealocations otherwise we get duplicates and then the costing of the works order doubles, trebles etc
- Fix to also update the project transaction lines when a works order is associated to a sales order with the correct sales order line ID and sales order ID
- Fix when creating a template and it requires the user to input the template number, updated the validation message to inform them that it must be in a numeric format. If the user cancels this process it will no longer continue to create the template
- Fix when backflushing multiple works orders, to check if it is the ultimate parent when on the ‘Allocate and Issue’ stage. If it is the ultimate parent then only book at the final step of the backflush… Issue where works orders would get booked twice in the process if it was initally only part booked
- Fix when calculating the next available date for a built item to initialise the starting date to today’s date and also return today’s date if there are no movements otherwise dates will be in the year ‘0001’
- Fix to default the build time to today’s date otherwise the calculate can get return min date build times ending ‘/0001’
- Fix for bulk issue items to no longer allocate or issue these items when the setting ‘Issue Bulk Issue Items at Booking’ is turned off. If this setting is turned then they will still be issued at booking. Bulk issue items will also display as ‘Confirmed’ once the issue process has been completed
- Updated the message given when attempting to allocating only bulk issue items to a works order to state these get confirmed at the issue stage of the works order
- Fix when adding anew works order line to make sure we set the reason earlier in the process so that when the line gets updated it correctly populates the reason field when adding a history line
- Fix for posting project transactions when the setting ‘Issue To Project’ is turned off and it was creating duplicates
- Fix when using the web API method ‘Create WO from BOM’ to correctly set the passed in due date and works order name against the generated works order
- Fix unissue components not totalling quantity correctly if multiple part-issues were processed for the same item & bin. For example, issue 2 items, then 3 more, then unissue. This code will only unissue a quantity of 2.
Date applied: November 22, 2023
221.0.44
Issues Resolved New Features ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Works Order Processing
- Added the ability to complete works orders on a specified date
Material Resource Planning
- Added a new warning message when creating purchase orders informing the user if they have selected a quarantined warehouse and this purchase order line will not be used when running MRP
Issues Resolved
Works Order Processing
- Fix to correctly split works orders if by the specified minimum batch size when creating works order from sales orders
- Fix when backflushing works orders with sub assemblies which only contain bulk issue items to correctly issue and allocate and book these at the ‘Allocate and Issue’ stage of backflushing. If not then these won’t be booked in before the parent is booked in and therefore the user is unable to fully backflush
- Fix when backflushing works orders and the user selects to only backflush the sub assembly to correctly follow the process through. Issue when it would come to booking in the sub assembly and it would not appear on the list to be booked in
- Fixed issue where the create sub assembly form would appear during creating a works order, and then afterwards Sage would crash.
- Fix when booking a finished item in with the setting ‘Enable Finished Products Tab’ enabled and this would leave the works order in a ‘Booked’ state rather than ‘Complete’
- Fix for issue when the setting ‘Allow Book Before Issue’ was enabled or unconfirmed costs is turned on when completing works orders no nominal postings would be created for Labour, Machine, Sub Contract and Overhead items. Also in the case of unconfirmed costs no ‘Add Finished Item’ transaction would occur
- Fix when adding new lines to purchase orders that have sub contract lines on them and the user would be informed this cannot be created as it is linked to a sub contract
- Fix to reintroduce a warning message when the setting ‘Allow Book Before Issuing all Components’ is turned on and not all works order lines have been issued
Material Resource Planning
- Fix when using the ignore follow up on suggested works orders and purchases order. If the option is set to ignore and the user filters the screen this will remain greyed out and cannot be checked
- Fix when using the calculate button to check there are items to calculate… Issue where the button would be pressed and there was no standard item SOP lines [“Value cannot be null”]
Kitting
- Fix to correctly enable or disable the ‘Disassemble’ button on sales returns
Date applied: November 1, 2023
221.0.43
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Corrected issue when viewing the ‘Materials’ tab on the works order settings and settings would not appear
- Rationalised the allocation settings within the ‘Materials’. By default now the only option that will be available will be ‘Use Sage Stock Fulfilment’ (Formally ‘Use Sage SOP Fulfilment’) setting. Anyone using existing allocation settings will see no change and will remain on that setting when upgrading.
Date applied: October 19, 2023
221.0.42
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Works order form additional information tab – corrected tab index order, fixed cursor appearing at the end of the production date field, allowed a decimal place within the numeric field and fixed information saving as soon as the WO is created.
- Fix when deleting a works order with sub assemblies [“Execution timeout expired”]
- Fix when unbooking a works order when unconfirmed costs are turned on, check nominal postings have been made before creating a WIP Summary posting [“Object Reference error”]
Date applied: October 17, 2023
221.0.41
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix when importing works order lines to honour the setting for sub assemblies ‘Allocate From Free Stock If Available’
- Fix to exclude deleted preallocations when getting the ‘Actual Quantity’ for creating a project transaction after booking in a finished item [“Object Reference Error]
- Fix for the components summary tab on works order screen not showing any details.
Material Resource Planning
- Fix for grouping suggestions when the grouping matches set the date to the earliest suggestions, issue where suggestion were too late as the earliest suggestion was a sub assembly
Kitting
- Fix when building a kit and it would incorrectly check that enough of each kit line has been allocated for the quantity to build
Date applied: October 10, 2023
221.0.40
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix an issue when amending or completing works orders and it would refer to a Sicon Projects dll when Sicon Projects was not installed [“Could not load file or assembly ‘Sicon.Sage200.Projects.Objects version x or one of its dependencies”]
Date applied: October 6, 2023
221.0.39
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix when getting operations to delete, when refreshing the rough cut screen [“Object Reference Error”]
- Fix to pass through the ‘Name’ and ‘Description’ in the correct order when creating a new Sicon team off the back of creating a new Labour resource Group… Issue where the description was being set as the name and the name as the description
Material Resource Planning
- Fix when creating user suggested purchase orders to exclude quarantined warehouses from being selected and attempt to default the warehouse to the same as the original suggested purchase order if that location exists on the stock item
Date applied: October 3, 2023
221.0.38
Issues Resolved New Features ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Works Order Processing
- Added components onto operations
- Added a summary list on the Materials tab
Issues Resolved
Works Order Processing
- Fix when updating a quotes selling price that is linked to an estimate, to send through the total selling price from the estimate, issue where the cost value was being sent through
- Fix when changing the works order quantity to make sure component line quantities honour the stock setting ‘On adding line to works order round quantity up to’
- Fix to reset the ‘Completed’ flags on copied operations when copying a works order
- Fix to create ‘WIP Summary’ entries when unissuing or unbooking a works order
- Fix when creating a works order where the child sub assembly has a eco batch quantity and it was displaying to set this quantity to a negative figure. This would happen when there was enough free stock to fulfil the works order line and then a the eco batch popup would appear suggesting to create a works order for a negative value
- Fix when creating a purchase order for a works order line to set the document date to todays date
- Fix corrected the works order list view to get the correct BOM version
- Fix when backflushing works orders where sub assemblies contain no materials to book these sub assemblies in as part of the ‘Allocate and Issue’ process so the parent works order can be issued correctly
- Fix when creating a works order sub assembly to make sure we do not over preallocate the parent works order line… Issue where economical batch size was turned on and this would create 2 sub assemblies which combined have a greater total than the original works order line. This would result in the parent works order line being over preallocated
Material Resource Planning
- Fix when running MRP for only suggest PO’s for supplier via stock or direct deliveries [“Value cannot be null”]
- Fix when running MRP where a BOM would have the same stock item and it would duplicate the child BOM line suggestions
Kitting
- Fix if the user adds kit line to back order when using the ‘Build Kit’ menu item and they then build the rest of the kit. Make sure to unlock the new sales order lines… Issue when editing the order it originated from [“Must set field StockItem”]
- Corrected an issue where the radio buttons on the settings screen in the conversion tab where all grouped together
Date applied: September 26, 2023
221.0.51
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix to display a message when generating works orders from sales orders and the item that the works order is being created for is set to ‘Default Bought’. Brings this inline with manual works order creation.
Date applied: September 18, 2023
221.0.37
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix when attempting to book in a works order where lines are bulk issue and of stock type Miscellaneous, setting ‘Issue Bulk Issue Items At Book’ as true and these lines wouldn’t get correctly issued. Therefore the works order wouldn’t get booked in
- Fix when using the setting to ‘Issue Bulk Issue Items At Booking’ to exclude bins where the free stock is in minus to issue from
- Fix to adjust the sub contract line quantity when the associated purchase order line quantity has been adjusted. Check to make sure this doesn’t go below the allocated or despatched quantity
- Fix to display a message when generating works orders from sales orders and the item that the works order is being created for is set to ‘Default Bought’. Brings this inline with manual works order creation
- Fix when allocating a works order line with the setting ‘Auto Allocate To A Bin’ and it would not allocate any stock when there is free stock available
- Added a new flag on the ‘SiWorksOrderLineIssueHistory’ table to show when a line has been unissued. Now create a new entry on this table for ‘Unissued’ lines so that we can get true linking to the transaction history table
- Fix to correct store the production date and continuous flag of a works order when the works order is created [“Object Reference Error”]
- When component list refreshes on the amend works order screen, the list would go back to the top, when the users would prefer it to stay in the current position. This is particularly useful with large works orders.
- Updated the unbooking message when there is not enough stock in the location it was booked into to give the user some more information
- Fix to correctly display the ‘Allocated’ or ‘Issued’ batches to a works order when viewing on the context menu
- Fix to check the user has selected a ‘BOM/Template’ before searching [“Object Reference Error”]
- Fix to increase the maximum value of a numeric field before setting this value… Issue where values stored above 100 would keep getting set back to 100 when amending a works order
Material Resource Planning
- Fix when getting the works order min stock, reorder level or maintain zero suggestions to check the ‘Default Built/Bought’ flag on a stock item… Issue where suggested works orders were being created for items that are ‘Default Bought’ items when it is only a re-order level suggestion needed
- Fix to suggested works orders quantity allowing value to be set to a negative number or zero.
- Fix to prevent user from adding inputting 0 into the quantity field of suggested purchase order lines table
- Fix the clear the ‘Follow Up’ filter on the suggested purchase order tab in MRP when hitting the ‘Clear’ button
Kitting
- Fix when attempting to disassemble kits on a sales return and the user would get an error [“Invalid column name ItemDbKey”]
- Fix to also stop the prompt to create a kit on the fly when creating a new sales return
Date applied: September 12, 2023
221.0.36
Issues Resolved New Features ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Kitting
- Added new kitting web API methods to create, allocate and build a kit, these web API methods can be used when the ‘Use Allocation’ setting is turned on
Issues Resolved
Works Order Processing
- Fixed to store the reason code in the SiWorksOrderHistory table
Material Resource Planning
- MRP will now honour the Projects setting ‘Auto Issue After Goods Received’ and any purchase orders that are associated to a project will display in the ‘Future Stock Movements’ screen as being automatically issued and will also not be considered when running MRP
- Fix when creating suggested purchase orders, to honour the setting ‘Supplier Lead Time Calculations in Calendar Days’… Issue where suggestions for weekends were being brought forward to the Friday incorrectly
Date applied: September 5, 2023
221.0.35
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix when there is no works order cost and we calculate the values to split when there are items that are standard cost [“Attempted to divide by 0”]
- Fix to keep phantom lines all together when they are added to a works order… Issue where multiple phantoms would get added and when viewing the works order there would be no order to how they were added
- Fix to hide the ‘WIP Summary’ tab when the stock setting ‘Integrate with nominals’ is turned off
Kitting
- Fix when using ‘Add To back Order’ in kitting and part way through the user would get an error [“Collection was modified; enumeration operation may not execute”]
- Fix for some of the sales order lines that were created would be “locked” and therefore could not be edited
- Fix to also get the ‘Unit Selling Price’ for the new sales order lines when adding them to the sales order
Date applied: August 30, 2023
221.0.34
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix when with Projects Integration and Works Orders and it would ignore the setting “Issue Stock to Projects”
Date applied: August 23, 2023
221.0.33
Issues Resolved New Features ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Works Order Processing
- Added the ability to copy batch attributes across all batches when booking in a finished item
Issues Resolved
Works Order Processing
- Fix when duplicating or loading a stock item where there are Manufacturing attributes [“Failed to update objects”]
- Fix to correctly export the manufacturing attributes set when exporting from ‘Sub Contract Maintenance’ screen and the item is the finished item of a warehouse.
Added a purchase order filter to this tab to make searching easier - Fix to allocations form not displaying components in the correct sequence
Date applied: August 16, 2023
221.0.32
Issues Resolved New Features ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Works Order Processing
- Added a new web API method to get works order finished item transactions (Get Works Order Finished Item Transactions)
- Added a new setting to default the ‘Use by’ date on a finished item that has a shelf life to be calculated from the ‘Booked In’ date
Issues Resolved
Works Order Processing
- Fix to make sure we read the traceable item to get the correct ‘Use By’ date before sending it back… Issue where new SiWorksOrderSerialNumber were being created and then the information we would send back would be today’s date rather than the TraceableItems ‘Use By’ date which is set by Sage when calling the ‘Retrieve Production Orders’ web API
- Fix to overallocation WOP setting not allowing overallocations
- Further error logging when backflushing through the web API
- Fix for using the ‘Booked Finished Goods’ web API end point and it would complete part booked works orders causing it to post the full cost of the works orders incorrectly
- Fix to check an operation resource or component has been sent when creating a BOM through the web API
- Fix to not display the preallocation popup if the setting ‘Do not ask to allocate preallocated lines’ is true
- Fix when selecting the traceable tab and the user would get an error [“Object Reference Error”]
- Fix when creating the WIP summary when issuing components to check the stock item setting ‘Integrate with Nominals’ [“Object Reference Error”]
- Updated the API method (Create Labour Timesheet) to include OperationID, SiWorksOrderLineID, SiWorksOrderID, Quantity and Status
- Display better message when there is not enough stock in bin to allocate component line. Also fixed issue when using sage sop fulfilment methods to allocate, and needed to allocate across multiple bins
- Fix when viewing the ‘Traceable Item Enquiry’ and the traceable item is associated to a deleted works order and it would error out [“Unable to locate one works order with the works order number ‘X’]
- Fix to filter out deleted works orders on the view to get the current balances on a works order and unallocated view
- Fix when calculating the split of cost for finished items, to not change the value of ‘Standard Cost’ items
- Fix to use the bin that has been selected by user if the setting ‘Show allocations screen’ is turned on
- Fix to an issue where works orders created from the web API would not have project transactions created without having to amend the works order
- Fix when adding or updating an operation via the web API to correctly update the quantity field on the works order line that is associated to it with the expected hours value
- Fix when using “standard cost” finished items that have a higher value than the works order cost… when recalculating the lines on the ‘Finished Item Tab’ the value of the other finished items will be set to 0 unless they have been manually set. A variance posting will be posted upon completion of the works order
Material Resource Planning
- Fix when running MRP the user would incorrectly get suggestions made for warehouses that are marked as ‘Returns’ or ‘Direct Delivery’
- Stock transfers are now created between the works order finished item and the sales order line if they are pre allocated to each other and the warehouses are different.
Kitting
- Fix for an issue where kit line required quantities were being incorrectly calculated using the ratio which was only being stored to 5dp and therefore causing rounding errors, therefore when allocating and building a kit where the line quantities had changed it would would incorrectly recalculate the value to allocate or build
- Fix to filter the warehouse bins by the selected bin for the kit line… Issue on Web API where the user would pass a bin item in and this would not be used when issuing the kit line
- General clean up of the kitting settings screen
- Default the kit finished item quantity to 1 if this has not been set already adding a new kit line [“Attempted to divide by zero”]
- Fix corrected the line quantity that is required when part building a kit
Date applied: August 9, 2023
221.0.31
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix for using the ‘Booked Finished Goods’ end point and it would complete part booked works orders causing it to post the full cost of the works orders incorrectly.
- Fix when selecting the traceable tab and the user would get an error… No longer join to the stock item table on the control as we do this by default [“Object Reference Error”].
Date applied: July 28, 2023
221.0.30
Issues Resolved ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
Issues Resolved
Works Order Processing
- Fix updated the data type on the finished item request object for DateTime types to help with serialization.
- Fix to when using the ‘BookedFinishedItem’ API method when booking non traceable items in to not include or validate the traceable information.
- Fix to when allocating a sub assembly pre-allocation to pass through the correct quantity… Issue where the full works order line quantity was being passed through and this would cause it to error as there was not enough free stock.
- Added a new setting to allow the user to select whether they would like the use by date to be set via the production date or by the earliest component date.
- Fix to get the correct cost of a purchase order line when creating PO’s from a works order… Issue with suppliers in different currencies and changing the value even if the value come from the stock item supplier
- Fix to set the BOM component line type when posting a comment line to the BOM creation methods [“You must specify a valid Stock Item for a Component Line.”].
- Amended the MRP sql script by stopping it picking up all transactions of transactiongroupID 1 with replacement suggested (6,15,23).
- Fix to item name not displaying name for any stock code on subcontract management form grid.
- better handling when there we don’t have a cost price to recalculate the values from [“Attempted to divide by zero”] – Enable and disable the split line button dependent on the quantity booked in
- Fixed issue where ‘Use By’ date was being reverted to the current date for booked items.
- Fix for recalculating the values/percentage when new items have been added and the cost of the works order has changed.
- Fix to make sure our finished item totals are correct before we book and unbook a finished item, issue with recent finished item changes where the unbook value would be different to the booked value also always set the cost of the works order if there is only one finished goods and set percentage to 100.
- Fix to when using the ‘BookedFinishedItem’ API method when booking non traceable items in to not include or validate the traceable information.
- Fix to update the percentage and variance when there is only one finished item on the finished item tab
Date applied: July 28, 2023
221.0.29
Issues Resolved New Features ImportantImportant Info
ALL USERS MUST BE LOGGED OUT WHEN UPGRADING TO v22.1 FOR THE FIRST TIME. THIS IS BECAUSE WORKS ORDER FINISHED ITEM TRANSACTIONS WILL BE SWITCH TO BOM BUILD TRANSACTIONS, DUE TO HOW THE SAGE STOCK VALUATION REPORT HANDLES UNCONFIRMED TRANSACTIONS.
TRANSACTION HISTORY FOR UNCONFIRMED COSTS WHERE THE NOMINAL HAS NOT BEEN UPDATED WILL HAVE THE COST VALUE REDUCED TO 0. THIS IS TO FIX INCORRECT VALUES BEING SHOWN ON THE RETROSPECTIVE STOCK VALUATION REPORT.
New Features
Material Resource Planning
- Added options to group suggested works order sub assemblies by a defined period in MRP.
Works Order Processing
- New message box pop up on the works order form -Appears if stock item warehouse doesn’t match the default component warehouse, finds the reason why and displays it, if stock item doesn’t exist in either WOP settings on stock item details or WOP settings default component warehouse the message will display where it HAS been set to.
Issues Resolved
Works Order Processing
- Fix to when retrieving the movement balance record for a works order to calculate the cost of the works order to only sub string this value when it is over 20 characters long.
- Fix when issuing stock to a project [“Object Reference Error”].
- When component list refreshes on the amend works order screen, the list would go back to the top, when the users would prefer it to stay in the current position. This is particularly useful with large works orders.
- Fix to get the correct sub assembly number when creating a works order
- Updated the ‘Create Sage BOM’ and ‘Update Sage BOM’ web API methods to allow the user to add or update operation resources on a Sage BOM
- fix to when booking an item in where not all components have been issued and the backflush screen would appear but would not correctly populate.
- Fixed an object reference error when updating / creating BOM from web api when no operation details are provided.
- Fix to set the requested delivery date when adding a sub contract line to an existing PO to the operation due date… This follows how the requested delivery date is set when generating a PO.
- Fix to display to the user whether a purchase order line is linked to a works order sub contract when the user is going to cancel an order and then allow them to either cancel the deletion process or they will hae the associated sub contract transaction deleted [“Object Reference Error”].
- Fix to when creating a works order with sub assemblies to pass through the correct warehouse for the finished item warehouse [“Object Reference Error”].
- Fix for getting the correct nominal amount when posting hte issue cost for the WIP summary… Previous issue where it was pulling the average cost of the item however this could be different for FIFO items.
- Fix to use the total cost column to get the correct total value when updating a quote from the works order summary… Issue previously where the unit value was larger than the total and therefore this would send an incorrect value back to the quote.
- Fixed works order appearing as ‘completed’ instead of ‘booked’ when the WO number is greater than 20 characters.
- Fix when deleting a works order where there are sub contracts and therefore no stock item associated when adding this to the history to use the line comment rather than the item code
Kitting
- Fix to when building kits on the fly on a sales order and a reserved quantity would get left on the stock item and the setting ‘Use Allocation’ was turned on… Issue would occur when there is some free stock available that can be allocated to the sales order but doesn’t make the required quantity and this value would then go to reserve on the stock item but would not clear.
Date applied: July 28, 2023