Share
ReportI am integrating PO Receipts using the eConnect nodes (these PO receipts are not associated with a PO and all the items are flagged as non-inventoried). I noticed that when I integrate a PO receipt with a unit cost that extends out to two decimal places the extended cost gets rounded, either up or down. If I manually enter, into the GP interface, the same PO Receipt line the extended cost does not get rounded. So I decided to add the extended cost parameter to my SQL Stored Procedure so that Extended Cost is passed in, instead of getting calculated for me. Once I made that change I started getting the error "Decimal Places passed in on EXTDCOST does not match setup". The company does not use multi-currency. I have verified that in Purchase Order Setup non-inventoried items are two decimal places for quantity and cost. I am not really sure where else to look for the setup on the number of decimal places. Once strange piece of information, when I manually added the PO Receipt line, that did not round the extended cost, I did it on the same PO Receipt that was integrated via eConnect. When I compared the two lines in SQL they were identical with the exception of the extended cost. I was expecting to see some differences between the two lines, especially when it concerned the number of decimal places. Any help would be greatly appreciated.
*This post is locked for comments
All responses (
Answers (
2
