Dynamics GP Series Posting Issue

I recently had a sticky issue with a client's posting in a particular company. Sometimes and for some users the batches would post through the GL; other times they would not. After checking the obvious setup for series posting and making sure everything is set to post through the GL, I found a couple of KB articles that are relevant. Article 1 didn't solve our issue, so I dug deeper and found the second article.

One note on using the 'ALL' option for the series posting - it isn't very self-explanatory but when you click apply, it rolls down the options selected to the postings for that series and then resets to the default options. By default, it posts at the transaction level and not the batch level. In general, I would skip the 'ALL' option and look at the individual types of batches for the series.

Article 1: There are a few General Ledger windows that the user will need to have access to in order to post through the GL successfully from the subsidiary module. Access to these windows can be given at Setup >> System >> Security. Choose your User ID, Company, Product of eEnterprise or Dynamics, Type of Windows and the Series of Financial. Give the user access to the following: Batch ID, Batch Entry, and GL Open Files. Setting security on these windows only for GL is the minimum security for a user to be able to post series through the GL.

Article 2: Note: Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs.
SYMPTOMS: Consider the following scenario. You post transactions from a submodule. The posting is set up to post to and to post through General Ledger in Microsoft Dynamics GP. In this scenario, General Ledger is not updated by the transactions. Note: The submodule batches are available in batch entry. Additionally, the batches can be posted, and they will update General Ledger.

CAUSE: This problem occurs if the Posting Definition Master table (SY00500) or the procedures that are associated with this table are damaged or corrupted.

RESOLUTION: To resolve this problem, re-create the Posting Definition Master table. To do this, follow these steps.

1. Make sure that no other users are logged on to Microsoft Dynamics GP.
2. Post all the batches that you can in Microsoft Dynamics GP.
3. In Microsoft Dynamics GP 9.0 and in earlier versions, point to Maintenance on the File menu, and then click SQL.
4. In the Database list, click the company database, and then click Posting Definitions Master.
5. Click to select the following check boxes: Drop Table, Create Table, Drop Auto Procedure, Create Auto Procedure
6. Click Process. Note: The Posting Definition Master table contains information about all unposted batches in the company except for Payroll. After you drop and then re-create the Posting Definition Master files, you cannot see any one of your batches in the company until you complete the remaining steps.
7. Perform the check links process for the files in the corresponding modules. To run the check links process, in Microsoft Dynamics GP 9.0 and in earlier versions, point to Maintenance on the File menu, and then click Check Links.
8. Click the appropriate module file, and then click OK. Use the following list to determine the module files:
   
   -- Payables Management: Payables Transaction Logical in the Purchasing series Note: If you use Multicurrency for Payables Management, you must run the check links process on the Payables Transaction History Logical file before you run the check links process on the Payables Transaction Logical file.
   -- Purchase Order Processing: Purchasing Transaction Logical in the Purchasing series
   -- Receivables Management: Receivables Open Transaction in the Sales series
   -- Invoicing: Invoice Work File in the Sales series
   -- Sales Order Processing: Sales Work File in the Sales series
   -- Inventory: Inventory Transaction Work file in the Inventory series
   -- Bill of Materials: Bill of Materials Transactions file in the Inventory series
9. If you use the Project series, you must run the check links process for this module based on the transaction types that are used in the existing batches. To do this, in Microsoft Dynamics GP 9.0 and in earlier versions, point to Maintenance on the File menu, and then click PA Check Links. 
10. 
    
    Click the appropriate file, and then click OK. Use the following list to determine the transaction files:
    

    -- Timesheet Batches: PA Timesheet Transactions

    -- Asset Log Batches: PA Asset Log Transactions

    -- Expense Log Batches: PA Expense Log Transactions

    -- Inventory Transfer Batches: PA Inventory Transfer Transactions

    -- Purchase Order Batches: PA Purchase Order Transactions

    -- Vendor Invoice Batches: PA Vendor Invoice Transactions

    -- Employee Expense Batches: PA Employee Expense Transactions

    -- Billing Batches: PA Billing Time & Materials Transactions
11. If any batches exist in General Ledger, reconcile the batches in the Reconcile Financial Information window. To do this, in Microsoft Dynamics GP 9.0 and in earlier versions, point to Utilities on the Tools menu, point to Financial, and then click Reconcile.
12. If transactions exist in the Quick Journal Entry window, open the transactions in the Quick Journal Entry window, and then save the transactions again.
13. If you have batches in Inventory, you must click to select the Post To GL check box for these batches, and then repost the batches to General Ledger.

 Notes:

• Batches will be available in the company after you run the check links process and then reconcile the batches.
• This process will set any recurring batches to single use. You must change the frequency of any recurring batches in the Batch Entry window before you post the batch. If you post to General Ledger from another module by using the batch date as the posting date, the posting date for batches in all modules are set to the user date. If this date is incorrect, you must change the date in the Batch Entry window.