Software Engineer
asked on
Microsoft eConnect: Unit Price Calculation Does Not Match Out to Extended Price
Hello:
The end user has a unique Microsoft Dynamics GP Sales Order Processing requirement where the Unit Price is to be $0.00, and the Extended Price is to match the Extended Price column of the source file for an eConnect import.
So, I'm getting that famous error, "Unit Price calculation does not match out to Extended Price."
I have tried setting the two defaults for default price and default extended pricing to FALSE or TRUE or vice versa to no avail.
It is very strange that you can manually enter 0 for Unit Price and whatever for Extended Price in GP. But, eConnect does not allow for this.
Also, the items are noninventoried.
Any ideas?
Thanks! Much appreciated!
Software Engineer
The end user has a unique Microsoft Dynamics GP Sales Order Processing requirement where the Unit Price is to be $0.00, and the Extended Price is to match the Extended Price column of the source file for an eConnect import.
So, I'm getting that famous error, "Unit Price calculation does not match out to Extended Price."
I have tried setting the two defaults for default price and default extended pricing to FALSE or TRUE or vice versa to no avail.
It is very strange that you can manually enter 0 for Unit Price and whatever for Extended Price in GP. But, eConnect does not allow for this.
Also, the items are noninventoried.
Any ideas?
Thanks! Much appreciated!
Software Engineer
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, Steve! Your referenced article led me to create my fix for this issue, as follows:
In eConnect, I programmed the following calculated field called “NEWUNITPRICE” for the line item’s Unit Price mapping: return fn.ROUND((_EXTPRICE/_UNITQ TY), 5). This, basically, divides the source file’s Extended Price by Quantity and sets the number of decimal places for the resulting figure at 5.
Secondly, in the test company, I configured SOP Setup to allow for 5 currency decimal places. The combination of these two steps allowed for importing of all three source files without error.
I took these steps because the end user does not care about how the Unit Price looks. as long as the Extended Price imports successfully.
Thanks, again, for your help!
Software Engineer
In eConnect, I programmed the following calculated field called “NEWUNITPRICE” for the line item’s Unit Price mapping: return fn.ROUND((_EXTPRICE/_UNITQ
Secondly, in the test company, I configured SOP Setup to allow for 5 currency decimal places. The combination of these two steps allowed for importing of all three source files without error.
I took these steps because the end user does not care about how the Unit Price looks. as long as the Extended Price imports successfully.
Thanks, again, for your help!
Software Engineer
ASKER
Thank you!
Can you post the full eConnect error response with XML snippet?
Thanks,
Steve