Manufacturing

Issues Resolved

Works Order Processing

• [#11077] Fix when running update companies and the user would get multiple errors,
  – “Procedure SiconWorksOrderProjectCostsView, Invalid column name ‘PhaseDescription'”
  – “Procedure SiconWorksOrderProjectCostsView, Invalid column name ‘StageDescription'”
  – “Procedure SiconWorksOrderProjectCostsView, Invalid column name ‘SubStageDescription'”
  – “Procedure SiconWorksOrderProjectCostsView, Invalid column name ‘CommitValue'”
  – “Procedure SiconWorksOrderProjectCostsView, Invalid column name ‘ActualValue'”.
• [#11872] Fix to correctly calculate the SiWorksOrerLine estimate hours, minutes and seconds for an operation line when it has a fixed quantity. Issue where the duration would have just remained the same no matter how many we are building.
• [#13321] Fix when using the ‘Update From BOM’ routine and the setting ‘Group like components when creating works orders’ enabled and it would ungroup the existing group lines.
• [#16411] Fix to ensure the default projects are set against the works order if they have not been set. If these are not set this can lead to further issues when trying to manually add a preallocation between the works order and sales order if both are ‘N/A’.
• [#16420] [#16272] Fix to ensure the PO line description when generating a PO for a sub contract or adding to an existing PO is consistent.
• [#16822] Prevent error when processing operation multiselect for machine operations when amending operations. [“Object Reference Error”]
• [#16823] Improve ‘Multi Select’ feature to retain machine row details when returning from the multiselect popup. Updated the button to now use a hyperlink.
• [#16833] Fix to ensure we multiple the cost of an operation line by the manning level.
• [#16878] Fix to now store an ‘OriginalWarehouse’ field on ‘SiWorksOrderLine’ so that if a line is allocated from a different warehouse via warehouse hierarchy then when it is unallocated the works order line returns to the original warehouse.
• [#17424] Made sure that we use the area on the operation for the works order first before looking at areas on the BOM item.
• [#17464] Fix when deleting a finished item from a works order [“Unable to update the object (Sicon.Sage200.WorksOrder.Objects.SIWorksOrderFinishedItem, ), as the object has been deleted”]
• [#17417] Fix to no longer default the finished item warehouse or component warehouse when creating a works order and the user selects the BOM.
• [#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”].

Material Resource Planning

• Added validation when filtering by the ‘from’ and ‘to’ dates on the ‘future stock movements’ screen to ensure the ‘to’ date is not before the ‘from’ date.
• [#17299] Combined both suggested stock transfers and direct allocation transfers onto the same ‘Suggested Stock Transfer’ tab so the user can view all the transfers.
• [#17322] Fix when running rescheduling for dates in the past to ensure to use the earliest possible date when attempting to rescheduling them.
• [#17329] Applied auto select/search on the ‘Follow up’ drop down on the suggested purchase orders grid/tab, so that the user can type a couple of characters and then the value will be auto set
• [#17719] Fix for demand for teams not showing on ‘Rough Cut’.
• [#17736] Fix to ensure the ‘Projects’ column on ‘Suggested Works Orders’ is not visible when projects is not enabled in works orders.
• [#15673] Fix to also only create one transfer with all the items going to the same ‘In, Out Warehouse’ on the same ‘Despatch Date’ when create the final stock transfer form a suggestion.

Change in Functionality

Material Resource Planning

• [#17479] Improved performance of the suggested purchase orders list in MRP.
• [#9533] Updated the ‘Future Stock Movements’ screen so that it now splits the tabs per warehouse. This is to ensure the warehouse detail values are accurate for what the user is viewing.