!--a11y-->
Requests in a DataStore Object 
This tab page gives you information on all the requests that have been run in the DataStore object. You can also delete requests here or schedule when they are to be updated.
The
information
Request
Is Available for Reporting is displayed when activation has been
started.

The system does not check whether the data has been activated successfully.
If the ODS object request is used as a data source in data marts, that is in other BW systems or the Myself system, the data mart status for the DataStore object is displayed. Use the corresponding pushbutton to manage the distribution of this request.
The
icon shows you that the request is retrieved
from all connected InfoProviders. The
icon
shows you that the request is already updated in other InfoProviders. However,
it is possible that you might have to repeat this request. In the event that
you have the impression that the data was not correctly posted, reset the
monitor status and request a repeat so that the request can be posted again.
To do this, choose Reverse Posting of
Request in the monitor. You can also read the documentation about the
monitor.
The traffic light status “red” means that there are problems processing the request, and that these problems are preventing a secure upload.

Only requests that have a “green” status after loading can be activated and displayed in the query.
If a request was “green” after loading but became “red” during activation, you can restart activation.
Data packets with “red” or “yellow” traffic lights are not taken into consideration when executing a BEx query. In this case, subsequent data packages with the “green” traffic lights are also not used in the query, because the consistency of the data in a query can no longer be guaranteed.
You can reset the original monitor request status by clicking on the request status symbol in the column QM Request Status after Update, and selecting Delete Status, Return to Request Status.
With
Monitor you can
jump to the extraction monitor and there determine the location where the
errors occurred. You can display a detailed overview of the request processing
for all request operations with
Log. Here
you can trace when which steps of the request processing, such as status
changes and activation, were started and ended. You can check the performance
from the runtimes. Technical information and detailed messages make it easier
to analyze errors.
This tabstrip gives you information on all the requests that have been run in the DataStore object. You can also delete requests here if you need to. You can only directly delete requests that have not yet been activated. The system uses rollback for requests that have already been activated.
Refer to
Deleting by
Request.
Choose Selection to schedule the update of requests individually or as an event chain in the background. The Post-Processing function allows you to specify the events that you want to execute once the process is complete. The Delete function triggers the background job or it can delete it directly.
You can
activate requests by using
.
You can select whether the requests need to be compressed to one request in
the change log when activated (this request can be rolled back from the
DataStore object as a whole). You can also select whether the requests should
be activated in a series.
See also
Activating Data
in ODS Objects.