220.0.18
Issues Resolved New Features 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.
New Features
Works Order Processing
- Setting added to set a default if we don’t show the prompt to update works order due date on sales order promised date.
- When adding operations to a works order, the BOM operation resource efficiency will be used to calculate estimated length.
Issues Resolved
Works Order Processing
- Fix to not set use by date against traceable items where the stock item doesn’t use use by dates.
- Fix to show the correct quantity remaining when receiving the final part of a preallocation that is less than the total of the booked quantity but that quantity is less than the total preallocated quantity.
- Fix to keep the child nodes of a works order expanded when booking works orders
- Fix to project integration to handle non stock items.
- Fix to show the non-stock setting nominal header in the works order settings screen.
- Fix to stop error when getting bin from warehouse hierarchy, using the data context when updating from BOM.
- Fix to stop error when using update from BOM on multiple works orders.
Material Resource Planning
- Fix to show the correct purchasing unit of measure and stop showing units that do not have a stock item unit.
Kitting
- Fix to creating a new sales order line that has a kit on without stock. If the user then selects to build the kit this will allocate the new kit to the line and then when the user would save this new line it would get allocated twice incorrectly.
Date applied: December 30, 2022