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.
- Previously it was only possible to use Update from BOM on New or Allocated orders. This has now been updated to allow changes to Part Issued and Issued, where the values are higher than what has been issued. (E.g. if you have issued 5 components, and the BOM now only requires 3, this line will not be changed on the Works Order).
- On the Works Order, History tab, changes to the Works Order as a result from running the Update from BOM will show more detail to illustrate the above.
- Improved the performance of the ‘Process Works Order’ and ‘Complete Works Order’ screens.
- For sites with complex, multi-layered BOMs, working with these screens could take a long time to load. These screens have been re-written to reduce the time taken to expand and filter these results.
Material Resource Planning
- Improved the performance of the ‘Suggested Works Order’ tab.
- For sites with complex, multi-layered BOMs, working with this screen could take a long time to load. These screens have been re-written to reduce the time taken to expand and filter these results.
Date applied: March 20, 2024