Dynamics GP Posting Recovery, what to do if your Batch Posting Crashed

Historically Great Plains Dynamics, or how it is currently known – Microsoft Dynamics GP, this Corporate ERP application was open to data level custom programming and reporting.  One of the tradeoffs is not complete transaction roll back.  More specifically, Great Plains Dexterity uses cursor style access and data manipulation technique and it is procedural programming shell (Integrated Development Environment), where it is really complex to include and trigger begin, commit or rollback SQL transaction (plus honor the fact, that Dexterity initially provided database abstraction level for several DB platforms, such as Btrieve, Ctree and MS SQL Server, where not every DB platform supports transaction rollback).  Having said that, we should give you some feedback on old Great Plains Dynamics support – about 25% of the calls from Great Plains customers, were associated with batch posting limbos.  Let’s review your options and recovery scenarios:

1. Before you post the batch.  As Dynamics GP is mid-market Corporate ERP application, it is recommended to review the batch prior to posting.  Open Batch Window and print Batch Edit List report (you can print to the screen, as everyone wants to be green nowadays) – look at it on the subject of error messages.  Typical messages are about missing posting account – if this is your case, please open the referenced document and add account manually (and then probably review with your Dynamics GP consultant posting accounts default settings)

2. Batch Recovery logic.  If batch posting crashed, next time your login GP you will get a prompt to go to Batch Recovery.  Here, it is important to review the status.  For example is the status is “Edit Required”, don’t try to post the batch again and again, it will not go through, as you will have to print batch edit list and correct errors on the document level (again, these are typically missing GL distribution accounts, I think you would agree, being accountant, that computer accounting cannot make decision on which account to use for specific missing credit or debit account).  If the status is something else, hopefully you are lucky, and batch recovery will unlock the batch for the following posting.  However, there are situations, when the batch was partially posted and it is impossible to force it all the way through via Batch Recovery window

3. Good Practice to avoid Batch Posting Recovery.  Batch Posting logic has huge number of computer code, written in Dynamics GP Dexterity, and these codes are played, when you do batch level, module or master level posting.  One of the best advises is to let your computer to finish the posting job and get out to talk to your friends over the cell phone or take a cup of coffee in the kitchen and discuss your progress with your controller.  We really discourage you from switching computer to something like Internet surfing or playing games.  Computers are not absolutely reliable in multitasking and there might be the scenario, when your computer game crashes and this will lead to background Dynamics GP Batch posting process to crash together

4. If Batch Was Partially Posted and Crashed.  Here you need to appeal to professional Dynamics GP Technical Consultant, who should analyze posting progress and where the traces of the posting might be either completely deleted or recovered.  If you are SQL DBA, please think about the recovery procedure this way.  Let’s say, SQL programmer forgot to frame its SQL Insert and update set of commands into Transaction envelope.  If update and insert logic involves several tables in the sequence, then you as DBA are playing the role of the database doctor, looking at the first table in the row, then into the second one to find out where the set of commands failed and stopped

5. Some observations of batch posting crashes and their causes.  In our opinion native Dynamics GP business logic is very reliable and Microsoft Business Solutions releases Service Packs on the regular base to address the issues, reported by customers or its own beta testers.  However, in your case you might decide to order custom Dynamics GP extensions, typically in Microsoft Dexterity or eConnect, where beta testing and Quality assurance could be done only on one customer – your own company (plus QA and beta testing is something requiring extra budget and you may decide to skip this “unnecessary” expense).  If your custom module works and doesn’t produce errors in posting down the road – we share your happiness, otherwise – you’ve got what you paid for

6. To request further support, please call us 1-866-528-0577, help@albaspectrum.com We need to discuss your cards in order to recommend you the best solutions, which is not contingent to our preferences.  We serve you USA/Canada nationwide via remote support (web sessions and phone/skype conferences).  Local service is available in Western Michigan, Chicagoland, Southern California (LA, Orange County, San Diego), Houston area of the state of Texas

Leave a Reply