I wish to push back gently at Bert's response. What happened was that the user called me in panic after they pushed the button and I had to puzzle through the SQL query to fix the data, and it was quite a puzzle. Whether the document reconcile procedure would have fixed it I do not know, because I did not try it, the data pattern suggested that it would not. It was a complex cash application affecting dozens and dozens of invoices and credit memos and payments.
My advice for anyone who tries to unapply a complex transaction and the report shows the unapply will not balance, is for the user to restore the production database to a test database and then tinker with it. The code for the Great Plains core modules is as perfect as code can be perfect, but what we can never control is procedures that do not run to completion yielding partial or duplicate data in the work and history files.I also want to emphasize that these situations are EXTREMELY RARE, I only encountered this situation once in the dozen years that GP was live in our company.
If you've found this thread useful, dive deeper into User Group community content by role