Manufacturing v26

Issues Resolved

Works Order Processing

• [#19052] Errors are no longer thrown when changing the sequence of operations in a works order.
• [#19169] Works order operations are now moved together in groups and those groups are highlighted in the grid.
• [#18629] Fix for TraceableItems and TraceableBinItems being incorrectly deleted after being booked in. This can lead to further problems when amending sales order lines when a preallocation has been completed and it appearing as though the sales order line has not been correctly allocated.
• [#18618] BOM lines with a quantity of zero will no longer be added to works orders. Import Works Order Line will now show a validation error for Component/Finished Item lines with a line quantity less than or equal to zero.
• [#18842] Fix when adding a new line on the ‘Bulk Issue’ screen in works orders. [“Object Reference Error”]
• [#18908] Fix when tabbing through the components tab when amending a BOM and if nothing was selected in the ‘Warehouse’ column it would remove any new lines that had been created.
• [#19050] Fix when manually adding a sub contract operation to a works order and it would generate an extra operation line incorrectly.
• [#19173] Fix to reinstate auto printing of works order labels once a works order has been booked in.
• [#19428] Fix when creating a works order with comment lines. [“Cannot set the value of the Field (.BomComment) to ‘X'”]

Material Resource Planning

• [#19146] Fix for suggested orders not being generated for ‘Min Stock’, ‘Reorder’ levels when warehouse hierarchy is enabled and the stock level of the warehouse is currently below the min or reorder level.
• [#19100] Fix when selecting all on the suggested purchase order tab then sorting by a column and selecting unselect all and it would not uncheck all the items, it would uncheck only a few of them.

Shop Floor Data Capture

• [#19154]: Fixed issue when completing an operation from SFDC and was getting the following error: Unable to update the object (Sage.Manufacturing.BusinessObjects.BillOfMaterials.BomOperationResourceDataObject, ), as the object has been deleted.

Issues Resolved

Works Order Processing

• [#18555] Updated tree views to help with intermediate database timeouts.
• [#17333] Fix to not allow works orders to be created when they contain operation without a resource or a subcontract. Display this as a warning to the user when setting up BOMs with operations too. This is because it can lend to further issues further down the line when booking in the works order.
• [#18815] Fix when using the ‘Update from BOM’ feature and it would appear to not to update all the lines. Report any errors back to the user. Issue here was a sub assembly line without a sub assembly works order [“Sequence contains no elements.”]
• [#18357]: Fixed issue where the issued quantity of a component line would be set incorrectly when adding time to an operation. This is if the component line was linked to the operation. This would only occur sometimes.
• [#18847] Fix to add an active lock when a works order is being created to avoid other users entering the works order when it has not fully been created.
• [#17333] Fix to improve the error handling when generating a works order from a sales order and when using the workflow options in WOP. Also no longer give the option to add an operation without a resource to the BOM.

Material Resource Planning

• [#18286] Fix for incorrect suggested PO quantities being raised when an item uses ‘Usual Order Quantities’.
• [#18879]: Added warehouse lookup to ‘Suggested Purchase Order’ tab.
• [#18820] Fix for the ‘Include suggestions from last MRP run’ filter not working correctly on the ‘Future Stock Movements’ screen.

Kitting

• [#18598] Fix when building a kit from a sales order line that is a batch type. [“Cannot set the value of field (.TraceAvailForDespatch) to x”]
• [#18598] Fix to correct display the required amount to be allocated for batch kit component lines when it has been part allocated. This can happen when allocating the lines, then increasing the it quantity and allocating again.

Issues Resolved

Works Order Processing

• [#18815] Fix when using the ‘Update from BOM’ feature and it would appear to not to update all the lines. Report any errors back to the user. Issue here was a sub assembly line without a sub assembly works order [“Sequence contains no elements.”]
• [#18820] Fix for the ‘Include suggestions from last MRP run’ filter not working correctly.
• [#18700] Within Process Works Orders, printing no longer deselects selected child works orders.
• [#18759] Creating an estimate from a quote now factors in stock item batches and will ask if you want to create multiple estimates to adhere to batches.
• [#18755] Fix for the missing traceable item tool to look at all current booked transactions to find missing traceable items not just the last one. Further fix for the manual adding of traceable items not working correctly.
• [#18598] Fix when building a kit from a sales order line that is a batch type. [“Cannot set the value of field (.TraceAvailForDespatch) to x”]
• [#18598] Fix to correct display the required amount to be allocated for batch kit component lines when it has been part allocated. This can happen when allocating the lines, then increasing the it quantity and allocating again.

Issues Resolved

Works Order Processing

• [#17305] Fix when searching on the ‘Process Works Orders’ and ‘Complete Works Orders’ screen where a works order contains multiple finished items. [“Cannot set the value of the field (.FinishedItemCode) to …”]
• [#17917] Fix to improve the validation part of the backflush routine to ensure sub assemblies which are built to a different warehouse to the parent works order line and have been fulfilled are flagged up as not being able to backflush as they require a stock transfer to complete.
• [#17918] Fix to reinstate the ‘The book-in process is now complete’ message box that pops up at the end of the booking process.
• [#16792] Fix Project Enquiry taking a long time to load if a project is selected which is only linked to ‘suggested’ works order(s).
• [#17961] Fix to improve how we set the status of a works order. Issue when loading a works order with a large number of components and it would cause an error [“Out of memory”].
• [#17961] Fix to directly set the works order status to ‘New’ when creating a new works order unless another status has been passed in eg estimate.
• [#17973] [#17743] Fix when amending the works order due date [“Object Reference Error”].
• [#17961] Fix to filter out deleted works order lines when attempting to set the works order status otherwise incorrect status’ are set.
• [#17961] Fix for status’ not being reset when a works order is complete and then unbooked.
• [#17775] Fix when attempting to remove an area on a BOM operation. [“Object Reference Error”]
• [#17883] Fix to ensure when warehouse hierarchy is enabled that the setting ‘Show allocations screen to split allocations across multiple warehouses’ is not enabled.
• [#18071] Fix for incorrect stock history being posted when a works order with unconfirmed costs is completed.
• [#18071] Fix for incorrect rounding, when getting the full value to post the booked finished item this should remain as 5dp however when we create any journals (Overhead, Labour, Machine etc) these should remain as 2dp as per Sage rounding.
• [#17917] Improved the handling when a user cancels booking in a works order part way through ie when booking a sub assembly.
• [#17957] Fix to reinstate ‘By Products’ when they are used on a works order.
• [#17994] [#17490] Fix when using ‘Update From BOM’ and the setting ‘Group same components’ is not enabled, when a line with the same item code has been deleted from the BOM this would not update correctly. Ensure the update from BOM log correctly informs the user when a component has been deleted.
• [#17775] Fix when removing an area from an operation and saving the operation. [“Object Reference Error”]
• [#18126] Fix for the settings ‘Remove unused lines’ or ‘Zero unneeded lines’ not working correctly when booking in a works order.
• [#17615] Fixed ‘An item with the same key has already been added.’ error when adding an operation to a BOM.
• [#17699] Fix to ensure no duplicates are shown on the allocation screen when using the setting ‘Use FIFO allocation’ and ‘Show allocations screen to split across mutliple warehouses’ settings are both enabled.
• [#17699] Fix to also ensure the required quantity will not display as a negative number if ‘Allow over allocation’ setting is enabled and the works order line is over allocated on the allocation screen.
• [#18181] Fix for incorrect ‘Free Stock’ values being calculated when using warehouse hierarchy and the ability to allocate stock when there is a line with no stock but it would appear to use warehouse hierarchy.
• [#18179] Fix to correctly handle the setting ‘Use FIFO Allocation’ with warehouse hierarchy enabled.
• [#17806] Operations are only added to the works order if there is a resource or a sub contract on the operation.
• [#18226] Fix when creating a works order where the sub assembly doesn’t fit into any of the overrides for the parent or main settings. [“Object Reference Error”].
• [#17836] Minor fixes to WOP imports and settings text.
• [#17474] Fix to ensure sub assembly quantities are updated when using ‘Update from BOM’. Issue where the user could say no to updating the sub assembly quantities but then select to update them and it would appear the sub assembly quantities didn’t update.
• [#16722] The option to create an estimate from a quote line is disabled until a product and quantity are set.
• [#17986] Made sure that the question ‘The quantity will exceed the works order quantity, are you sure you want to do this?’ appears at the right time when adding a finished item to a works order.
• [#17376] Handled bulk issue items correctly on the Bulk Issue screen. User was able to allocate bulk issue items, as well as part allocate or part issue. We have now prevented this and the can now only fully issue bulk issue items from the Bulk Issue screen.
• [#17839] Fix when using the works order line import if the setting to use auto numbering is enabled then the works order number entered on the import file will be ignored and auto numbering will be used instead. This column can be used to group the works order lines that are required for the same import still.
• [#17491] Fix to improve the ‘Update from BOM information’ when a works order line has changed quantity. Issue where the line would increase and then would be reduced back to the original quantity but the ‘Update from BOM information’ would suggest no changes were made when they have been.
• [#18355] Fix for the nominal specification not store on the booking transactions.
• [#18355] Fix when adding stock on backflush and it appearing to still be an error when in fact the stock had been added correctly.
• [#18338] Fix to improve the handling of errors when creating a works order this get reported back in a much more user friendly manor.
• [#18338] Improved checking whether a warehouse exists on a stock item when the warehouse name has changed and it was set as one of the overrides on a stock item.
• [#18390] Was getting an object reference error when unbooking a finished item where no stock is available to unbook.
• [#17699] Fix to ensure the ‘IsIssued’ flag is reset on a ‘SiWorksOrderLine’ when an allocation is made. This can happen when a line gets fully issued but the setting ‘Allow over allocation’ is enabled and the user then allocates more to the line then the ‘Allocated’ column incorrectly displayed ‘Issued’.
• [#8603] Works Order Summary ‘Calculate Summary’ now correctly calculates component costs for FIFO items.
• [#17286]: Fixed booking in unconfirmed costs when there are unbooked transactions. The last booking in transaction was sometimes appearing on the works order as negative (the actual posting in stock control and stock history was correct).
• [#13511] Fix for extra suggestions being made for stock items that have not been selected if the user picks a specific stock item.
• [#18079] Fix to ensure we set the ‘BudgetUnitCost’ and ‘BudgetQuantity’ on ‘SiWorksOrderLine’ table when creating a works order. This can lead to an issue when viewing the ‘Works Order’ tab on a ‘Project’ and the ‘Component’ ‘Original Estimate Cost’ remains at 0.
• [#18084] Fix to improve the performance of loading the works order desktop list.
• [#18342] Fix for getting the correct component warehouse for a sub assembly when it is on the parent and no overrides have been set but the user has specifically selected a warehouse. This keeps the sub assembly finished item warehouse in the same warehouse.

Material Resource Planning

• [#17254] Improved the performance for the ‘spMRPPOSOPLines’ when reading the main settings ‘Include Sales Quotes’ and ‘Include Sales Proformas’ which would produce errors when running MRP. [“Database timeout”]
• [#17893] Fix Future Stock Movements screen incorrect balance after changing dates and warehouse tabs.
• [#17479]: Fixed SiMRPPOSuggestedView because it was failing to execute on databases with compatibility level of SQL Server 2008. This would happen when running update companies.
• [#18197] Fix when attempting to combine suggested stock transfers when Sage Manufactured is not installed. [“Sage.Accounting.Exceptions.ManufacturingModuleNotEnabledException. The Manufacturing module is not enabled.”]
• [#18193]: fixed issue where the fulfilment drop down was not appearing on first click on the warehouse hierarchy maintenance screen.
• [#18349]  No error is displayed when closing MRP with only distribution module enabled.
• [#11780] Fix to ensure ‘Project Templates’ are not included when running MRP.

Kitting

• [#17280] Fix when kits should be allocated when created from a sales order to handle the serial selection for traceable kit lines. Issue where the user would get an allocation error but this would then be followed by a serial selection screen.
• [#17280] Prevented kits from auto creating when saving a sales order after the user has already said no to creating a kit.

Barcoding

• [#17861] Fix Barcoding Add Stock using Backflush not setting use/sell by dates for finished items.