Wednesday 28 March 2012

Requests in DataStore Objects

Use

This tab page provides information about all requests that have run in the DataStore object. You can also delete requests here or schedule an update.

Features

Request Is Available for Reporting
The This graphic is explained in the accompanying text Request is available for reporting information is displayed when activation has been started.

The system does not check whether the data has been activated successfully.
Data Mart Status
When a request from a DataStore object is updated into additional InfoProviders, the data mart status of the request is displayed. You use the corresponding pushbutton to manage the distribution of this request.
To show the InfoProvider into which the request has been updated, choose This graphic is explained in the accompanying textRequest Got from InfoProvider

For more information, see Where-Used List for DTP Requests.

The This graphic is explained in the accompanying text icon shows that the request has already been updated into other InfoProviders. However, in some cases you might have to repeat this request. If you think that 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 Request Reverse Posting in the monitor. For more information, see the documentation in the monitor.
Request Status
The “red” traffic light means that problems occurred while processing the request, and these problems prevent 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 is “red” during activation, you can restart activation.

Data packages with a “red” or “yellow” traffic light are not taken into consideration when you execute a BEx query. In this case, subsequent data packages with a “green” traffic light are not used in the query either because the consistency of the data in the query can no longer be guaranteed.

You can reset the original request status in the monitor by choosing the request status symbol in the QM Request Status after Update column, and selecting Delete Status, Back to Request Status.
Monitors and Logs
You choose This graphic is explained in the accompanying text Monitor to jump to the extraction monitor and determine the location of the errors that occurred. You can display a detailed overview of request processing for all request operations by choosing This graphic is explained in the accompanying text Log. Here you trace the start and end times of the steps in request processing, such as status changes and activation. You can check performance by looking at the runtimes. Technical information and detailed messages make help you analyze errors.
Deleting Requests
This tab page provides information about all the requests that have run in the DataStore object. You can also delete requests 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.
Scheduling Background Jobs
Choose Selection to schedule the update of requests individually or as an event chain in the background. The Subsequent 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 deletes it directly.
Activating Requests
You chooseThis graphic is explained in the accompanying text to activate requests. You can specify whether the requests are to be compressed in one request in the change log when they are activated (this request is then rolled back from the DataStore object as a whole). You can also apply settings for processing.


End of Content Area

No comments:

Post a Comment