To make the data that is to be loaded with an InfoPackage available only once in an InfoCube, you can delete from the InfoCube requests with partially overlapping or similar selection conditions as well as relevant deletion selections that are already available in the InfoCube

After loading new data into the InfoCube, the InfoCube contents are checked using the selection conditions for an InfoSource/DataSource/source system combination to see if overlapping data has been loaded into the InfoCube. In this way the data that has been loaded into the InfoCube is not analyzed rather the selection conditions that you determined in the Scheduler for InfoObjects are compared.

With this function the dataset in BW is reduced to the size necessary for analysis, and redundancies are avoided.

You select the variable deletion conditions for transaction data when scheduling the InfoPackage that loads the new data. With the pushbutton in the column Automatic Deletion of Similar/Same Requests from InfoCube in the tab page Data Targets you get to the dialog box Deletion of Requests from the InfoCube After Update.

Here you can determine under which conditions the existing requests are deleted in the InfoCube:

• You can include update modes, InfoSources, DataSources, and source systems for requests.

• You can determine whether the selections for the new request need to be the same or more comprehensive as the selections of the request to be deleted, or whether the selections for the new request need to completely or partially overlap with the selections of the request to be deleted.
• You can specify deletion restrictions according to date. This means that, by using appropriate deletion conditions, only the requests that were loaded within a specific time period are actually deleted.

• You can specify when a request is not to be deleted, in spite of appropriate deletion conditions.

• Another option for determining deletion conditions is creating a user routine for the InfoPackage and the InfoCube. In this routine you can exclude requests from deletion or plan additional requests for deletion.

After successfully loading the new request, deletion or cancellation is carried out automatically.

If the request is not compressed, it is deleted. Only if the deletion is no longer possible with a compression (because the request number is no longer transparent) is a request canceled. You can only cancel a request if no exception aggregation has been defined in the InfoCube or in the update rules and all InfoObjects are updated with summation.

You can set whether requests are cancelled or deleted with or without displaying a warning in the Scheduler under the path Scheduler à Test Deletion Selections at Start.