| Microsoft Dynamics GP, or former name Great Plains | | | | batch by changing to zero posting status. Then you |
| Software Dynamics/eEnterprise is currently available | | | | are typically trying to repost this batch again and if |
| on MS SQL Server platform only. In the past this ERP | | | | you are lucky then this is the end of the story, |
| application was available on Pervasive SQL and Ctree, | | | | however if batch fails again, the easiest way is to |
| including version for Mac (server was typically hosted | | | | unlock it again and then delete. When you delete the |
| in Windows hardware with Ctree/Faircom database). | | | | batch you should reenter transactions and post new |
| If your GP was successfully implemented for your | | | | batch as you would normally do |
| company, then from time to time you should expect | | | | 3. Complicated posting interruption. If above |
| help in data recovery and other scenarios. Let's | | | | recommendation doesn't work, you should rescue to |
| review the most typical cases: | | | | professional GP technical consultant help, or restore |
| 1. Batch Recovery. When user posts batch in GP, she | | | | database from backup if business conditions permit |
| or he should be patient and do not interrupt the | | | | 4. Security and modified reports. This is the second in |
| process, as posting has several phases and it travels | | | | row of popular tech support cases. Here is what is |
| from originating module all the way to and through | | | | going on: GP Dexterity allows you to modify existing |
| General Ledger. If you are not deploying Posting | | | | report, something like SOP blank invoice form, where |
| Server, then posting process is controlled by GP user | | | | you can add your company logo, change fields |
| workstation with partial control transfer to SQL | | | | positions, etc. If you do it on one workstation |
| Server (however it typically gets control back as the | | | | without changing default REPORTS.DIC path in |
| work is finished in the current module). This probably | | | | Dynamics.set file, then if you would try your user |
| explains why if your computer suddenly stalls due to | | | | login on another GP workstation, your modified |
| internet surfing or other activity, and posting is not | | | | report will not be found, as at another workstation |
| finished, then you will receive locked batch, which | | | | default path to the above dictionary will be |
| crashed in the middle of the way. GP interface has | | | | considered as local. And now if you try to print |
| batch recovery mechanism, but as you could expect | | | | invoice - you will get error message report not found |
| - not every batch can be recovered by it, especially | | | | 5. Pervasive SQL and Ctree data repair techniques. If |
| if posting was completed in original module and then | | | | you are on MS SQL, then you use query analyzer to |
| interrupted on the way to GL. | | | | fix your records. In the case of old DB platforms |
| 2. Batch table: SY00500. This table in company | | | | relatively simple way of doing data recovery is by |
| database if where you as SQL programmer begin the | | | | deploying Microsoft Access and creating linked tables |
| recovery process. The first step is to unlock the | | | | there. |