UPDATE: This issue has been resolved in Microsoft Dynamics GP 2015 R2. To download the R2 patch, you can go to the following:
Microsoft Dynamics GP 2015 Service Pack, Hotfix and Compliance Update Page - Download the R2 Patch!!
Customers - Click HERE Partners - Click HERE
Check out the FIX LIST.
I wanted to address an error we’ve had some reports of lately. When eConnect integrations using the taPMDistribution stored procedure are run the following error is encountered:
Error Number = 11991 Stored Procedure= Error Description = Error Codes were not found in table DYNAMICS..taErrorCode. Please insure that the table taErrorCode is up to update.
The cause for this issue is that the upgrade to Microsoft Dynamics GP 2013 R2 added 4 new parameters (@I_vPAYTYPE, @I_vCAMCBKID, @I_vCHAMCBID, @I_vCARDNAME) to the taPMDistribution stored procedure. Unfortunately, that change was not fully reflected in all needed locations:
To be clear, this will only affect those customers on GP 2013 R2. Any build up to, but not include R2 (12.00.1745) is not affected by this issue.
The only real workaround at this point is to use the taPMDistributionPre procedure to populate those columns with valid values so that the errors do not occur. These are the definitions and valid values you would need to populate:
Right now this issue has been targeted to be addressed in the upcoming Dynamics GP 2015 release.
Let us know if you have any questions/comments on this.
How to send @I_vPAYTYPE parmeter from my .net Application. I am not getting paytype property to assign value. Please help.
Thanks for your question Harsha,
At this point the only workaround that I've seen for this issue is to populate the necessary parameters in the taPMDistributionPre stored procedure. Since the API is not aware of these new parameters I'm not aware of a way that you could send them from your .NET application.
Thank you very much for reply Lucas.
Can you please tell me how to populate necessary parameters in stored procedure. In my stored procedure I already have these 4 parameters in stored procedure taPMDistributionPre
@I_vPAYTYPE smallint output, @I_vCAMCBKID char(15) output, @I_vCHAMCBID char(15) output, @I_vCARDNAME char(15) output,
When I previously looking into this I started by just adding the following after SELECT @O_iErrorState = 0 and before RETURN ( @O_iErrorState ) in the PRE proc:
SET @I_vPAYTYPE = 1
This means the Payment Type is set to Cash Amount. I then re-ran my previously failing XML. The result, as expected, was Error Code 11992, which corresponds to /*Cash Amount CheckBook Id is Missing*//*@I_vPAYTYPE @I_vCAMCBKID*/.
I updated the PRE proc to also set @I_vCAMCBKID to a valid value:
SET @I_vCAMCBKID = 'FLEX BENEFITS'
If you cho0se a PAYTYPE of 2 (Check) you will need to specify @I_vCHAMCBID.
If you choose a PAYTYPE of 3 (Credit card) you will need to specify @I_vCARDNAME
This allowed the transaction to be inserted for me. The problem is that it has essentially been hard-coded to a specific payment type and checkbook ID. If this is viable for your situation then it would appears to be a valid workaround for you.
If you need multiple PAYTYPE values for the PM transactions that you're inserting you may need to play around with the PRE proc to make them work.