Check Time
The check time is the time at which an aggregate is checked. Users determine check times.
You can determine the check time in the following ways:
| Check Time | Description |
|---|---|
|
After Change Run |
The aggregates are checked immediately after the change run. The system only checks aggregates if they have been modified in previous change runs and switches on the check for these aggregates. |
|
After Roll Up |
The aggregates are checked immediately after the data from the InfoCube has been rolled up. The system only checks those aggregates for which the check is switched on. |
|
After (Request) Deletion |
See After Roll Up. |
|
Schedule |
You specify that you want to execute the check at a particular time or periodically in background processing. Note
If you want to execute a particular check frequently but not on a regular basis, choose the Schedule check time when you create the check. Save the check. If you cancel the scheduling you can execute the check at any time using program RSDDK_CHECK_AGGREGATE_CHECKID in the dialog or in background processing (see section As Part of a Process Chainbelow). |
|
Now |
The check is started immediately as a dialog process. Aggregates that are checked with check time Now are not included in the definition of an aggregate check and are not saved. |
As Part of a Process Chain
You can also define a check in transaction RSDDAGGRCHECK and integrate this check into a process chain. To do this, you have to include program RSDDK_CHECK_AGGREGATE_CHECKID in the process chain with the corresponding check ID and the name of the InfoCube. The system checks all aggregates that have been selected with check time Schedule.
Aggregate checks cannot be transported. If you have included a check in a process chain and you transport this process chain, there is the possibility that an incorrect check may be executed. In different systems, create checks that correspond to one another with identical check IDs.