EDI 850 - EDI Unit Price

KTEDI

I have an 850 that I am importing (Nav 4.0, using Lanham EDI); I can get every line on the PO1 to import onto the sales order with the exception of the PO1-04 (Unit Price); the field is not populating because the TP does not send the PO1-03 (UOM) I have tried mapping the PO1-03 to the Item Sales UOM, I have tried a fixed value, but the only way I can get the PO1-04 to populate the Unit Price on the Sales Order is to put a UOM in the PO1-03.

Any suggestions would be greatly appreciated!

Alex_Chow

The unit price should populate irregardless of whether you put in a EDI UOM or not. I would check some modifications on your code, or look at the Lanham site to see if there are bugs associated with the version you're using.

Savatage

The addon added new fields to the sales line.
We have ours mapped to Field#14000353 "EDI Unit Price"
Once imported field#14000354 EDI "Price Discrepancy" tells us if the price on the EDI file matches our systems Unit price. If not a check mark appears on all lines with different prices.

It seems logical this way because you don't want Imported order from some customer dictating what price you should sell an item at. this way you know where its different and then you can ok it or not.

We import alot of orders and the easiest way to find them, if you have a lot of items, is to add a new function to one of your menu buttons at the bottom of the sales order.
-New Menu Item "Show All Price Discrepancies"
Action: RunObject
RunObject: Form Sales Lines
RunFormView: SORTING(Document Type,Document No.,Line No.) ORDER(Ascending) WHERE(Document Type=FILTER(Order),EDI Price Discrepancy=FILTER(Yes))

Anyway back to your question - see the pic of how we have it setup

Alex_Chow

Some of the clients wants to use the unit price from the EDI file instead of their own price file.

Savatage

Ah I see, I still like seeing what their price is in a seperate field and if i'm ok with any difference then update the sale price to their price. As you said it shouldn't stop a price from appearing because of the UOM - I would assume even with a bad setup it would default to the items sale Unit Of Measure :-k

Perhaps it's something simple like not setting the correct datatype - the pic above should be a helpful guideline