Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
General Procedure<br />
D.2 Upgrading Item Tracking from NA 3.01/3.10 to Navision 4.0<br />
TableID Name Update Action Procedure<br />
6666 Return Receipt Tracking<br />
Line<br />
Table 6521...6666 have exactly the same structure and are used for carrying item<br />
tracking information for different tables.<br />
Table 6502 is used for setup information.<br />
Table 6500 carries actual lot and serial numbers related to the specific ONE by an<br />
Item Tracking No.<br />
Table 6501 is used for information regarding posted items (item ledger entries). The<br />
relation is created by field 18, Item Ledger Entry No.<br />
Table 6503 is used solely for saving the last item tracking number.<br />
Step 0 - Cleaning the 3.01/3.10 database<br />
Run a check function that will check whether the assumptions for the upgrade are<br />
fulfilled. The check function might also itself make some initial clean-up of reservations<br />
and tracking.<br />
Step 1 - Preparing the 3.01/3.10 database<br />
The item tracking information is stored in upgrade tables that are carried to the new<br />
database.<br />
The data in the original tables is then deleted.<br />
Replaced by relation to T32 via 6507 D<br />
Step 2 - Creating the 4.0 database<br />
Procedures are run that will use the data in the upgrade tables for splitting ILEs and<br />
value entries and put data in table 336, 337, 6507 and 6508.<br />
When the update is completed, the upgrade data is deleted.<br />
The specific Item Tracking objects that have been removed from the 4.0 solution are<br />
deleted from the database in case they are still there in step 2.<br />
Procedure A - Transferring Item Tracking Lines<br />
The data that was placed in table 6500, Item Tracking Line, must be transferred to<br />
table 337 as far as items not handled are concerned, and table 336 for items already<br />
handled - that is, sales or purchase lines that have been partially posted.<br />
The data that should be placed in table 336 is available more directly through the<br />
relation to the split ILE. Hence we will not use the content of table 6500 for this<br />
purpose – that data is redundant.<br />
137