2015 Microsoft Dynamics GP MVP

Richard, I will not be at Convergence, I have added a product suggestion:

connect.microsoft.com/.../1134159

I look forward to feedback from the development team.

Phil, you can start by dropping a product suggestion here.

connect.microsoft.com/dynamicssuggestions

Will you be at Convergence next month? There will be members of the development team there and I will make sure I bring up.

Richard, congrats on MVP, now to put you to task....

I have run into a bug in taGLTransactionHeaderInsert sproc for eConnect.  The bug exists in both GP2010 and also GP2013 versions of eConnect.

Scenario:  I am using eConnect to submit GL Transactions:

1. The currency of the company is USD

2. The currency of the transaction is CNY

3. The Amounts of in balance in CNY

4. The amounts are out of balance by $00.1 when converted to USD.

5. The additional record is created in GL10001 with an ACCTTYPE = 0.

(This is exactly the same as when manually entering the transaction through GUI)

6. I get an error due to credits and debits out of balance in eConnect, no error when using GUI.

Root Cause:

In taGLTransactionHeaderInsert, you will find the following lines of code:

SELECT @TRXTOTAL1 = sum(CRDTAMNT)

FROM GL10001 a(NOLOCK)

WHERE a.BACHNUMB = @I_vBACHNUMB

AND a.JRNENTRY = @I_vJRNENTRY

AND a.ACCTTYPE IN (

1

, 3

)

SELECT @TRXTOTAL1 = isnull(@TRXTOTAL1, 0)

SELECT @TRXTOTAL2 = sum(DEBITAMT)

FROM GL10001 a(NOLOCK)

WHERE a.BACHNUMB = @I_vBACHNUMB

AND a.JRNENTRY = @I_vJRNENTRY

AND a.ACCTTYPE IN (

1

, 3

)

SELECT @TRXTOTAL2 = isnull(@TRXTOTAL2, 0)

IF (@TRXTOTAL1 <> @TRXTOTAL2)

BEGIN

SELECT @O_iErrorState = 944

EXEC @iStatus = taUpdateString @O_iErrorState

, @oErrString

, @oErrString OUTPUT

, @O_oErrorState OUTPUT

RETURN (@O_iErrorState)

END

As you will see, as it is filtering ACCTTYPE  in (1,3), it will never balance if a rounding transaction is added with ACCTTYPE of zero.

I have manually modified the proc in DEV to include ACCTTYPE of zero, which work as expected.  However, I would like to have a patch/fix issued by Microsoft to ensure that it does not break in the future.

What is the process for doing so?  And is this something you can facilitate?

Regards Phil

GP 2015 is compatible with SQL 2012 or SQL 2014. So if you are on SQL 2012 you are all set.

mbs.microsoft.com/.../MDGP2015_System_Requirements

Are your servers imaged or are they physical boxes. When given the choice, I will always go with fresh installations. Most upgrades to SQL go along without a hitch but their is always that one that just will not work. Make sure you have backups and keep me posted.

I am about to install Dynamics GP 2015. Even though we already have Dynamics GP 2013 SP2 already implemented. Now my concern is if I am going upgrade is that means the SQL needs to be upgraded to SQL 2014 since this is the requirement for Dynamics GP 2015. Or what's the best approach please?