Dynamics Community Forum Thread Details

eConnect: Decimal Places Passed in on Unit Cost Does Not Match Setup

Hello:

In using the eConnect tool to import purchasing receipts for Microsoft Dynamics GP, I'm getting the following error on the Line Item node (taPopRcptLineItemInsert):

Decimal Places Passed in on Unit Cost Does Not Match Setup.

This error makes absolutely, positively, without a shadow of a doubt no flippin’ sense whatsoever.

True, the decimal placement of the Unit Cost field of some of the records in the database goes beyond 2. But, for a similar import for purchase orders, I eliminated the error by using the following calculation for the Unit Cost field:

return fn.ROUND (UNITCOST, 2 ).

But, for the receivings map and for a record whose Unit Cost is 6.72, it is throwing this error – whether I use this calculation or not. And, I have tried resolving this a million ways to Sunday.

Here’s what I don’t get. The Unit Cost, in this example, actually does not go beyond 2 decimal places. It is, simply, a figure of 6.72. And, the GP Purchase Order Processing Setup window is set to 2 for Currency Decimal placement of noninventoried items.

Any ideas?

John

Categories:

Development / Customization / SDK

Other

Distribution

Hello,

Thank you for your details. This error is specifically for Non-Inventoried items will check the following.

1. First we check to see if you are registered for Multicurrency. eConnect will do this by looking at the IV00105 (inventory MC table) and the CM00100 (Checkbook maintenance table) to see if you have any currency IDs that are not blank. You must have a record in both of these with a valid currency or else eConnect will assume you do not have MC registered.

2. It will then look at the POP40100 if Multicurrency is not installed for the number of decimal places, or if MC is installed (based on step 1) then it will check the POP40600 table for the matching currency id of your integration to get the number of decimal places for your non-inventoried items.

This tells eConnect how many decimal places you will be using. Keep in mind the setup tables hold the decimal place plus 1. so 3 = 2 for example.

3. We now take your unit cost, and round it in SQL based on your number of decimals. and see if the unit cost still matches your origin unit cost. If it does not, then you will receive the message that you are seeing.

if (round(@I_vUNITCOST, @DECPLCURItem) <> (@I_vUNITCOST))

If your setups are correct in GP, then I am assuming that they either have MC registered but do not have a checkbook and item currencies set up yet. OR they do not have MC registered but imported a checkbook or item with currency information so the tables in step 1 create a false positive.

I hope this helps, and please let me know if you have any questions.

Thanks!

Isaac Olson

Microsoft Support

Quick Links

Leaderboard