Dynamics Gp Deleting Historical Year In Sql Scripts: Sy40101 And Sy40100

Dynamics Gp Deleting Historical Year In Sql Scripts: Sy40101 And Sy40100

By:


There might be situations, where you have to clone of the Great Plains companies and load its Chart of Accounts into new company, installed via GP Utilities. Table SY40101 is well known in such scenarios, where you need to remove historical years, plus if you would like to reopen one or more of the recent historical years, you could simply update Hystoryr field. With one of the customers, who is running Great Plains in membership outsourcing organization with more than twenty company databases, when copying we realized that there are some nuances

We were able to remove historical years in SY40101 table in the company database without the problem. Then we ran Utilities -> Financial -> Reconcile and to our surprise this process simply wiped out the whole GL10110 table (Account Current Summary Master), where by business logic it should of rebuild the current year records in GL10110. Check Links over Account Master didnt fix the issue

We also tried to enable in Dex.ini logging into DEXSQL.log file, where we were not able to find any clue about error message

After several hours of additional research and analyzing we finally looked at SY40100 table (Period Setup), where we found the traces of historical years. And after removing historical periods in SY40100 table and rerunning Utilities -> Financials -> Reconcile the table GL10110 was repopulated

Customer actually detected the problem in FRx reporting, as FRx uses summary tables in Account master to expedite report generation. Customer reported the problem that Balance Sheet and P&L reports revealed no data. The culprit was SY40100 table, where we didnt delete historical years

Microsoft Management Reporter and the described issue. We believe that it would be also vulnerable in MMR, as it uses the same idea to base reports on GL summary tables (including GL10110 Open or Current Year Account Summary Master file)

The issue might be popular but a bit unique and it is not described in MBS Partner or Customer Source as far as we know. As you might be aware SQL Server 2008 on 64 bit Windows Server platform introduced dramatic technology improvements and changes. For example, you as SQL DBA is encouraging to use SSIS versus old-good-days technologies such as Linked Server to Text File and Open Row Set to text file

Please call us 1-866-304-3265, 1-269-605-4904. help@efaru.com We have local presence in Chicagoland, Southern California, West Michigan, Houston and Dallas areas of Texas. We serve customers USA, Canada, Mexico nationwide and internationally via web sessions and phone conferences (Skype is welcomed). Our consultants speak English, Spanish, Portuguese, Russian, Chinese


About the Author:
Andrew Karasev is Great Plains Certified Master, MVP, help@efaru.com 1-866-304-3265, 1-269-605-4904. He is also the initiator of eFaru project http://www.efaru.com and founder of Alba Spectrum information space



Article Originally Published On: http://www.articlesnatch.com


|

Loading...
Related....
Videos...

Recent Software Articles

Comments

Still can't find what you are looking for? Search for it!

Loading

Copyright 2005-2011 ArticleSnatch, LLC - All Rights Reserved.
Privacy Policy | Terms of Service.