Manufacturing

Issues Resolved

• Fix when getting the estimated cost for a works order when associated to a project to filter out the deleted Sicon Prealocations otherwise we get duplicates and then the costing of the works order doubles, trebles etc
• Fix to also update the project transaction lines when a works order is associated to a sales order with the correct sales order line ID and sales order ID
• Fix when creating a template and it requires the user to input the template number, updated the validation message to inform them that it must be in a numeric format. If the user cancels this process it will no longer continue to create the template
• Fix when backflushing multiple works orders, to check if it is the ultimate parent when on the ‘Allocate and Issue’ stage. If it is the ultimate parent then only book at the final step of the backflush… Issue where works orders would get booked twice in the process if it was initally only part booked
• Fix when calculating the next available date for a built item to initialise the starting date to today’s date and also return today’s date if there are no movements otherwise dates will be in the year ‘0001’
• Fix to default the build time to today’s date otherwise the calculate can get return min date build times ending ‘/0001’
• Fix for bulk issue items to no longer allocate or issue these items when the setting ‘Issue Bulk Issue Items at Booking’ is turned off. If this setting is turned then they will still be issued at booking. Bulk issue items will also display as ‘Confirmed’ once the issue process has been completed
• Updated the message given when attempting to allocating only bulk issue items to a works order to state these get confirmed at the issue stage of the works order
• Fix when adding anew works order line to make sure we set the reason earlier in the process so that when the line gets updated it correctly populates the reason field when adding a history line
• Fix for posting project transactions when the setting ‘Issue To Project’ is turned off and it was creating duplicates
• Fix when using the web API method ‘Create WO from BOM’ to correctly set the passed in due date and works order name against the generated works order
• Fix unissue components not totalling quantity correctly if multiple part-issues were processed for the same item & bin. For example, issue 2 items, then 3 more, then unissue. This code will only unissue a quantity of 2.