Notifications
Announcements
I’m using eConnect to do invoice matching. When there is a Purchase Price Variance, the amount for the Purchasing Distribution is incorrect. Where should I look for the issue?
I’m using these eConnect objects:
Note that I am NOT using taPopDistribution.
Hello,
There is an issue with the taPOPCreateDistributions Stored Procedure which throws off the the PURCH amount (most of the time we see the total correct PURCH amount multiplied by the number of lines on the transaction). Because eConnect Stored Procedures are encrypted it is not something that you can just update without a copy of the unencrypted version. If you have access to the unencrypted version of this stored procedure from a version prior to GP 2016, you could put that into place to resolve the issue. Otherwise I would recommend opening a support case which we would not charge due to this being a quality issue and we can get you a fix to implement.
Thanks,
Isaac Olson
Microsoft Support
Hey Isaac,
Thank you for your reply and for this information! I don't have access to GP 2016 and so I will open a support case with Microsoft as you suggest.
Hello ,
I am facing the same issue in GP2018 R2 enviornment. eConnect throwing wrong Purchase Amount for LC invoice Match.
Are you able to resolve the issue?Thanks much
Sandip
Hi Sandip,
No, I wasn’t able to resolve the issue – I had to do a (big) workaround instead.
I used TIBCO Scribe to create an interface to do our three-way match of Invoices, Purchase Orders, and Shipping Receipts.
The Scribe interface consists of these main steps:
I did a lot of experimenting with the values for AutoCost, UsingHeaderLevelTaxes, and CreateDist. I ended up writing a custom post-process (step 4) to calculate and verify the taxes and the distributions. It was time-consuming and not pretty, but it works and we’ve been in Production for about a year now (Dynamics GP 2018 R2).
Not the answer you wanted, I’m sure. Good luck to you.
Hello Sandip,
I would be my suggestion as a starting point, to open a case with us at Microsoft first as we have workaround stored procedures for this that has worked for most customers. Since this is considered a quality issue on our end, the case would not be charged to you once we provide the workaround. If you have too complex of a scenario and need to do your own customization like Connexus above, then at least you would be able to try our workaround without charge first before going that route.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
André Arnaud de Cal... 663 Super User 2026 Season 1
Abhilash Warrier 289 Super User 2026 Season 1
Martin Dráb 232 Most Valuable Professional
