Skip to content

Commit 3154b66

Browse files
committed
slight edit
1 parent c0e7528 commit 3154b66

File tree

1 file changed

+14
-7
lines changed

1 file changed

+14
-7
lines changed

business-central/admin-manage-documents.md

Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,13 @@ Service orders are not deleted automatically, however, if the total quantity on
3030

3131
## Compress Data with Date Compression
3232

33-
You can compress data in [!INCLUDE [prod_short](includes/prod_short.md)] to save space in the database, which in [!INCLUDE [prod_short](includes/prod_short.md)] online can even save you money. The compression is based on dates and works by combining several old entries into one new entry. You can compress entries from closed fiscal years only, and only entries where the **Open** field is set to **No**. Also, by default, you can only compress data that is at least five years old. If you want to compress data that is less than five years old, contact your Microsoft partner.
33+
You can compress data in [!INCLUDE [prod_short](includes/prod_short.md)] to save space in the database, which in [!INCLUDE [prod_short](includes/prod_short.md)] online can even save you money. The compression is based on dates and works by combining several old entries into one new entry.
34+
35+
You can compress entries under the following conditions:
36+
37+
* They're from closed fiscal years
38+
* The **Open** field is set to **No**
39+
* They're at least five years old. If you want to compress data that is less than five years old, contact your Microsoft partner.
3440

3541
For example, vendor ledger entries from previous fiscal years can be compressed so that there is only one credit and one debit entry per account per month. The amount in the new entry is the sum of all the compressed entries. The date assigned is the starting date for the period that is compressed, such as the first day of the month (if the entries are compressed by month). After the compression, you can still see the net change for each account in the previous fiscal year.
3642

@@ -51,19 +57,20 @@ When you are defining criteria for the compression, you can use the options unde
5157
5258
After the compression, the contents of the following fields are always retained: **Posting Date**, **Vendor No.**, **Document Type**, **Currency Code**, **Posting Group**, **Amount**, **Remaining Amount**, **Original Amt. (LCY)**, **Remaining Amt. (LCY)**, **Amount (LCY)**, **Purchase (LCY)**, **Inv. Discount (LCY)**, **Pmt. Disc. Given (LCY)**, and **Pmt. Disc. Possible**.
5359

54-
> [!NOTE]
55-
> Compressed entries are posted slightly differently than standard posting. This is to reduce the number of new general ledger entries created by date compression, and is especially important when you keep information such as dimensions and document numbers. Date compression creates new entries as follows:
56-
>* On the **General Ledger Entries** page, new entries are created with new entry numbers for the compressed entries. The **Description** field contains **Date Compressed** so that the compressed entries are easy to identify.
57-
>* On ledger pages, such as the **Customer Ledger Entries** page, one or more entries are created with new entry numbers.
58-
> The posting process creates gaps in the number series for entries on the **General Ledger Entries** page. Those numbers are assigned to the entries on the ledger pages only. The number range that was assigned to the entries is available on the **G/L Register page** in the **From Entry No.** and **To Entry No.** fields.
60+
## Posting Compressed Entries
61+
Compressed entries are posted slightly differently than standard posting. This is to reduce the number of new general ledger entries created by date compression, and is especially important when you keep information such as dimensions and document numbers. Date compression creates new entries as follows:
62+
* On the **General Ledger Entries** page, new entries are created with new entry numbers for the compressed entries. The **Description** field contains **Date Compressed** so that the compressed entries are easy to identify.
63+
* On ledger pages, such as the **Customer Ledger Entries** page, one or more entries are created with new entry numbers.
64+
65+
The posting process creates gaps in the number series for entries on the **General Ledger Entries** page. Those numbers are assigned to the entries on the ledger pages only. The number range that was assigned to the entries is available on the **G/L Register page** in the **From Entry No.** and **To Entry No.** fields.
5966

6067
> [!NOTE]
6168
> After you run date compression, all accounts in the ledger are locked. For example, you cannot un-apply vendor or bank ledger entries for any accounts during the period for which dates are compressed.
6269
6370
The number of entries that result from a date compression depends on how many filters you set, which fields are combined, and which period length you choose. There will always be at least one entry.
6471

6572
> [!WARNING]
66-
> Date Compression deletes entries, so you should always make a backup copy of the database before you run the batch job.
73+
> Date compression deletes entries, so you should always make a backup copy of the database before you run the batch job.
6774
6875
### To run a date compression
6976
1. Choose the ![Search for Page or Report](media/ui-search/search_small.png "Search for Page or Report icon") icon, enter **Data Administration**, and then choose the related link.

0 commit comments

Comments
 (0)