GP 10 SP5 is out – See the post by David Musgrave for download links, which has some important notes as well -
Worth pointing out specifically - “Once service pack 5 is installed, there is NO update path to GP 2010 until the release of service pack 1 for GP 2010.”
I have been awaiting this service pack for 20 odd Analytical Accounting Fixes. Somehow I had run into most of them in the last few months – they all had fairly easy workarounds, but were irritating. I was going to report one of them to Microsoft in a few hours today, till I saw the description in the Fix List.
See the complete Fix List for GP 10 SP 5 in the Service Pack 5 install guide (10.0SP5_install_guide_enus.pdf) – Page 16 onwards.
Below are some of the important AA Fixes (See complete list in the document above)-
Fix You encounter a primary key error if you have installed Analytical Accounting in your system and you attempt to post a
Purchase Order Processing shipping documents batch created in another system in which Analytical Accounting is not
installed, and if zero aaSubLedgerHdrID records exists in the AA subledger table.
Fix The data received from the distribution query is not sorted correctly.
Fix Distributions are not updated in the AAG10001 table for a multicurrency transaction if you back out a journal entry and
change the transaction date.
Fix If you back out a journal entry in the Transaction Entry window, the SEQNUMBR created for the distribution in the AAG30001
table is different from the SEQNUMBR created for the distribution in the GL20000 table. (This was the issue I was going to report today!)
Fix If you have a Sales Order Processing batch with documents having document numbers that are not in sequence and you
post the batch in summary, the distributions are not created in the AAG10001 table.
Fix Running the Transfer Transaction Data to History utility for a historical year which is not the recent closed year updates
incorrect value in the HSTYEAR field of the GL 30000 table.
Fix Analytical Accounting information is missing from the AAG2000x tables for Purchase Order Processing transactions.
Fix Duplicate distributions are created in the AAG30001 table for an invoice created in the Purchase Order Processing module if
you have deleted and inserted a tax distribution for this invoice, and then you post and void this transaction.
Fix Transaction dimension codes assigned to the account class must be displayed automatically for transactions posted without
assigning a transaction dimension code.
Fix Analytical Accounting transactions are not validated when you perform a series or master posting.
Fix Duplicate distributions are created in AAG30001, AAG30002 and AAG30003 tables if you void an invoice saved in a recurring
batch that is posted previously.
Fix Balances are not carried forward for transactions posted to a closed year when you run the Transfer Transaction Data to
Fix The balances are not brought forward for the combination of codes as entered during transaction entry.
Fix Records are incorrectly inserted in the GL20000 table if you have journal entries with the same journal entry number both in
the General Ledger history and open tables, and you run the Move Transaction Data to History utility.
Fix An SQL Server error occurs when you log on to Microsoft Dynamics GP and perform the Analytical Accounting year-end
close or if you generate reports.
Fix Incorrect Analytical Accounting assignments are displayed when you change the unit cost in the Purchasing Invoice Entry
Fix A primary key error occurs in the Analytical Adjustment Entry window when you select a journal entry posted with allocation
Fix Analytical Accounting information is not available for Bank Management transactions.
Fix Deleting line items in the Item Transaction Entry window does not remove distributions correctly from the AAG20001 table.
Fix Duplicate distributions are created in the AAG30001, AAG30002, and AAG30003 tables for Payables Management
transaction if you have deleted and inserted a tax distribution for an invoice.
Fix An error occurs when you attempt to post a Sales Order Processing batch if the batch name contains an apostrophe.
Fix An Analytical Accounting error message appears incorrectly when you attempt to post a NSF debit charge for a cash receipts
transaction, even if distribution accounts are not linked to an account class.
Fix Inactive transaction dimension codes are included when you assign codes to a budget tree.
Fix Analytical Accounting transactions are incorrectly validated in the Receivables Transaction Entry window if you select French
(Canada) as the regional option in your system settings.
Fix The originating amount is rounded off to the nearest integer if Multicurrency Management is not registered.
Fix The Analytical Accounting posting journal contains journal entries from a different batch if you post two General Ledger
Fix The primary key error occurs when you run check links for Analytical Accounting.
Fix Clicking the Redisplay button in the Payables Transaction Entry Distribution window does not regenerate the sequence
number in Analytical Accounting.
Fix A SQL Server error occurs when you post a Sales Order Processing batch containing transactions originated in the Contract
Fix The Show valid code combinations in transactions and budgets option does not work for Bank Management transactions.
Fix The Analytical Accounting information is not correctly updated in the AAG10001 table for posted cash receipt transactions if
you have marked the Create a Journal Entry per Batch option in the Posting Setup window.
Fix Incorrect GLPOSTDT in the AAG40000 table for transactions posted to historical year.
Fix If you have installed the Project Accounting module on your system, Analytical Accounting information for Receivables
Management transactions posted from a batch are not updated in General Ledger.