Purchasing Distribution incorrect when matching with eConnect

(0) Share

Report

Posted on by Community Member

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:

taPopRcptLineTaxInsert
taPopEnterMatchInvLine
1. AUTOCOST = 0/Manual
2. AutoInvoice = 0/Manual
3. EXTDCOST = Interface input is different from the PO
4. UNITCOST = Interface input is different from the PO (a new Unit Cost is calculated before input)
5. QTYINVCD = Interface input is the same as the PO

taPopEnterMatchInvHdr
1. AUTOCOST = 0/Manual
2. CreateDist = 1/Automatic

Note that I am NOT using taPopDistribution.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (6)

Answers (1)

Verified answer

Isaac Olson Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No
sandipdjadhav 18,319 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report
Copy link

Link copied!
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:

Get the the next Purchase Receipt Number from GP

eConnect taPopEnterMatchInvLine

AutoCost = 0/manual

AutoInvoice = 0/manual

econnect taPopEnterMatchInvHdr

UsingHeaderLevelTaxes = 1/true (even though we have line taxes)

CreateDist = 0/manual

Custom post-processor

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.

Was this reply helpful? Yes No
Suggested answer

Isaac Olson Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

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.

Thanks,

Isaac Olson

Microsoft Support

Was this reply helpful? Yes No
Suggested answer

Terry R Heley Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Wanted to create awareness that we added a new section to our documentation of published eConnect procedures that have changed, and issues customer may run into. The taPOPCreateDistributions is one of them on the list.

Please review this area and download the procedure and test your situation further.

Developer Tools - Dynamics GP | Microsoft Learn

Thanks

Terry Heley
Microsoft

Was this reply helpful? Yes No