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