Activities to Reduce the Number of Requests in a Data Target

The type of activities required in order to reduce the number of requests in a data source depends on which phases of the life cycle of requests the requests in the data target are located in.

Life Cycle of Requests in InfoCubes and DataStore Objects

  1. The request is loaded successfully into a data target (technical status of the request = ok).
  2. The request is available for reporting and analysis (overall status of the request = ok).
  3. For Standard DataStore objects: The request has been activated.
  4. The request is updated to at least one retrieving target.
  5. The request is updated to all subsequent data targets.
  6. The data records in the request are removed from the data target in one of the following ways:
    • For InfoCubes: The request is compressed.
    • For Standard DataStore objects: The records in the request are deleted from the change log.
    • For write-optimized DataStore objects: The request is moved to near-line storage.

The last step makes sure that the request in the data target is nothing more than a set of defined data records, meaning that the data records cannot be assigned to the request any longer. This request can thus be removed from the request list, and the value in the data target can be set to the highest non-reduced request.

Overview of Activities to Reduce the Number of Requests in a Data Target

Data Target Type Activities Required as Prerequisite for Reduction of Number of Requests Measured for Reducing the Number of Requests
InfoCube Compression Reduction
Standard DataStore Object Delete records from the change log Reduction
Write-Optimized DataStore Object More to near-line storage Reduction (if the write-optimized DataStore objekt is used as corporate memory)

Deletion from the change log (if the write-optimized DataStore object is used as a staging object in the data provider layer)
InfoObject - Deletion (from Status Management)