Upgrade Toolkit

Appendix D. Upgrading Item Tracking
138
This means that we will concentrate on creating records in table 337. The tool
demands that no reservations exist for items carrying item tracking information. For
the same reason, we will delete all order tracking entries before making the transfer of
item tracking numbers.
The place where this will cause problems is in connection with existing MTO
structures, because MTO connections are registered in reservation records.
The records in table 6500 are run through. For every record with remaining quantity to
handle, we will create and insert a surplus/prospect record in table 337. The values for
the pointer fields on the table 337 record will be retrieved via the Item Tracking No.,
looking up the related record in the database.
Transfer orders are special in this relation. In the 4.0 solution, we keep track of the
ILEs created during posting and use this relation for retrieving item tracking
information later on.
Therefore, item tracking information is retrieved from the ILE directly, looking for ILEs
with type Transfer, filtering on document no etc. For transfers we do not create table
336 records.
Table 337 records will be created for remaining quantity to handle/ship and put on the
transfer line. The quantities already shipped must be created as table 337 entries
pointing at the transfer receipt, that is the derived lines.
Procedure B - Splitting Item Ledger Entries
Run through table 6501, group by ILE entry number, and split the ILE according to the
records in table 6501. If there are n records in table 6501 within the group, we will
generate n-1 new ILEs, which will get new entry numbers based on the last existing
ILE in the database. The original ILE will be modified according to table 6501 record n.
For every group, we have to find out whether we have relations to the original ILE.
This will be the case on posted document lines, e.g. Posted Shipment. On the
posted document lines we must clear the reference field, e.g. table 111 Item Shpt.
Entry No., and instead create entries in table 6507 linking the line with all the ILEs in
the group.
At the same time we must split the value entries related to the ILE, which is new since
3.01/3.10. Records must be stored in table 6508 to save the information about which
records the VEs are split into.
To find out which specific value entries are related to a posted invoice, we will have to
use some secondary indications, as we do not have any strict relation between the
records. Instead we will have to make use of several fields on the value entry and set
up the link that way:
Item No. : Must match
Posting Date: Must match the posting date on the document header
Item Ledger Entry Type: Sales, Purchase - Depending on what type of document
we’re dealing with