Hi, I need orders not to be deleted when shipment & Invoice. What if I change the code to success it? Is there any bad impact about this ? Any suggestions ?
quote:
Originally posted by philipv
Hi, I need orders not to be deleted when shipment & Invoice. What if I change the code to success it? Is there any bad impact about this ? Any suggestions ?
I did it for a customer about three years ago and so far nothing evil happened. They have a lot of old orders, but they are happy with them. [:)] Anna
If you are talking about purchase orders, then I can tell you from our own experience that keeping them around does not cause any problems. We are running some statistics on our purchase orders from time to time, which requires them not to get deleted or archived. All has been working well for the 4 years we are now running Navision.
The only problem you might have it the order tables would become cluttered and it would be difficult to navigate to open orders. You could use the standard Navision archive functionality to copy the order the the order archive tables then post it as normal. Chris.
I have done this for many of my clients in both the sales and purchases modules and the only problem has been the increased amount of data in the database. The benefits however for one of my clients in particular has been overwhelming, they rely heavily on actual order data and the massive amounts of data linked to these when reporting and viewing historical information. Good luck in Codeunits 80 & 90 [}:)]
We’re running on 2.60 and we need to Archive Purchase Orders. I’m looking for a simple solution so I thought maybe of creating a new “Document Type” on Table 38 and 39 called “Document Type”::“Archived Order” and basically just have a Batch job which RENAMEs the the Purchase “Order” we want to archive into Purchase “Archived Order” … What are you point of views/opinions on this ?
I would highly recommend to move the records out of Sales Header and Sales Line. Otherwise You will run in to problems. The problem is that when everything is invoiced cu80/90 doesn’t care to update the fields in Sales Line since it’s going to be deleted anyway. So instead of delete in cu80/90, move to other tables. Also make that move in the batches that deletes fully invoiced orders
Hello Tarek, I have come accross a number of clients who have either had a new Document Type of Archived/Completed Order added or just kept the orders as orders in the Sales Header and Line tables, but in the case of customers who put more orders on than most, the order processing has slowed down because of the amount of extra data that is held in what are essentially transactional data tables. We have found that having separate “Archive” tables has worked better, as the history is retained, but does not slow down the handling of new, live, documents. We have also found that it makes upgrading easier as Order Archiving is a standard feature in 3.10 onwards, and having a system that already works in a similar way makes it much easier. Once you have upgraded the data, you just have to replace your archiving functions with a call to the 3.XX one when an order is completed and it will auto-archive. If it works the same as the new version then you do not have to re-train your users either! [:D]