Sage 100

New Hot fix in V440 PU4 for Inventory Maintenance ""A record with an invalid posting date was encountered in an Item Transaction table. The recalculation cannot continue"" in Recalculate Item History, and I/M Trial Balance is incorrect after migrating data if transactions were purged in Sage MAS 90 and 200

DETAILS : ""A record with an invalid posting date was encountered in an Item Transaction table. The recalculation cannot continue"" in Recalculate Item History, and Inventory Trial Balance is incorrect after migrating data if inventory transactions were purged Entry Type: Program Issue Product: Sage ERP MAS 90, Sage ERP MAS 200 Application: Inventory Management Version Reported: 4.40.0.3 Status: Resolved with Hot Fix IM4018-T (Sage ERP MAS 90 and 200 4.40.0.00 4.40.0.04) Subject: The following issues occur after migrating data to Sage ERP MAS 90 and 200 4.40 if inventory transactions have been purged and the fiscal year no longer exists in GL Fiscal Year Maintenance. Inventory Trial Balance is incorrect ""A record with an invalid posting date was encountered in an Item Transaction table. The recalculation cannot continue"" occurs in Recalculate Item History Steps to Duplicate: In the earlier version, purge inventory transactions. expand Inventory Management and Reports. Double-click Inventory Trial Balance. Print the report. Start Sage MAS 90 or 200 4.40 and migrate the data.. Print the Inventory Trial Balance in version 4.40. Note that the beginning balance does not match the earlier version. Expand Inventory Management and Utilities. Double-click Recalculate Item History. ""A record with an invalid posting date was encountered in an Item Transaction table. The recalculation cannot continue"" occurs. Expected Behavior: Beginning balances should migrate correctly even if inventory transactions are purged.

Upgrade to 4.40 creates undated transactions Date: 2/23/2011 Product Line: MAS 90 and MAS 200 Application: Inventory Management Application Level: 4.40.0-4.40.0.4 Number: IM4018-T Symptom When inventory transactions have been purged and the fiscal year no longer exists in GL Fiscal Year Maintenance, upgrading to 4.40 may create transactions without a transaction date. This can cause unexpected results on reports and utilities. Resolution The following program will correct the problem. GL_FiscalYear_bus.pvc Version 1.2 To install the correction, run the Download file below. Download IM4018_t.exe http://support.sagesoftwareonline.com/mas/query/index.cfm?action=tipdetail&tip_id=1896

Wow. I submitted this case to them back on 8/9/10. After about a month, the solution was to reinitialize IM_ItemTransactionRecalc.m4t and then recalc inventory history. Then last month, the same client reported the same issue with a different company in MAS. Luckily, I didn't have to reinvent the wheel for the solution. Now it all makes sense. Client had been a Hightower client until last year and had been very self sufficient. Client had been running MAS for nearly 15 years and their setup options were all over the place. Just had a two hour session a couple weeks back reviewing some best practices with them. They had their history retention year field set very low. Since they had many years in GL fiscal year maintenance without any detail account transactions, they deleted the year in fiscal maintenance. Glad to see fix only took six months. I guess it will be about four more months before the issue with the back order flag getting flipped during a conversion will be fixed. I'll mark my calendar...............