Automatic Further Processing 
If you are still using a 3.x InfoPackage to load data, you can activate several automatic features to further process the data in the InfoCube. If you use the recommended data transfer process and process chains, however, you cannot use these features.
We recommend that you always use process chains.
More information: Including InfoCubes in Process Chains
Caution
During the parallel loading of requests into an InfoCube, these automatic processes can lock each other out if they do not use process chains (see also the automatic processes for improving InfoCube Performance). See Functional Constraints of Processes.
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.
You can automatically roll up requests in the InfoCube with "green traffic light status", that is, with ensured data quality, and transfer them into the aggregate.
Caution
The process terminates if no active, initially filled aggregates exist in the system.
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.
Caution
This function is critical, since you cannot delete compressed data 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.
To activate automatic further processing, choose .
See also: