Microsoft Dynamics GP: Analytical Accounting and Integration Manager

One of the downfalls of Dynamics GP Analytical Accounting, is the ability to use existing Integrations through integration manager. There are many articles that contain information on how to update the integration so that AA does not interfere, however, until recently, I have not been able to accomplish this.

One difference is that the integration manager node needs to be the eConnect destination – not the standard destination. You will see that the fields are available for the Transaction Dimension, Transaction Dimension Code, and Dimension Code Amount. When mapping to these fields, however, errors are often encountered.

I was able to narrow down one of the causes of the error message I received. It had to do with the Journal Entry field being set to Use Default. eConnect requires a value to be supplied for the journal entry.

In order to resolve, there are two options. Note the next Journal entry number and populate the data within the source file of the integration, and change the Rule for the Journal Entry Number to Use the Source File. The other option is to add a couple scripts to the Integration. One script will be added to the Before Document event script within the Integration manager properties. The other is to set the field to retrieve that number.

Please find the scripts below – Now you can finally take advantage of uploading Journal Entries with Analytical Accounting Information!

Before Integration Script:

Const adCmdStoredProc = 4
Const adParamInput = 1
Const adParamOutput = 2
Const adParamInputOutput = 3
Const adInteger = 3
Const adVarchar = 200
Const adBoolean = 11
Const adChar = 129
Const adDate = 7
Const adNumeric = 131


Dim SqlStmt
Dim objConnection, objCommand, NextJournal


Set objConnection = CreateObject("ADODB.Connection")
Set objCommand = CreateObject("ADODB.Command")



objConnection.Open _
   "Provider= SQLOLEDB;Server=MGB001\GP11;Database=TWO; Trusted_Connection=yes;"



With objCommand
.ActiveConnection = objConnection
.CommandType = adCmdStoredProc
.CommandText = "glGetNextJEWrapper" 'our wrapper stored proc

.Parameters.Append .CreateParameter ("@IO_iOUTJournalEntry", adInteger, adParamOutput, 4)
.Parameters.Append .CreateParameter ("@O_iErrorState", adInteger, adParamOutput, 4)

.Execute
NextJournal = objCommand.Parameters("@IO_iOUTJournalEntry").Value
End With

SetVariable "gblJounal", NextJournal

Set objCommand = Nothing
Set objConnection = Nothing



Journal Entry field Script:
CurrentField.Value = GetVariable("gblJournal")

 

This article was written by Kaydee Baker, Practice Manager for Tridea Partners. Tridea is a leading Microsoft Dynamics provider.

 

 

 

 

Analytical Accounting with Dynamics GP

How many of you out there are using Analytical Accounting with Dynamics GP?  It is a great tool that allows you to flag distribution amounts to codes, without having to increase the length of your General Ledger Accounts.  Through many times of implementing this module, we at Tridea have found that a few custom reports can make everyone’s lives easier.  Because it is an additional module, outside of the standard GP modules, Smartlists and Edit Lists are limited and can be made more efficient.

Using SQL Server Reporting Services to create custom reports, users can access their Analytical accounting data and balances quickly and accurately.  Furthermore, SSRS reporting can be used to create edit lists that will combine standard Edit List reports from GP with the Analytical accounting information.  Custom buttons can be added to the batch entry window that will trigger the SQL report to generate, pulling only transactions contained in the batch selected.  Not only does this consolidate the information needed for editing and reviewing batches, but it will also reduce the amount of paper allowing for a greener approach to accounting!

This article was written by Kaydee Baker, Dynamics GP Application Consultant for Tridea Partners. Tridea is a leading Microsoft Dynamics provider serving CA, AZ, UT, CO, New England and surrounding regions.

Balance Sheet Reporting Without Closing YTD in Dynamics GP

It’s almost that time again. Soon it will be time to complete another year-end close in GP. Since GP will only allow adjusting entries to the SINGLE LAST closed year in GP, it can sometimes be a scary process for users. Due to ongoing audits or other various factors, it may be inevitable that adjustments will be needed for more than just one historical year. Without closing a year, the amounts for balance sheet accounts will not roll over as beginning balances for the next year. For those instances, here is a little trick that will allow for accurate balance sheet reporting, without having to complete the official year-end process in GP.

Below is an example of a Management Reporter column definition. In this example, column B is mapped to pull YTD data from the last month of the last fiscal year. Column C is mapped to pull YTD information for the current fiscal year. Both columns B and C are configured as “non-printing” columns. Finally, column D is a calculation that adds columns B and C. Voila! Accurate balances without closing the year in GP.

 

balance sheet reporting