Brian, Found this post, .... BTW, after you import rebuild the SO sort files.
Using VI to Change Existing fields in Detail lines
Version 4.4 is supposed to allow update of existing line records in SO Entry. I wouldn't use the SO History Files to get your key fields. They involve links to AR History and do not necessarily match up as you might expect with the Key in SO Entry Detail.
If you are not 4.4, the other response to your post applies to all prior versions.
In 4.4, you should be able to read the Line Key from an SO detail, along with the SO Number. The line key is a 6 character, zero filled (from left), numeric field. Those two fields make up the Primary Key of the detail file, and would be the minimum you would need.
You can export the SO, Line Key, Warehouse code etc. using VI. We typically link to the tables from Access using a linked table or a pass -through query to see what the records look like in MAS.
You should be importing to the SO_SalesOrderHeader. The ""SalesOrderNo"" and ""LineKey"" fields are both available in the Data tab of the import Job Maintenance.
You need the Order Line Key or the program will not update the sales order and you might recieve error messages. Received any error messages lately?
Blank detail lines aways means you left out your record selection. Since it is possible to have up to five (5) different line type you have to tell VI how to tell the difference. If the line type will always be an inventory item then you can hard code it by selecting L1 Regular Item and changing the Relationship to Not Equal <> and leave the Value field blank. This is telling VI that as long as there is data in the line it's a regular item, well duh.
--
Thank you for all comments received, but finally I resolved my problem a couple days ago, the trick was adding in the record tab :
Description : Component Line
Pos : 7 (number of column with the item number )
Start : 1 ( start with the first Character )
Leng : 15 (max length on my field )
Relatyion : <>
Value : "" "" ( 15 spaces )