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