This function allows you to delete both inactive and active requests from DataStore objects. It enables you to delete incorrect requests as the system usually only recognizes errors in the data or update rules after the request has been activated. The request is deleted both from the table for active data and the change log.
An error message appears if the request has already been updated into additional InfoProviders. In this case, you first have to delete the request to be deleted from the data targets. See also Deleting Already Updated Data.
Afterwards, you have to manually reset the data mart status in the DataStore object. Then you can delete the request. You can load more deltas after this.
If you do not reset the data mart status, the delta update is deactivated in the connected InfoProvider when deletion is performed.
You can only directly delete requests that have not yet been activated. The system uses rollback for requests that have already been activated.
With rollback, the system reverts back to the status in the DataStore object before you updated the incorrect requests. This means that all requests that were updated after the incorrect request are also deleted. You can repost requests that are available in the PSA afterwards.
Processing upon deletion can be performed in parallel on a package-by-package basis. In this case, the packages in a request are processed in parallel. This is possible because the package has a unique key. Processing upon deletion is always performed sequentially only for requests that have been loaded and activated using a DTP for real-time data acquisition.
If you post three requests and want to delete the middle one, the final request is also deleted.
It is also possible to combine three requests into one single request in the DataStore object when you activate. Requests 1, 2, and 3 in the source DataStore object correspond to request 1 in the target DataStore object. If you want to delete request 3 from the source DataStore object, you have to delete request 1 from the target DataStore object because the three requests are combined in this one. Subsequently you also have to delete all three requests from the source DataStore object in order to remain consistent.