Integration Manager and Analytical Accounting

If you in the trenches with Analytical Accounting and considering the use of Integration Manager, check out these two posts

Using Integration Manager with Analytical Accounting by David Musgrave

When you use Integration Manager on a system with Analytical Accounting (AA) installed, integrations often fail because Analytical Accounting will open windows which are unhandled by Integration Manager. However, there are time when you still want to use Integration Manager to import transactions where the Analytical Accounting information is left blank. This post provides three methods of how to make Integration Manager work when Analytical Accounting is installed.

http://blogs.msdn.com/b/developingfordynamicsgp/archive/2009/09/09/using-integration-manager-with-analytical-accounting.aspx

Integration Manager: Integrating journal entries with Analytical Accounting Information by Mariano Gomez

If you are one of the fervourous Integration Manager fans out there and have had to work on integrating journal entries with Analytical Accounting information, you may know this is only possible with the eConnect Adapter, not the Standard Adapter.

http://dynamicsgpblogster.blogspot.com/2010/11/integration-manager-integrating-journal.html

Dynamics GP SDT Essential Series 2 – Transfer AA Dimensions and Codes from Test to Production

The Support Debugging Tool has a fantastic XML Table Export and Import features. This can be used to achieve fantastic things like –

• David Musgrave showed – how to transfer Security Tasks and Roles between Systems. This is useful when you are migrating security from Test to Production.
• Mariano Gomez used the XML Table import as one of the ways of Transferring Extender customizations from one company database to another

Another use that we recently tested this feature was in migrating the Analytical Accounting Dimensions and Codes from Test to Production. Often people test out the AA Codes and Dimensions in a test environment, and when they are happy with what they want they want to set it up in Production. SDT allows you to transfer this in a snap, instead of manually setting things up again in Production.

As a bonus, the article also covers the ability of running SQL scripts from inside GP using the SQL Execute option of Support Debugging Tool.

Read the complete article here - Dynamics GP SDT Essential Series 2 – Transfer AA Dimensions and Codes from Test to Production

AA Duplicate Error and a ‘House Moment’ ?

A few weeks back we got the error below when adding a dimension in Analytical Accounting.  The user was trying to add the dimension “Customer” in their test environment.

Cannot insert duplicate key row in object ‘dbo.AAG00600’ with unique index ‘AK2AAG00600’

We tried the steps in the KB Article 897280 and a related helpful article from Daoud, but they didn’t really help. We couldn’t add the “Customer” dimension.

However, when we added “Cust” it worked! We took a screenshot, and since everything else was working smoothly, thought about researching about it later .

I sent the screenshot to Rubal, and she had her “house moment”, and immediately showed me the values in the Table AAG00600. She said it seems like whenever we add a dimension called “Employee” or “Customer” is causes a conflict with the keys in the AAG00600 aaTreeMstr table.

We verified this with the other values in the aaTreeMstr table.

So these 6 dimension Names are not allowed. Try it out in your new GP install- if you try and add the dimension “Employee”, it will give you that error. I have tested this in a GP 10 and a GP 2010 install, let me know if you get this error as well.

Related errors and resolution -

Error message when you try to post Analytical Accounting transactions in Microsoft Dynamics GP: "Cannot insert duplicate key in object"

Article ID : 897280

https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?WTNTZSMNWUKNTMMYKKQRRUZVRPSSXNSNKVMMVVRXTSXXQNNVZKKSSQUZOZXOKPKP&wa=wsignin1.0

http://mohdaoud.blogspot.com/2009/08/analytical-accounting-error-cannot.html

GP 10 SP 5 is out (with lots of AA Fixes)

GP 10 SP5 is out – See the post by David Musgrave for download links, which has some important notes as well -

Microsoft Dynamics GP 10.0 Service Pack 5

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.

Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 10.0 (PartnerSource)

Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 10.0 (CustomerSource)

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
History utility.
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
window.
Fix A primary key error occurs in the Analytical Adjustment Entry window when you select a journal entry posted with allocation
accounts.
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
batches simultaneously.
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
Administration module.
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.

Analytical Accounting Alias Feature

Aliases for Dimension codes was a cool new feature that was added in GP 10 Feature pack. (You can create a grouping of Analytical Accounting Transaction Dimension codes as defaults when entering analytical information on a transaction similar to the account alias in General Ledger. A default combination of transaction dimension codes will help increase speed and accuracy for data entry and enable users to create more than a single set of defaults for the transaction dimensions.)

The world Before AA Alias – You had to manually select the dimension codes.

In some cases you could set Dimension codes as  defaults, but that had a very limited use.

 

Enter AA Alias

Open the window from Cards >> Financial >> Analytical Accounting >> Alias

Set the defaults.

 

The Magical World with AA Alias!

When you open the AA Window, the cursor is already placed on the Alias field. All you have to do is enter the Alias, and it would fill all the dimension codes for you. Excuse my dramatization, but I am sure anybody who has spent more than an hour entering transactions with AA codes would share my enthusiasm!

While writing this post I searched the custom GP Blog Search Engine at www.gpwindow.com and found another great post about this feature by CVAKumar. So I saved some time I would have spent in discussing how -“You can import alias from a Microsoft Excel spreadsheet that has been set up in the required format.” Check out his post !

Note – You need to be on GP 10 SP2 or higher to use this feature.

Related :

See articles about GL Alias Feature below

Weekly Review: Account Alias : http://msdynamicsgp.blogspot.com/2010/04/weekly-review-account-alias.html

Account Alias-Speed up your GL Transaction Entry http://sandipdjadhav.blogspot.com/2010/01/account-alias-speed-up-your-gl.html

Automatic User Access for new AA Codes

If you are using Analytical Accounting, you probably know about this pain point – You have to go to “Setup > Company >Analytical Accounting >
User Access” and assign security to new codes before they can be used. Most people have customizations setup by their partners to resolve this.

In GP 2010 - Security access to use a transaction dimension code is granted automatically to the user who created the code during transaction entry. So that’s a great step in the right direction.

CVA Kumar has a couple of posts which should server as good reference – He has a SQL Script to provide access to Transaction Dimension Codes to Users and a Macro to provide access to Transaction Dimension Codes to Users