Automatic Subsequent Processing 

Use

If you want to use an InfoCube as a data source for another InfoCube or DataStore object, we recommend that you make some settings relating to automatic request processing.  This simplifies further processing.

During parallel loading of requests in an InfoCube, these automatic processes can lock each other out (see also automatic processes for improving InfoCube Performance). See Functional Constraints of Processes.

If you use process chains to guarantee serial processing of the process, these settings are not supported for the object (with the exception of setting the quality status). Then you have to include the automatic processes as process types in the process chain.

See also the example for Including InfoCubes in Process Chains.

Features

Setting the Quality Status to OK

You can specify that the quality status of the data automatically be set to OK after it is loaded into the InfoCube. This needs to happen before the requests can be processed further.

Roll Up

You can automatically roll up and transfer into the aggregate requests in the InfoCube with “green traffic light status”, that is, with saved data quality.

The process terminates if no active, initially filled aggregates exist in the system.

Compressing InfoCubes

After rollup, the InfoCube content is automatically compressed. The system does this by deleting the request IDs, which improves performance.

If aggregates exist, only requests that have already been rolled up are compressed. If no aggregates exist, the system compresses all requests that have yet to be compressed.

This function is critical, as the compressed data can no longer be deleted from the InfoCube using its request ID. You must be absolutely certain that the data loaded into the InfoCube is correct. For more information read Compressing InfoCubes.

Activities

To switch on the automatic subsequent processing, select  Main Menu ® Environment ® Automatic Request Handling.

See also:

Loading Data into Aggregates Efficiently