Manufacturing

Issues Resolved

Works Order Processing

• Fix to make sure we read the traceable item to get the correct ‘Use By’ date before sending it back… Issue where new SiWorksOrderSerialNumber were being created and then the information we would send back would be today’s date rather than the TraceableItems ‘Use By’ date which is set by Sage when calling the ‘Retrieve Production Orders’ web API
• Fix to overallocation WOP setting not allowing overallocations
• Further error logging when backflushing through the web API
• Fix for using the ‘Booked Finished Goods’ web API end point and it would complete part booked works orders causing it to post the full cost of the works orders incorrectly
• Fix to check an operation resource or component has been sent when creating a BOM through the web API
• Fix to not display the preallocation popup if the setting ‘Do not ask to allocate preallocated lines’ is true
• Fix when selecting the traceable tab and the user would get an error [“Object Reference Error”]
• Fix when creating the WIP summary when issuing components to check the stock item setting ‘Integrate with Nominals’ [“Object Reference Error”]
• Updated the API method (Create Labour Timesheet) to include OperationID, SiWorksOrderLineID, SiWorksOrderID, Quantity and Status
• Display better message when there is not enough stock in bin to allocate component line. Also fixed issue when using sage sop fulfilment methods to allocate, and needed to allocate across multiple bins
• Fix when viewing the ‘Traceable Item Enquiry’ and the traceable item is associated to a deleted works order and it would error out [“Unable to locate one works order with the works order number ‘X’]
• Fix to filter out deleted works orders on the view to get the current balances on a works order and unallocated view
• Fix when calculating the split of cost for finished items, to not change the value of ‘Standard Cost’ items
• Fix to use the bin that has been selected by user if the setting ‘Show allocations screen’ is turned on
• Fix to an issue where works orders created from the web API would not have project transactions created without having to amend the works order
• Fix when adding or updating an operation via the web API to correctly update the quantity field on the works order line that is associated to it with the expected hours value
• Fix when using “standard cost” finished items that have a higher value than the works order cost… when recalculating the lines on the ‘Finished Item Tab’ the value of the other finished items will be set to 0 unless they have been manually set. A variance posting will be posted upon completion of the works order

Material Resource Planning

• Fix when running MRP the user would incorrectly get suggestions made for warehouses that are marked as ‘Returns’ or ‘Direct Delivery’
• Stock transfers are now created between the works order finished item and the sales order line if they are pre allocated to each other and the warehouses are different.

Kitting

• Fix for an issue where kit line required quantities were being incorrectly calculated using the ratio which was only being stored to 5dp and therefore causing rounding errors, therefore when allocating and building a kit where the line quantities had changed it would would incorrectly recalculate the value to allocate or build
• Fix to filter the warehouse bins by the selected bin for the kit line… Issue on Web API where the user would pass a bin item in and this would not be used when issuing the kit line
• General clean up of the kitting settings screen
• Default the kit finished item quantity to 1 if this has not been set already adding a new kit line [“Attempted to divide by zero”]
• Fix corrected the line quantity that is required when part building a kit