Can not assign Item Tracking Code if there's ledger entries.

koalado

Our Navision have been runing for half a year. Now we decide to enable "Item Tracking". but since there are already historic ledger entries for 95% items, system doesn't allow us to assign a "Item Tracking Code" to item card.
OK then I add the "Item Tracking Code" via SQL instruction in SQL Query Analyzer. We went throught each module and it seems that everything OK. All related entries are recorded correctly with the tracking information (Lot No.) from the date I made the change.
So, my question is, is there any risk I haven't noticed? Since MBS courseware says for this circumstance, we have to recreate new Item and assign "Lot No.". Gosh, we have more than 5000 items. recreate?..... ](*,)
Thanks in advance

kriki

-If you do this kind of things manually, there is always the risk you forget something (same goes for changing/adding/deleting Item Ledger Entries and lots of other tables)
-If you do it with SQL, you run an extra risk because SQL can write things in tables that are not good for Navision (e.g. put a lowercase character in a code-field).

ara3n

I believe Navision should fix data, especially with lower case data in code fields, and not just complain that the data is corrupted. It's a simple fix.

kriki

ara3n wrote:

I believe Navision should fix data, especially with lower case data in code fields, and not just complain that the data is corrupted. It's a simple fix.

Simple BUT when the wrong data is in the DB, the sorting can be completely wrong and create more problems. I think that is the reason why Navision did it the way they did. So they force us to put the data correctly in it.

kine

Yes, you can have problems when you will try to work with the entries which were open in time you added the tracking code. Because when you are working with lot nos. or ser. nos. there are created extra records in some tables and this records will not exist for old entries. The data are now inconsistent and this can be source of problems in the future...