Show TOC

Cleaning Up Requests Using Process Chains Locate this document in the navigation structure

To clean up data from the DataStore object (advanced), you can use process chain type Cleaning Up Data from DataStore Objects (advanced).


The requests must have already been updated before they can be removed/compressed.


Removing requests avoids a situation where the object consumes too much memory space. Only the oldest requests are removed. These requests can then no longer be reloaded.


  1. You are in the plan view of the process chain where you want to insert the process variant. To insert a process variant for cleaning up requests from the change log in the process chain, select process type Clean Up Requests from DataStore Object (advanced) from process category Data Target Administration 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 the selection patterns, for which you want to clean up requests from the DataStore object.
  4. Enter a DataStore object. You can use the placeholders Asterisk * and + Plus to flexibly select requests with a certain character string for multiple DataStore objects.
    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 character.
  5. The following three options are available under Clean Up Action:
    • Removal of old requests from the inbound table, for DataStore objects (advanced) without modeling properties and with the properties Activate Data and Keep Inbound Data, Extract from Inbound Table.
    • Remove old requests from the change log - for DataStore objects (advanced) with the modeling property Activate Data and Write Change Log.
    • Activate requests - for DataStore objects (advanced) with modeling properties Activate Data and All Characteristics are Key, Reporting on Union of Inbound and Active Table. In this case, the requests are compressed.
    The system automatically selects the relevant option for the object. If you have specified a name part with a placeholder, you can choose whichever option you want. If you want to have multiple clean-up actions for a name pattern, you need to create multiple lines for this name pattern (one line for each option).
  6. In the Requests field, you can specify the number of requests that should not be cleaned up.
  7. Enter a date or a number of days in the field Older than, in order to define the time when the requests should be removed/activated. If you have already specified a restriction under Requests, both restrictions are taken into account. This means that adding the second restriction reduces the number of requests to be cleaned up.
    Note We recommend only using one of these restriction methods.
  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 cleaning up requests is added to your process chain.