ADSO ChangeLog Cleanup

Created by:	SNP
Client-dependent:	No
Settings as variant:	No
Support for RecycleBin:	Yes
Support for initial Housekeeping:	No
Pause/resume support:	No

Introduction

The ASDO ChangeLog Cleanup is part of the Business Warehouse deletion tasks.
The ChangeLog tables are named /BIC/A*3 and are automatically created for Advanced DataStore Object (ADSO). It is created with the options Activate data and Write ChangeLog.
The ChangeLog contains the change history for delta updating from the DataSource or InfoProvider to ADSO.
The data is inserted into the ChangeLog via the activation queue and is written to the table for the active data upon activation. During activation, the requests are sorted according to their logical keys. This ensures that the data is updated in the correct request sequence in the table for active data.
In SNP Outboard™ Housekeeping, it is possible to delete data from ChangeLog tables using a retention time.

Step List

1. In the main SNP Outboard™ Housekeeping menu, select Business Warehouse > Deletion Tasks > ADSO ChangeLog Cleanup and click Settings.
2. Specify your desired settings. You can create new settings by entering a new ID or choose from existing settings.
3. In the Settings area of the task ADSO ChangeLog Cleanup, you can specify the selection criterion of the settings group as well as the time window for data relevancy.

For more information on settings, refer to the Creating a settings ID chapter of this user documentation.

_scroll_external/attachments/image2020-10-5_14-21-56-0105d4c3db1398e79c263694e49d5ed2c6003fd7f360a571496fe0ad48289315.png

_{ADSO ChangeLog Cleanup – settings group selection}

You can edit the created settings group. To save your changes, click Save Settings in the taskbar.

Step 1

1. You can specify the ADSO name(s) by clicking Add object.
2. From the list of available ADSOs (F4), select which ones you want to add to the newly created settings group and then confirm your selection.
3. You can specify the InfoArea as an additional filter for ADSOs. The options Include and Exclude determine if the result of the selection will be added or removed from this selection.
4. You can set the ADSO name in a pattern style, e.g. ZADSO*.
5. By selecting Do you want to save a pattern?, you can skip the selection of ChangeLog tables. This is useful if you create settings at the group level.
6. After confirming, select the ChangeLog tables that you want to clean up and confirm your selection again.

The selected ChangeLog tables will be added to the settings group list.

_scroll_external/attachments/image2020-10-5_14-24-2-9deb01abb6053bb4d78dc921bbf5aea85e4acb101771f7f21b2207cd152d6487.png

_{ADSO ChangeLog Cleanup – ADSO selection}

_scroll_external/attachments/image2020-10-5_14-24-51-556542073acbbf3b339225f846ba417c3b03b9c596ef5c52d2ee90576e61744c.png

_{ADSO ChangeLog Cleanup – Changelog selection}

_scroll_external/attachments/image2020-10-5_14-25-59-bb344557f522c4e814436d75afae5671b3f65d7289fa4834d09fa6e0d54fbc45.png

_{ADSO ChangeLog Cleanup – Settings with patterns and objects}

Icons in the X column indicate how the lines will apply to the overall list of ChangeLogs:

_scroll_external/attachments/worddav5e8fb89c7710c4a2119043bc0b1bcb06-c014e2bc2ca338584753a0e6dbb57c35126fb9af7c94141baf40cf0c254c3b4a.png The pattern will be evaluated during the task execution, and the ChangeLogs will be added to the overall list.
The pattern will be evaluated during the task execution, and the ChangeLogs will be removed from the overall list.
_scroll_external/attachments/worddav21fc442754602cae38d6f871ff97b3ff-ecb5f0b0df2f60f2ca546abd777459f6e69f974edd9a2d5c8861462f2ddfdae9.png The ChangeLog will be added to the overall list.
The ChangeLog will be removed from the overall list.

Step 2

By clicking Select requests, you can specify the time period for the deletion of relevant entries in selected ChangeLog tables.

NOTE You can specify different time criteria for every ChangeLog table in the list. If no selection on the ChangeLog table is made, the selected time parameter will be set for all ChangeLog tables in the list.

_scroll_external/attachments/image2020-10-5_14-30-1-4c09b49723e0c239e4e72268065dc8fab26405bd54b6cbe9ebe215be2c545819.png

_{ChangeLog Cleanup – Time period settings}

Step 3

Test Run for selected ChangeLog tables: This run scans all ChangeLogs and identifies all request IDs for any ChangeLog that fulfills the Time period condition. After Test Run execution, a list of relevant request IDs, ADSOs and InfoAreas is opened.

_scroll_external/attachments/image2020-10-5_14-30-55-d00948125f574f7d0403a25676c0483ddb9b75dab27f709c4da8cc9fa3863eb4.png

_{ADSO ChangeLog Cleanup – Test run result}

NOTE To create the settings at the landscape level, the Test Run button is unavailable and therefore this step is skipped.

Step 4

The next step is to set the time limit for the RecycleBin. Enter the value in days in the RecycleBin Period field or leave the default value, which is 14 days.

NOTE Data stored in the RecycleBin is available and can be restored if necessary during the time period that was defined during the setup. Once the time period expires, data stored in the RecycleBin will be automatically deleted by manual or scheduled execution of the system task RecycleBin Cleanup.

_scroll_external/attachments/image2020-10-5_14-32-19-eda39c0a9d8663d2fae38f1ab0276ca131517864576e25d16e5eb4b4073df10c.png

_{ChangeLog Cleanup – RecycleBin Period}

Once the settings for the task ADSO ChangeLog Cleanup are specified, you can run the created/modified settings group from the main menu. There are several options for starting the deletion. For more information, refer to the Executing and Scheduling Activities chapter of this user documentation.

You should specify the settings ID while executing/scheduling the activity.
To check the status of the run, you can go to the monitor or check the logs.

Recommendation

We recommend periodically deleting the following requests:

Delta requests that have been updated successfully in an InfoProvider and no further deltas should be loaded for.

It helps to reduce the database disk space usage significantly. We recommend scheduling this task daily with a retention time of 15 days in a row, but it is application-specific.