As a follow up to our previous blog post where we listed all the HotFixes that were addressed in Sage 300 ERP 2012 Product Update 1, we bring you a list of HotFixes that have been resolved in Sage 300 ERP 2012 Product Update 2.
HotFix 210-1005828 – “Sage 300 ERP UI Container has stopped working” message after changing paper destination
Product Update 2 resolves the following error that appeared when printing any report in Sage 300 ERP 2012:
"Sage 300 ERP UI Container has stopped working"
After the error appears it terminates the closes the Sage 300 ERP program.
HotFix 210-1005701 – Print to File or Export Report does not default to Disk File or save the last option selected
If you recall, people were having this issue if the Print Destination was set to File, the program does not default to Disk File like prior versions.
After upgrading to Sage 300 ERP 2012, the user must select Disk File each time as the program does not remember what was used previously. This issue should not occur once you’ve installed Product Update 2.
HotFix 210-1005814 – Separated Values Export Options form no longer available when exporting report to CSV in Sage 300 ERP 2012
Product Update 2 resolved the Separated Values Export Options form issue. This issue is when this form is no longer available when exporting reports to CSV. This causes the data to include extra header records in the export file and prevents users that have 3rd Party applications that they need to integrate with via CSV.
HotFix 210-1005534 – Slow Performance when opening the Reconcile Statement Screen
Once you install Product Update 2, you will probably not encounter the long delay in displaying the Reconcile Statements screen after clicking the Reconcile Statement icon.
HotFix 210-1005859 – T5018 form layout has changed from 3 to 2 per page
This only applies to Canadian customers. Product Update 2 updated the the Statement of Contract Payments (T5018) form layout, which was changed from 3 per page to 2 per page.
HotFix 210-1004150 – “document(s) were found in the specified range that failed processing” error occurs when running Create Retainage Batch
Fixed a problem that could occur when using the Create Retainage Batch screen to create a retainage batch, which could prevent some transactions from being processed in the batch. This problem occurred only for transactions that were originally created in Order Entry, and that have outstanding retainage but no retention period specified.
HotFix 210-1005421 – Reversing a negative cost shipment doubles the original actual cost
Once you install Product Update 2, it will fix the problem that could cause the cost of an inventory item to be updated incorrectly if the item had a negative cost. This problem occurred if you posted an O/E shipment that included an item with a negative cost, and you later reduced the quantity of the item on the shipment or related invoice. The incorrect cost information appeared on O/E, I/C, and P/O screens.
Check back later for Part 2 as we list more HotFixes that were addressed in Product Update 2 as well as a link of the complete list of all the program fixes.
