Requests in InfoCubes 

Use

All the requests that have run in the InfoCube are displayed. You can also delete requests. In addition, you can see whether the requests are scheduled for aggregation, if they have been aggregated already, or if they are scheduled for deletion.

Use the update date to limit the number of requests that are displayed.

You can also control the higher-level monitor status of a request individually for an InfoCube.

Features

Request Is Available for Reporting

The  Request is available for reporting information is displayed when the request has been successfully posted to the InfoCube.

InfoCube Status

You can aggregate only those data packages that have the traffic light status “green” (meaning data packages with stored data).

The traffic light status “yellow” means that the process is still running.

A “red” traffic light means that problems occurred while uploading data and these problems prevent a secure upload. An example of an error of this type is an error in the definition of the transfer structure.

Note the information on the relationship between the request status in the monitor and the request status in the InfoProvider administration in the section Overall Status under Traffic Lights.

 

Data packages with traffic light status “red” or “yellow” cannot be taken into consideration when executing a query. In this case, follow-on data packages with “green” traffic lights are not used in the query either, because the consistency of the data in the query can no longer be guaranteed.

In some cases, it is useful to set the InfoCube-specific request status from red to green.

You update requests with an initial load into two InfoCubes If the load process runs successfully for InfoCube 1 but is unsuccessful for InfoCube 2, the higher-level monitor status for the affected request is set to red. As a result, you are not able to use for reporting, the requests that were loaded into InfoCube 1. You can set the request status for InfoCube 1 to “green” by clicking on the status symbol for the request.

You can reproduce the original monitor request status by clicking on the request status symbol and choosing Delete Status, Back to Request Status.

If you delete or reconstruct a request, an application log is automatically generated. You can look at the log by selecting the request and choosing the Application Log pushbutton.

In transaction SM50 you can monitor and manage all background jobs and batch processes.

Data Mart Status of Request

When a request is updated into other InfoProviders, the data mart status for the request is displayed. Use the corresponding pushbutton to manage the distribution of a request.

Choose  Request Got from InfoProvider to show the InfoProvider into which the request has been updated. For more information, see Where-Used List for DTP Requests.

You choose the  icon to show 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.

Checking the data consistency of requests in the InfoCube

You can check the consistency of an InfoCube request. This involves checking for overlaps in the data selections.

For individual requests in the InfoCube, the InfoObjects or fields of the source system are displayed along with the request selection conditions in the Selection Conditions column. The data consistency check runs using the information in this column.

To start a check, select the requests that you want to check on the Requests in the InfoCube tab page.

Choose the pushbutton Check Data Consistency. A separate session opens where you can enter other requests you want to check.

By using the radio buttons on this screen, you determine whether you want to display Errors Only (partial overlapping of the data selections) and/or Complete Overlaps Only. If you have not chosen any requests from the table, all the requests are checked.

Start the check.

A report that can run in the background is started. This report compares each selected request with every other request in the InfoCube and generates an ABAP list. This list contains information about the status of the update, overlaps with other requests, as well as information about the options for compressing, aggregating, or deleting InfoCube data.

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 pushbutton triggers the background job or it can delete it directly.

Request check

You can specify that you want the system to check that the request IDs actually exist in the InfoCube. To do this, choose Environment  → Complete Check of Request ID. If the check is switched on, you can refresh the request display. This checks whether all the requests that have not been aggregated or compressed still exist in the InfoCube. If they no longer exist, the entry is deleted.

This process can take quite some time.

Log display

You can call application logs for the requests in the InfoCube. To do this, select the request you want to analyze from the Requests tab page and choose Environment → Application Log from the main menu, or choose the Application Log pushbutton. All the logs that were written for this request are displayed.  In the log display, you can analyze and access more detailed information about the logs or their respective messages. A navigation tree allows you to navigate among the messages. The messages you have selected are displayed in a list.

You can also display short logs for certain actions in InfoCube Administration on tab page Performance using Call Log. You can analyze the process flow for these actions by checking the status notifications and messages for these logs. The creation and deletion of indexes, reconstruction of statistics, and selective deletion from the InfoCube, as well as aggregation, compression, and reconstruction of the InfoCube are all supported in the log display. In the application log, you can also call logs for the short logs. To do this, choose Application Log and enter the date and time for the log entry. You get this information from the short log.