Hello Community - This is the situation
Our customer has not been using inventory inside NAV, they were managing it using a third party software. They never cared about locations or inventory costing, they only had the items setup so they. With time and multiple sales and purchases going on, the item ledger entry table was filled with what they call "Garbage Data". Now they would like to start with a fresh Item Ledger Entry table and implement NAV Inventory. They would like to keep the items the way they are only changing the Costing Method. NAV does not let you change the inventory unless (according to NAV support) you close all entries and then comment out part of the trigger on table 27 before changing it. Additionally they want to keep their current inventory item names.
Our suggestion at first was to do a double rename of the inventory items copying the garbage item into a new one. i.e. the old one would be named XXX_OLD and the new one will just be XXX. Therefore you could change the posting method to whatever you wanted and also keep an audit trail of the new fresh start. This will take some time but most importantly they did not like the idea that their open and posted documents (orders,invoices, cm, etc..) will be linked to the OLD items. so essentially they would like to have a brand new item ledger entry table but at the same time have historic documents (i.e. posted invoices) refer to their current items.
Is there a clean way to do this? They don't care about the current item ledger entry, they only care about the history from the documents.
They are thinking of just deleting the item ledger entry table. and start fresh. i would like to know what the implications of such an action could be. Can they corrupt the DB?
I read closing all open entries and archiving the item ledger entry actually deletes the ledger entries themselves but this will mean they will have summary entries that they do not care about and I also heard that archiving was causing other type of issues with related tables where those entries were referenced. Any input or direction will be greatly appreciated. thanks for reading.
OMG i did not realize how much i wrote. sorry
Comments
http://www.BiloBeauty.com
http://www.autismspeaks.org
For our golive we actually run processed that wipe all the transactions and you are left with just setup and master table.
Just make sure you include all the tables.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
I would second this. Some of the tables that come to mine are Item Entry Relation, Item Application Entry, Value Entry, and Value Entry Relation.
You can run the test database functionality before you do the delete and after to test any field relationships. It's a good way to know if you have orphaned any records. And, obviously, do it in a test database first.
You may also want to consider archiving the entries instead of just deleting them. You really never know when you might need something you thought was trash.
Hi Mattrax,
Could I know the way to archieve the Ledger data ?( Generally in NAV we can archieve the Unposted data only)
Thanks in Advance.
Archieve ledger data : copy it to some other table.
http://ssdynamics.co.in
Thanks Singla,
Can i know what is the logic behind this ? At what scenerio we should Archieve ledger data ? what will be the advantages?
Thanks in Advance.
Can any one throw light on this ?
Thanks in Advance
Hello ara3n/Mattrax
Please can you give me a full list of tables that link to ILE.
As we decided to go down the path of deleting ILE in our TEST database before we try it in LIVE.
Is there anything else that should be on our checklist?