Using Integration Manager with Analytical Accounting


David Meego - Click for blog homepageWhen 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.


Disclaimer: Methods 1 and 3 use an unsupported technique of calling Dexterity sanScript from Visual Basic for Applications (VBA) or VBScript. While Method 2 does not use an unsupported technique, it is important to note that none of the methods in this post are supported.


Note: The methods described in this post do not allow of the importing of Analytical Accounting data via Integration Manager. They only allow for Integration Manager to run by avoiding the usual dialogs that will open once Analytical Accounting is installed and activated.  Method 1 will not allow for any AA data; and Methods 2 and 3 only allow for default AA data.


 


Method 1: Disable Analytical Accounting from Integration Manager VBScript (not recommended)


This method disables the Analytical Accounting triggers which prevents the AA dialog boxes from opening.


Advantages



  • This method works for all transaction integrations where AA would normally cause an error.

Disadvantages



  • By disabling AA, no AA records are generated for the imported transactions. Normally AA generates records for all transactions even if there is no specific AA information. This allows AA reports to be able to report on all transactions.

Sample code


When you add the following sample code below and after an integration, you,can disable Analytical Accounting for the duration of the integration.


Before Integration Script

After IntegrationScript


 


Method 2: Automatically accept the default Analytical Accounting dialogs


Advantages




  • This method does not disable AA, so default AA records are created.

Disadvantages




  • Visual Basic for Applications (VBA) must be registered.


  • AA information must have default values for any required fields.


  • VBA code is always active, so a separate client is needed for use with Integration Manager.


  • Does not work with modified windows. As Integration Manager disables modified windows, the VBA code must be on the original window.

Sample code


The sample instructions code illustrates how a sales transaction can be entered with default Analytical Accounting information.


Add the Sales Transaction Entry window to VBA and add the following script:


Add the Analytical Accounting Sales Transaction Entry window to VBA and add the Distribution field and OK Button to VBA, then add the following scripts to the main window:


Add the following Script to both of the grid windows associated with the parent window:



 


Method 3: Automatically accept default Analytical Accounting dialogs only when running integrations


Advantages




  • This method does not disable AA, so the default AA records are created.


  • VBA code is only active when integrations are running, no separate client needed.

Disadvantages




  • Visual Basic for Applications (VBA) must be registered.


  • AA information must have default values for any required fields.



  • Does not work with modified windows. As Integration Manager disables modified windows, the VBA code must be on the original window.

Sample code


Method 3 is the same as Method 2 but it adds a IMMode variable to the Sales Transaction Entry window to specify whether the system is currently running an integration. The value of the IMMode variable is set when the Sales Transaction Entry window is opened. To read the value from Dexterity requires the use of pass through sanScript to get the value of the ‘IMIntegrationMode’ of globals system variable and store it into the table used by the Dynamic User Object Store (DUOS). This value is then read by the VBA code and the IMMode variable updated.


Add the Sales Transaction Entry window to VBA and add the following scripts:



So that the Analytical Accounting Sales Transaction Entry window can also use the IMMode variable you will need add a reference from Analytical Accounting Module to the Microsoft Dynamics GP module. To do this, on the Tools menu, click References . Add the Analytical Accounting Sales Transaction Entry window to VBA, add the Distribution field and OK Button to VBA, and then add the following scripts to the main window:



Add the following Script to both of the grid windows associated with the parent window:


Method 3 can work well when you just need to default the AA information.  If you need to actually import Analytical Accounting data you will need to look at using the eConnect objects which support AA data.


David

Comments (10)

  1. Hi David,

    I used the first method recently for setting up Integrations to Payables and Receivables however without Analytical Accounting. They just worked perfect.

    Thanks David

  2. Robert McCamon says:

    Hi David,

    SP4 for Integration Manager was recenctly released and new Destination mapping folders are now included for eConnect General Journal upload (being folders Analytics & Dimensions). Thus I now receive no errors with windows opened by IM when AA is switched on and integrated.

    However, I still have this problem for Payables Management transactions as there are no eConnect Payables Management Destinations to select.

    Do you still recommend one of the above three solutions or perhaps you know of another solution specifically for Payables Management Integration?

    Many thanks in advance,

    Robert

  3. David Musgrave says:

    Hi Robert

    None of these methods are really recommended as none are supported.  Method 3 is the best method if it can work for you.

    David

  4. David Musgrave says:

    Posting from Jivtesh Singh from About Dynamics, Development and Life

    http://www.jivtesh.com/…/integration-manager-and-analytical.html

  5. Very helpful post David. Thanks.

  6. Ian Grieve says:

    Hi David,

    I've been doing some checking and I think the answer is that it's the same.

    But I was wondering if the answer to this had changed since 2009 or if there was still this hole in how the Integration Manager adapters handle IC, MC (standard adapter) and AA (eConnect adapter) with no cross over?

    Thanks

    Ian

  7. Greg Willson [MSFT] says:

    Hi Ian,

    You are correct.  The answer to this has not changed unfortunately.  The Standard Adapters support Intercompany and MultiCurrency but not AA mappings. Conversely, the eConnect destinations for transactions have the AA mappings, but don't support Intercompany or MultiCurrency.

    Greg

    Senior Support Engineer – Dynamics GP

    Microsoft Corporation

Skip to main content