Sales Shipment Header & Lines

Savatage · 2006-07-06

I have two tables

110 - Sales Shipment Header
111 - Sales Shipment Line

These are huge and I don't need 2003 & 2004 info.

Does anyone see problems with deleting these two years from these tables?

Quickly thanks - I have an ichy finger on the delete button =P~

Thanks.

ara3n · 2006-07-06

As long as you have a backup, You should be fine.

Savatage · 2006-07-06

\:D/ Thanks - 2nd opinions never hurt!

ara3n · 2006-07-06

Make sure you delete the associated dimensions for the lines and header.
If you are using serial or lots there is another table. I can't remember the name right now.

[edit] Item Entry Relation that relates to sales shipment line.

Alex_Chow · 2006-07-06

Deleting them is no problem as long as they're properly shipped and invoiced.

We've done this at the request of one installation site back in 2003 and we haven't ran into any problems yet.

Savatage · 2006-07-07

ara3n wrote:

Make sure you delete the associated dimensions for the lines and header.
If you are using serial or lots there is another table. I can't remember the name right now.

[edit] Item Entry Relation that relates to sales shipment line.

no serial or lots - very very basic

Savatage · 2006-07-07

deadlizard wrote:

Deleting them is no problem as long as they're properly shipped and invoiced.

2003 & 2004 I sure hope so - else we're gonna have some upset customers

Alex_Chow · 2006-07-07

Well.. You'd be surprised at how many orders that were shipped/received without invoiced.

I'm not sure how it happened, but it does. :?:

Savatage · 2006-07-07

FYI - Apparently you can't delete them if the No. Printed is equal to zero

so I printed them to a phoney printer & deleted the output from the queue.

It generated a 150,000 pages.

My database size went down 10% \:D/

We never use these by the way - it just grows forever.

DenSter · 2006-07-08

If size is a concern Harry, you can decrease the size also by disabling unused SIFT levels. I've taken a native database from 8GB down to less than 5 just by disabling all secondary keys on the Item Ledger table.

Of course you would have to analyze each and every key's usage before you start disabling them. The good part is though that if you run into an issue you can easily turn them back on.

Alex_Chow · 2006-07-08

Savatage wrote:

FYI - Apparently you can't delete them if the No. Printed is equal to zero

so I printed them to a phoney printer & deleted the output from the queue.

It generated a 150,000 pages.

You could've just removed the code where it tests the No. Printed... Or print to the Microsoft Office Document Image Writer, which by the way, is one of the more unused/unknown tools.

Savatage wrote:

We never use these by the way - it just grows forever.

The Sales Shipments are mainly used to print Bills of Ladings. However, if you're using any Lanham products, you can generate teh BOL from the posted invoice.

Savatage · 2006-07-08

deadlizard wrote:

The Sales Shipments are mainly used to print Bills of Ladings. However, if you're using any Lanham products, you can generate teh BOL from the posted invoice.

We do use Lanham & that's exactly what we do.

Savatage · 2006-07-08

DenSter wrote:

If size is a concern Harry, you can decrease the size also by disabling unused SIFT levels. I've taken a native database from 8GB down to less than 5 just by disabling all secondary keys on the Item Ledger table.

Of course you would have to analyze each and every key's usage before you start disabling them. The good part is though that if you run into an issue you can easily turn them back on.

I hear ya! that table is a monster

Here are my current keys n info for ILE
http://www.geocities.com/navision_attain/ILE-KEYS.pdf

you guys work saturdays too I see

Alex_Chow · 2006-07-10

Savatage wrote:

you guys work saturdays too I see

No, we just have nothing better to do.

Sales Shipment Header & Lines

Answers

Categories

Sales Shipment Header &amp; Lines

Answers

Categories

Sales Shipment Header & Lines