You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Inconsistent Reservations<br />
6.2 Upgrading Company-Specific Data<br />
Navision 2.00-2.60 A reservation is inconsistent if, for example, a sales order reserves an item across<br />
locations. Furthermore, entries where the reservation status is not Open are also<br />
considered inconsistent.<br />
Navision 2.00-2.60<br />
and Navision<br />
Manufacturing 2.60<br />
Navision 2.00-2.60<br />
and Navision<br />
Manufacturing 2.60<br />
Inconsistent entries are deleted during the upgrade and you will have to create them<br />
again manually in accordance with the new reservation system. Note that in Navision<br />
4.0 you should use transfer orders rather than reserve items across locations.<br />
To run the Inconsistent Reservations report:<br />
· Select report 104025, Inconsistent Reservations, and click Run (ALT+R).<br />
Item Tracking<br />
Note<br />
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .<br />
You do not need to do this task if the existing standard key, Item No., Lot No., Prod.<br />
Order No., Serial No. has been enabled in the customer database.<br />
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .<br />
To avoid performance problems in the item tracking upgrade from Navision Financials<br />
2.00, 2.01, 2.60 and Navision Manufacturing 2.60, we recommend creating these 2<br />
new keys in table 32, Item Ledger Entry:<br />
Item No., Serial No.<br />
Item No., Lot No.<br />
Cleanup of Date Compressed Item Ledger Entries<br />
You may experience problems with the invoiced quantity in upgraded item ledger<br />
entries that were originally date compressed. The redistribution of this invoiced<br />
quantity may not be correct for every customer due to the different options for the way<br />
date compression can be performed. As a result, you may need to perform some<br />
cleanup of date compressed item ledger entries before you perform the upgrade and<br />
the upgraded entries must be carefully tested after the upgrade.<br />
Note<br />
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .<br />
Depending upon the retain fields that were used in the date compression, it may be<br />
necessary to adjust codeunit 104049, <strong>Upgrade</strong> 4.00 Step 2 Value, before you<br />
perform the upgrade. You should comment out some of the filters set in codeunit<br />
104049 that follow the comment:<br />
// The following filters can be set according to retain fields used<br />
// in the date compression batch job if different retain options are<br />
// set in date compression calls, filters need to be removed.<br />
53
Change language