You cannot access a batch that is held in Posting, Receiving, Busy, Marked, Locked, or Edited status.
Note If you use a Microsoft SQL or MSDE database,click the following article number to view the article in the Microsoft Knowledge Base:
850289 A batch is held in the Posting, Receiving, Busy, Marked, Locked, or Edited status in Microsoft Dynamics GP
Read the following information COMPLETELY before proceeding with the steps.
Follow these steps to get a batch back to the Available Status if restoring a backup is not an option.Following these steps will not ensure that your data will not be damaged.
1. Be sure no other users areloggedintoGreat Plains.
2. Makea backup.
3. Post all batches that you can in Great Plains.
4. Rename the Batch Activity Files (SY00800.*) located in the Dynamics/System directory on the server.
NoteThere is an Automated Solutionavailable to perform this task. For more information about how to release a batch that you cannot post, visit the Automated Solutions Page at the following link:
https://mbs.microsoft.com/customersource/support/selfsupport/automatedsolutions5. Try to edit the batch within Great Plains. If you cannot edit the batch, and you do not have a backup to restore, continue with the following steps.
NoteThis process will set any recurring batches to single use. Try to pull up the recurring batches in the Receivables Batch Entry window to see what is selected for the Frequency Field. After the batches are recreated in Steps 7 and 8, you must change the frequency of any recurring batches from the Batch Entry window before you post the batch. If you are posting to General Ledger from another module using the batch date as the posting date (Setup | Posting | Posting), the posting date for batches in all modules will have been set to the user date. If this is incorrect, you must change this date in the Batch Entry window.
NoteAfter you complete these steps, you should print reports in the affected module to verify that the information is correct. If Bank Reconciliation is being used, check to see if Bank Reconciliation has been updated by any of the transactions you were trying to post. Verify if General Ledger has been updated.
6. Rename the Posting Definition Master file (SY00500.*) located in the Company directory where your data has been stored. The Posting Definition Master file contains information about allunposted batches in the company except Payroll. After you rename the Posting Definition Master files, you will not be able to see any of your batches in the company until you are finished with these steps.
Note If you use aFairCom Server, verify that all users are out of Great Plains.Bring theFairCom Server down (consult your System Administrator if you have any questions on this step), and then rename the SY00500.dat and SY00500.idx files located in your Company directory.
NoteIf your batch is a Multicurrency Computer Check batch, you must also rename the MC00500.* file(s) in the Company directory.
7. Depending on which modules you have with existing batches, you need to follow these steps:
NoteIf you have an interruption when printing or posting Multicurrency Payables Checks,delete the Check batch and reselect your Vouchers for payment. If you do not delete the batch, the Check may be printed with incorrect currencies.
NoteIf you use Multicurrency for Payables Management, you should run Check Links onthe Payables Transaction History Logical file before you run Check Links onthe Payables Transaction Logical file.
Run Check Links onthe following files (File | Maintenance | Check Links):
A. Payables Management: Payables Transaction Logical (under the Purchasing Series).
B. Purchase Order Processing: Purchasing Transaction Logical (under the Purchasing Series).
C. Receivables Management: Receivables Open Transaction (under the Sales Series).
D. Invoicing: Invoice Work File (under the Sales Series).
E. Sales Order Processing: Sales Work File (under the Sales Series).
F. Inventory: Inventory Transaction Work file (under the Inventory Series).
G. Bill of Materials: Bill of Materials Transactions file (under the Inventory Series).
NoteIf you use Project Series, Check Links must alsobe run on this module depending on what transaction types have existing batches. Run Check Links onthe following files (File | Maintenance| PS Checklinks):
A. Timesheet Batches: PS Timesheet Transactions
B. Asset Log Batches: PS Asset Log Transactions
C. Expense Log Batches: PS Expense Log Transactions
D. Inventory Transfer Batches: PS Inventory Transfer Transactions
E. Purchase Order Batches: PS Purchase Order Transactions
F. Vendor Invoice Batches: PS Vendor Invoice Transactions
G. Employee Expense Batches: PS Employee Expense Transactions
H. Billing Batches: PS Billing Time & Materials Transactions
8. If any batches exist in General Ledger, use the Reconcile Financial Information window (Utilities | Financial | Reconcile) to reconcile batches. If transactions exist in Quick Journal Entry, bring those transactions up in the Quick Journal Entry window and save each one of them again.
Note If any Payables Computer Check Batches exist,delete them, run Check Links on Payables Transaction Logical and Payables History Logical files,and then reselect Vouchers for payment.Apply to records may becomedamaged or duplicates may occur if these procedures are not followed.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
852064 Payables Management check run was interrupted
When you run Check Links and reconcile batches, your batches are available in the Company again. You will now be able to access the batch and edit it, if necessary. You must determine if transactions were already posted or if they must be posted at this point.
NoteIf you have batches in Inventory, you must remark the Post To GL on those batches if you want them to post to General Ledger.
NoteIf you are using Intellisol's Advanced Purchase Order Processing,go through the following steps to bring your Advanced POP transactions back:
A. Select Purchase Order Entry.
B. Use the VCR buttons to pull up the first transaction and then save it to a new batch.
C. You MUST pull up each and every transaction and save it to a new batch.
D. Go into series posting or master posting and print an edit list of each batch (select the batch, go to file, and then Print) to verify that all transactions are included in the batch.
Keywords: batch status, batch stuck, batch posting, c-tree, pervasive sql
This article was TechKnowledge Document ID:7213
The issue that is described in the Summary section does not apply to Microsoft Dynamics GP 10.0.