I recently had a query from a client about Reporting Ledgers; to answer the query I enabled them in one of my demo VMs. Afterwards, I was faced with a choice; redeploy the sample company or switch off reporting ledgers.
The former was going to take more time than I wanted to spend, but the latter is not possible through the Microsoft Dynamics GP front-end.
I took a quick peek at the tables and found there was only two tables involved in the core product and one in Fixed Asset Management (depending on the installation) and would be easy to update.
/* Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (https://www.azurecurve.co.uk) This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int). */ UPDATE GL40000 -- General Ledger Setup (GL40000) SET Allow_Reporting_Ledgers = 0 ,UseLedgersForAcctBalance= 0 GO DELETE FROM GL40001 -- Reporting Ledger Setup (GL40001) GO IF (EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA = 'dbo' AND TABLE_NAME = 'FA49900')) UPDATE FA49900 -- Company Setup (FA49900) SET FA_Allow_Reporting_Ledge = 0 GO
If you’ve entered transactions with reporting ledgers switched on, I would advise against running the above script and, if you do run it, make sure you have a good backup first.