Reprocessing and Utilities
This folder holds the recovery tools: the scripts and utilities that rebuild quantities, costs, ledger balances and debt ages for a database whose numbers are already wrong. They are not maintenance, they are not routine, and none of them is a first response.
Read this before you run anything here
One document behaving oddly is never a reason to rebuild a database. A single document that has no accounting or inventory effect is fixed from the Business Requests screen — find its request, read why it failed, fix the cause, reprocess that one request.
The tools on these pages empty and rebuild whole tables. On a large database a full rebuild runs for days, the system is unusable while it runs, and there is no undo. Before you start any of them: take a backup, agree the downtime with the customer, and stop the application server where the page tells you to.
Where to start, by symptom
| What you are seeing | Go to |
|---|---|
| One document has no ledger entry or no stock effect | Business Requests — not this folder |
| Item balances or costs are wrong across many documents | Reprocessing Quantity, Cost, and Stock Ages |
| Account balances or customer/supplier ageing are wrong | Ledger and Debt Ages Reprocessing |
| You suspect something is wrong but cannot yet name it | Queries to Check for (and Fix) Cost And Qty Problems |
| The problem is inside one module | The module's utilities — inventory, manufacturing, fixed assets or real estate, below |
| A known list of records must be recommitted, deleted, re-replicated or exported | Batch Utilities That Work From a List File |
| Ownership, rental status, employee state, vacation balances, car status or asset values disagree with the documents | Rebuilding Module System Entries |
| Pending approvals show finished or deleted records, or an old summary | Approval Repair Utilities |
| A site is out of step with head office | Replication Utilities |
| Everything is correct but painfully slow | Suggest Indexes for Large Detail Tables |
The order to work in
- Read before you write. Start with the diagnostic queries. They report; they change nothing, and they tell you how wide the problem really is.
- Fix the narrowest thing that explains it. A failed business request, one document, one dimension.
- Rebuild one area — quantities and cost, or the ledger, or one module's tables — only once you know that area is the one at fault.
- A full rebuild is last, with a backup, an agreed window and the server stopped.
If step 1 does not explain the symptom, that is the moment to escalate rather than to widen the blast radius.
Launcher links on these pages
Many tools on these pages are started from a link rather than a menu. Each one is shown as a small form: an input for each of the tool's parameters, the finished link below them, and two buttons beside it — copy, which copies the link exactly as shown, and show server URL (the eye icon), which opens a box where you type the address of the customer's server. The link is rebuilt as you type, and the address you enter is remembered by your browser for every launcher link on the site, so you set it once per server rather than once per page.