Sage 100

V2016.1 and I am importing purchase orders and receiving. They give me a line number and I am importing this to the Purchase Order linekey. Visual Integrator gives me the field but appears to be ignoring me as it does not present it in the log and is sequencing the lines. In theory, the file is in the same order and their system assigns, 10, 20, 30, etc but I do not like trusting that this is consistent. Any thoughts on why VI is ignoring my request?

So this is a 2 step process - import the PO and then import the Receiving?

It is. My issue is the line key is available in both sources and I want to assign in the po first.

Perhaps if it used the same increment as Sage 100, it may work?

They run 10, 20, 30. The receipt may be for line 260 only. I would have to trust that all 13K records have all lines, in order, with no missing lines. I am not THAT trusting. :)

I've encountered a similar problem in the past (but I cannot recall if it was in PO) and am not sure you can set the line key when inserting new records. What I found was that VI updated the correct row if the key value was there, but if not found, the line key was ignored when inserting the new line. I assume your value is zero padded?

I am padding to the left to make it 6 characters. Actually what I do is this... mid(""000000""+Temp001$,-6,6) This way no matter the length of the key it pads properly. A little trick I learned some time ago that is easier than determining length and repeating zeros the proper number of times.

This may be a different way to skin the same cat. From the PVX manual for padding with zeroes from the left. PAD({TEMP02},7,0,""0"")

My experience with these files is that LineKey$ is completely sequential as to the order the items were entered... LineSeqNo$ is the order they are displayed in the grid to deal with lines being inserted. Since you are importing both, you should be able to rely on the increment and not have to deal with lines being inserted.... I am curious though... in versions 2015 and prior, the increment was 1 ... do I understand correctly that in 2016 the increment value has been changed to 10?

No, I am pulling information for a client that is adding a new division. They purchased the division from a company that used SAP. The old company has been handling transactions and they want those transactions moved to their Sage 100.

If it's a one time / short term situation, I'd import the PO's, then create a report to link the new data to the old, and pull in the line key for use in the receipts import (perhaps use a UDF_SAP_LINE_KEY in your report's table join).

Good Idea but boy wouldn't it be nice if I could fix the import for PO. Clear my PO import. Reload and then load my receipts without all of that linking. A man can dream... can't he?

Sage Answer...The red L.LineKey field is only used to modify existing line records, not to add new records. For example, you importing into Purchase Order Header and you realized you imported an incorrect quantity for a specific item, you can create an import with PO number, LineKey & Qty and this will correct the existing qty for that specific record.

Hi there! I know this post is old, but I'm trying to do what you were trying to do and VI isn't allowing me to set a line key for PO's so that when importing changes, I can refer back to the line key I set. Does anybody know if there's any way to override the system so that you can write the line key on a new item instead of letting Sage assign it? v2018 PU2.

------------------------------
Samantha Knigge
Eide Bailly, Inc.
------------------------------

Original Message:
Sent: 06-28-2016 14:28
From: Larry Bradford
Subject: V2016.1 and I am importing purchase orders and rec

Sage Answer...The red L.LineKey field is only used to modify existing line records, not to add new records. For example, you importing into Purchase Order Header and you realized you imported an incorrect quantity for a specific item, you can create an import with PO number, LineKey & Qty and this will correct the existing qty for that specific record.