web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Can't CREAT PROC GLReverseHistYear when upgrading to GP 2013 R2

(0) ShareShare
ReportReport
Posted on by

We have installed R2 and are trying to upgrade from the latest GP 2010 R2 release to GP 2013 R2 and we are getting an error on the Create of Procedure GLReverseHistYear.  It says that it is referring to an invalid column named "Ledger_ID" and also refers to table AAG30000.  Any one run into this?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    on at

    Hi,

    New column "Ledger_ID" is added into AAG10000, AAG30000 and AAG40000 tables, in the later version of GP and it is available in GP2013 R2, may be the upgrade process is not happened correctly, can you please check the structures of all the 3 tables listed above in SQL.

    you should find Ledger_ID column in all the 3 tables, if not found then you may have to do upgrade once again.

    Regards,

    SantoshG

  • Derek Albaugh Profile Picture
    Microsoft Employee on at

    We've also seen this error occur for customers that once had Analytical Accounting installed but decided not to install it going to Dynamics GP 2013 R2 or at an earlier version.

    What happens is that, until Analytical Accounting has been completely removed as per the KB article 915903, GP 2013 R2 Utilities still thinks it is installed, thus looking for the new columns, such as Ledger_ID in the AAG tables, which won't be there if Analytical Accounting isn't installed and being updated to the GP 2013 R2 version.

    Thank you

  • Suggested answer
    Community Member Profile Picture
    on at

    Hi,

    There is a bug logged to track this issue,

    For further details check the below link,

    community.dynamics.com/.../upgrade-error-on-the-glreversehistyear-stored-procedure-when-upgrading-to-gp-2013-r2.aspx

    below are the Workarounds which might help you,

    1.  Install Analytical Accounting if you need to retain your AA history or would like to use AA going forward.

                  Installing Analytical Accounting will then prompt you to upgrade Analytical Accounting which will update your AA tables which will then allow the Stored Procedure to get created successfully.  This will only work however if Analytical Accounting is on a version/build that has a valid upgrade path to the version/build of Microsoft Dynamics GP that you are upgrading to.

    2. Remove Analytical Accounting if you do not need to retain your AA history and do not plan on using it in GP 2013 R2.

                1.  915903 - Steps to remove Analytical Accounting from a computer that has Microsoft Dynamics GP installed

                2.  mbs.microsoft.com/.../KBDisplay.aspx

    Regards

    SantoshG

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Dan Liebl Profile Picture

Dan Liebl 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans