After a while a system like Visma Business
may contain large numbers of transactions. It may therefore be worthwhile to tidy up old
transactions.
The Compress transactions processing menu item allows you to
combine old transactions so that processes can be carried out more quickly in the
tables.
Customer transactions, supplier transactions, general ledger transactions, capital asset transactions and product transactions can be compressed.
When you start compression you are prompted to enter a Compression to date and check the box if you want to include organisational units. The transactions in question are then checked against this date in accordance with the following rules:
Transactions relating to customers, suppliers, general ledgers and capital assets with a value date older than or equal to the Compression to date are compressed.
- Transactions relating to customers, suppliers, general ledgers and capital assets with a value date older than or equal to the Compression to date are compressed. The sort should as a minimum be: Account no., Period, VAT year, VAT period, to be able to maintain the facility to check VAT retrospectively. If you use organisational units you should also consider the need for these as well.
- Transactions relating to products with a transaction date older than or equal to the Compression to date are compressed. The sort should as a minimum be Product no., Transaction type, Warehouse no., Shipment, Proc. Method 2; in addition to this it might also be useful to use customer no., supplier no., year/period. It is also important to check whether any of the transactions have temporary cost price status or are awaiting goods received.
- For product transactions Visma Business will compress up to and including the date that you have entered. You must
update the Stock change field in this table. You do this
by holding down the Shift key while simultaneously
pressing the compression button in the menu bar. You can generate a stock record
of deleted product transactions.
After compression you will only obtain transactions with accumulated totals.
Merk: Compression deletes old transactions and creates new, accumulated transactions. It
is therefore important that you:
- Make a back-up copy of your data before you begin compression.
- Carefully consider how you want to carry out the merge.
- Define a compression voucher type in the Bedriftsopplysninger
table.
- It is not the selection on screen that is processed. The screen is only used
to set the break level.
Compressing transactions in Oracle
When compressing transactions, Oracle does not use the correct index. You can rectify
this by using the parameter Optimization parameters in the
Other preferences dialog box under the Design/Table/Other
preferences menu item. To access Other preferences you must be in Design mode. You
can either select View/Design mode or the shortcut key combination
Ctrl+D.
The syntax is as follows:
/*+INDEX ( table [index [index]...] ) */