Disabling Multiple Ledgers functionality in Microsoft Dynamics GP 2010...after the fact

Let's face it! Like many things in life, configuration decisions are revisited even after going live (rightfully so!) with your system. What was viewed and considered a requirement a few months aback and worked during User Acceptance Testing turns out to be something the business no longer needs today, due to changes in direction, or changes in business conditions.

Just recently, I came across a request for disabling the new reporting ledgers functionality in Microsoft Dynamics GP 2010. While this implementation was not live, this issue was clearly affecting the consulting teams ability to move forward.

The following script should disable the reporting ledgers function:

-- Created by Mariano Gomez, MVP
-- This code is licensed under the Creative Commons 
-- Attribution-NonCommercial-ShareAlike 2.5 Generic license.

UPDATE GL40000 SET Allow_Reporting_Ledgers = 0, UseLedgersForAcctBalance = 0;
DELETE FROM GL40001;

Once the script is executed, go back to the General Ledger Setup window. You will notice that a BASE ledger is created by default, but also notice that the Allow flag is unchecked.


General Ledger Setup
Click the Ok button to continue.

Now, if you open the GL Transaction Entry screen, you will notice that the Ledger ID field is no longer present.

Transaction Entry
Hope you found this post useful.

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Jivtesh Singh said…
Mariano,

Wanted to turn off Ledgers in the test environment today, and searched KB/PS, but didnt find anything. As usual you were there to save the day!

Thanks
March 5, 2012 at 9:42 PM
Anonymous said…
Mariano, I used your script to disable the reporting ledger and now the when using the Finanial-Summary and History Summary inquiries no results are returned. If I access the summary and history windows from the Account Maintenance window the summary and history summary do return results. Any ideas what would cause this? Thank you, Scott
December 15, 2012 at 10:58 AM
Post a Comment

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

Image
In this video, learn to enable Power Apps Application Monitoring with Azure Application Insights.  The following topics are covered in this video:  ( 0:00 ) - Intro  ( 0:36 ) - What is Azure Application Insights  ( 1:32 ) - The timesheet app  ( 2:12 ) - Creating an Application Insight for the timesheet application  ( 3:55 ) - Identify and copy the application instrumentation key  ( 4:09 ) - Enabling the timesheet application with the instrumentation key  ( 5:32 ) - Working with Application Insights  ( 8:06 ) - Outro For additional information on Azure Application Insights, please follow these resources: Microsoft Docs - What is Azure Application Insights? here Adam Marczak - Azure for Everyone: Azure Application Insights Tutorial, here To check out my YouTube channel visit: https://youtube.com/user/mgomezb1 LIKE AND SUBSCRIBE!!! Until next post! MG.- Mariano Gomez, MVP
Read more

eConnect Integration Service for Microsoft Dynamics GP 2010

Image
One of the biggest improvements in eConnect 2010 is the addition of the new eConnect Integration Service . The eConnect installer now creates a new Windows Service application named eConnect for Microsoft Dynamics GP 2010 integration Service . The eConnect Integration Service is a Windows Communication Foundation (WCF) service that replaces the (very unstable) eConnect COM+ object available in previous versions of eConnect. The eConnect Integration Service supports the operations of the eConnect .NET assemblies, the BizTalk adapter, and MSMQ interfaces. In addition, you can use the service directly from an application that adds a service reference to the eConnect Integration Service. If you add a service reference, you do not need to add the Microsoft.Dynamics.GP.eConnect assembly and namespace to your development project. To add the eConnect Integration Service to an application, you must first add a service reference to the Visual Studio project for that application. To add a servi
Read more

Troubleshooting the Microsoft Dynamics GP 2013 Web Client - Part 3

Image
Part 3 - Resolving Microsoft Dynamics GP 2013 Web Client Functional Issues Last week, Part 2 of this series dealt with resolving Web Client implementation issues. The key to remember is any exception condition prior to the Microsoft Dynamics GP login window is treated as an implementation issue and as noted back in Part 2, there are two major processes - steps, if you will - in compiling information that will lead to resolving Web Client exceptions. Just like with the implementation issues, you must compile information related to all application exceptions. Let's see what type of information can be compiled: If the problem involves product functionality, it's always a good idea to record the steps to reproduce the problem. It's also possible that the issues are UI related, i.e., a window does not display correctly (though these issues are less frequent, but certainly possible). Printing and data export issues. In this case, you will want to determine whether th
Read more