Importing serial number to the batch Item Traking Lines

Flashtn

Good morning all,

I use Item Journal to enter items in inventory. When there are a lot of serial number, I must enter them one by one. It's very hard!!!

My question is : how can I import serial numbers of an item to the batch Item Traking Lines from EXCEL file ? Can I use the table Excel Buffer (ID 370) ?

Thank you in advance

i4tost

Use Barcode readers. Manually enter serial numbers - to strong

lakshmivalluru

why not a dataport? :!:

Asallai

1)

In Excel:
Save As ... *.csv
(this type of text file is contains separators. The operator default value is ";", but this is depend on the operating system (for example Windows XP at the Regional Settings --> Numbers (List separator))

2)

Next, create a dataport, because it is more easier than other way. Or if you can import from Excel directly, it's better) :!:

Can you setup the properties in a dataport module?

Flashtn

Yes, I can do dataport, but I want to know if i import data directley in this table (ID 370) or there are conditions ?

Asallai

Ther is one the most directly import:
for exapmle if the excel structure is the same as like tha table try select all in excel, copy, and paste to tha table

Some table it is works

But the dataport is the safeiest way

aryaputhra

you need to update the reservation entry table, item ledger entry and item tables whilst doing the dataport.

alternatively if you can provice your email id and i will email an object to import the file.

Flashtn

The Item Ledger Entry table, Reservation Table and Item table are updated when I posted (validate) the lines in the form of Item Journal. Thus, there is no problem in this side.

Flashtn

The Item Ledger Entry table, Reservation Table and Item table are updated when I posted (validate) the lines in the form of Item Journal. Thus, there is no problem in this side.

aryaputhra

there might be some other generic conditions that you need check

for example:

1) does the serial no. already exist in navision item ledger entry (ideally if you are importing that suggests a lot of s/numbers and it would be good if the client establishes duplicates before the dataport is imported, coz once it's imported its difficult to establish which one is the duplicate).

2) An exception report of the numbers that are not imported due any integrity issues.

awarn

Just structure your dataport a little differently and you wont need to check for duplicate numbers.

Set the autoupdate and autosave to false on the dataport dataitem.

Set the fieldlist

On the afterimportrecord trigger have 2 journal records

lrJnl.init;
lrjnl.reset;
lrjnl.setcurrentkey("journal template name", "journal batch name", "line no.");
lrjnl.setrange("journal template name", ___________);
lrjnl.setrange("journal batch name", _____________);
if lrjnl.find('+') then
lrjnl2."line no." := lrjnl."line no." + 10000
else
lrjnl2."line no." := 10000;

then set the rest of the values for variable lrjnl2, using VALIDATES for any fields that lookup, then

lrjnl2.insert;


at the very end of the dataport put a commit;



Then you import to the journal not worrying about overwriting records or primary keys. You should NEVER write directly to posted (ledger) tables, this has amazing potential for disaster. Import to the journal, post manually; let the posting routine do it's job and put the data in the correct place.

-a