Fixes and closed periods
Some one-click fixes change posted data: removing the open copy of a paid vendor or customer document that's also in history, clearing sub-penny open amounts, setting a document's amount remaining to what its applications leave (or to its full amount when nothing is applied and an application was removed), and rebuilding an open year's period summaries from the posted detail. They can never change a record dated in a period you've closed. They also only work once your SQL Server administrator has run usp_grant_amount_fixes, so it's your decision to allow them. The other fixes don't change amounts or posted data, so this doesn't affect them.
One exception: removing the history copy of an application that GP also keeps, identical, in its open table. Only the exact duplicate goes and the open copy stays, so no balance changes in any period or year, and a closed year doesn't stop it. It still needs usp_grant_amount_fixes, because the history table holds posted data.
What the guard does
A fix that changes amounts or posted data has to say which date each record is posted in and which GP series it belongs to. Before it runs, and again before it's undone, Ledger Doctor looks each date up in GP's fiscal periods:
- In a closed period: the fix is refused. The preview names the periods, like "2026 period 3". Reopen them in GP (Microsoft Dynamics GP > Tools > Setup > Company > Fiscal Periods), apply the fix, then close them again so the balances roll forward.
- In a closed year (one GP's year-end close has moved to history): the fix is refused, and Ledger Doctor won't change it at all. Take it to your GP partner.
- Outside GP's fiscal periods: the fix is refused until the fiscal year is set up in GP.
A period summary has no date of its own, so it's looked up by its fiscal year and period instead.
When any of these applies, the preview says so and Apply fix stays unavailable. Nothing is changed.
Permission is separate
The SQL access setup gives Ledger Doctor covers only the tables today's fixes clean up. A fix that changes amounts also needs write access to its tables, which a SQL Server sysadmin grants on purpose by running EXEC LedgerDoctor.dbo.usp_grant_amount_fixes. Setup never grants it.