Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
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.
Are you on Dynamics GP 2015 RTM or Dynamics GP 2015 R2? Build number 14.00.524 is RTM. This issue has not been addressed until R2, which is build 14.00.0725. You will need to upgrade to at least R2 if you don't want to use the provided workaround.
I am successfully using the stored proc with four UDFs suggested by Harsha Prakash. However, the post reports, "UPDATE: This issue has been resolved in Microsoft Dynamics GP 2015 R2." I am on GP 2015 R2, 14.00.0524 (RTM), and still require this workaround. Has this been fixed? Will it be?
Hi Harsha, thanks for posting your solution. I just used your solution of passing the values into the USERDEFND properties and assigning the values in the Pre procedure and it worked great.
We are seeing the same issue in GP 2015. Has it not been fixed?
Business Applications communities