Show TOC

Deleting from the Change LogLocate this document in the navigation structure

Deleting data from the change log of a DataStore object is recommended if several requests that are no longer needed for the delta update and are no longer used for an initialization from the change log have already been loaded into the DataStore object. If a delta initialization for updates to connected InfoProviders is available, requests have to be posted first before the corresponding data can be deleted from the change log.

A temporary, limited history is retained. The change log can potentially become very large, as data is added for every new request before image and after image. It can therefore be advisable to reduce the data volume and to delete data from a given period in time.

You can create selection patterns in the process variant Deleting Requests from the Change Log and thus delete requests flexibly.

Procedure

Including the deletion of requests from the change log in the process chain

You are in the plan view of the process chain where you want to insert the process variant.

  1. To insert a process variant for deleting requests from the change log in the process chain, select process type Deletion of Requests from the Change Log from process category Further BW Processes by double-clicking.

  2. In the next dialog box, enter a name for the process variant and choose Create.

  3. On the next screen, enter a description for the process variant and choose Continue. The maintenance screen for process variants appears. Here you define which selection patterns requests should be deleted from the change log for.

  4. Enter a DataStore object and an InfoArea. You can use the placeholders Asterisk * and + Plus to flexibly select requests with a certain character string for multiple DataStore objects or InfoAreas.

    Example

    The character string ABC* selects all DataStore objects that start with ABC and end with any characters. The character string ABC+ results in the selection of all DataStore objects that start with ABC and that end with any other one character.

  5. If you set the Exclude Selection Pattern flag, this pattern is ignored in the selection. Settings regarding the age and status of a selection pattern (request selections) are not taken into consideration for excluded selection patterns.

    Example

    You define a selection pattern for the DataStore objects ABC*. To exclude certain DataStore objects for this selection pattern, create a second selection pattern for the DataStore objects ABCD* and set the Exclude Selection Pattern flag. This selects all DataStore objects that start with ABC, with the exception of those that start with ABCD.

  6. Enter a date or a number of days in the field Older than, in order to define the time when the requests should be deleted.

  7. If you only want to select requests with a certain status, set the corresponding indicator.

    You can select the following status indicators:

    Delete Successfully Updated Requests Only

    Delete Incorrect Requests that were not Updated

    Delete Activation Requests Only, No Load Requests

    With Copy Request Selections you can copy the settings for the age and status of a selection pattern (request selections) to any number of selection patterns. To do this, select the selection pattern that you want to copy the settings to, place the cursor on the selection pattern that you want to copy from, and choose Copy Request Selections.

  8. Save your entries and return to the previous screen.

  9. On the following screen, confirm that you want to include the process variant in the process chain.

    The plan view for the process chain is displayed. The process variant for deleting requests from the change log is included in your process chain.

Deletion of requests from the change log in the administration of the DataStore object

  1. In the main menu in DataStore object administration, choose Start of the navigation path Environment Next navigation step Delete Change Log Data End of the navigation path.

  2. Specify the requests that need to be deleted by determining the days or dates (local time zone). You also have the option of specifying whether you only want to delete successfully updated requests, and/or only incorrect requests that are no longer updated in an InfoProvider (this only applies for transaction data).

  3. Define the start date values under Start Conditions.

  4. Press Start (Schedule Deletion).

    The deletion is scheduled in the background according to the selection conditions.

You can also display a request list for the change log. You can also mark requests and then delete them directly.