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). See Material Planning Help and User Guide for more information.
- 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 Top-level works orders from MRP, where grouping has been enabled and the subassembly works order will be created later for the lower levels.
Kitting
- Updated the ‘Import Kits’ screen to use the new import format.
- Sicon imports are gradually being updated to a standard method across all modules, and the Import Kits has now been updated to follow this format. The import change is to make importing simpler. The process will prompt the user to first save the import file (so it doesn’t matter if Excel isn’t installed). The import can be manipulated on-screen if simple mistakes need correcting. And the import can be split between successful and unsuccessful rows. Further information is available in the Kitting Help and User Guide, under the Import Kits section.
-
-
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