Housekeeping for Requests

The number of requests in the data target (request list) influences the processing time for various actions on requests. The overview List of Critical Data Targets enables you to monitor the number of requests contained in data targets of loading processes. This overview allows you to run housekeeping activities, which improve the performance for any actions carried out on requests and which make it possible to load significantly more requests into a data target than before.

There are various actions on requests where information is required (especially from status management) for all requests in a data target and a large number of entries must be processed in different tables. This causes increasing request processing times (for example, InfoCube compression) as the number of requests in a data target increases.

In the Administration view of the Data Warehousing Workbench, go to Start of the navigation pathHousekeeping Tasks Next navigation step Request HousekeepingEnd of the navigation path (transaction RSREQREDUCE). The overview contains data targets, which are classified as not critical, as to be observed or as critical with regards to the number of contained requests or how the number of requests develops. If data targets contain a performance-critical number of requests, you can run housekeeping activities for these data targets in the overview. Depending on the data target in question, you can delete requests, reduce the list of requests in the data target, and perform prerequisite actions for deleting or reducing requests. You can schedule and monitor these activities as periodic jobs.

When the request list is reduced in the data target, the entries are moved from the tables mentioned above and then deleted from the tables. The reduced request list decreases the time that status management requires to process the following processes:

  • Processing of data transfer processes (DTPs) or InfoPackages
    • Generating a delta DTP request (list of source requests and target requests is evaluated)
    • Closing a delta DTP request: (water levels in the source and in the target are evaluated)
  • Activating data in DataStore objects
  • Compressing, rolling up InfoCube data

Structure of Data Target Overview

The data targets are displayed in a list that is sorted in descending order, according to the number of available, but not reduced requests in the data target. Press Filter According to Mass ActivitiesFilter According to Mass Activities to specify which data targets you want to display in the overview.

The system shows the following information in the list for a data target:

  • Classification: Status icons indicate if a data target is classified as critical with regard to the number of requests. For more information about classification, see the tooltip for the field:
    Classification Number/Development of Requests
    Critical Data Target Data target contains more than 20,000 requests, or data target contains more than 10,000 requests and increases by more than 1000 requests every month.
    Data target should be observed Data target contains more than 10,000 requests, or data target contains more than 5,000 requests and increases by more than 1000 requests every month.
    Data target not critical Data target contains more than 10,000 requests, or data target contains more than 5,000 requests but increases by less than 1000 requests every month.
  • Number of requests: Displays the number of non-reduced requests in the data target
  • Increase in requests in last month: Displays the development of the number of requests in the data target
  • The overview also displays information about the reduction or deletion runs for the data targets: Besides the variant name for the job, the last reduction or deletion run is also displayed for a data target along with its status and the next scheduled run.