Requests in the InfoCube 

Use

AAll the requests that have run in the InfoCube are displayed. You can also delete requests. You can also see whether the requests are scheduled for aggregation, whether they have been aggregated already, or whether 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.

Functions

Request is available for Reporting

The information  Request Is Available for Reporting is displayed when the request has been successfully been posted to the InfoCube.

InfoCube Status

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

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

A “red” traffic light means that there are problems uploading data, and that these problems are preventing a secure upload. These can be, for example, errors in defining the transfer structure.

Data packages with traffic light status “red” or “yellow” cannot be taken into consideration when executing a 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.

In certain cases it could make sense to set the InfoCube-specific request status from red to green.

You update requests with the initial load into two InfoCubes If the load process runs successfully for InfoCube 1, but is unsuccessful for InfoCube 2, then the higher-level monitor status for the affected requests is set to red. As a result, you are not able to use for reporting, the requests that were loaded successfully 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 InfoCubes

If the InfoCube is updated in other data targets, the data mart status for the InfoCube is displayed. Use the corresponding pushbutton to manage the distribution of a request.

The  icon shows you that the request is retrieved from all connected data targets. The  icon shows you that the request is already updated in other data targets. 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.

Checking the data consistency of requests in the InfoCube

You can execute a consistency check on the InfoCube requests, meaning you can look 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 from the tab page Requests in the InfoCube.

Choose the pushbutton Check Data Consistency. This brings you to a separate session, where you can enter other requests you want to check.

By using the radio buttons on this screen, you can also 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, then all requests are checked.

Start the check.

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

Scheduling background jobs

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. Choose Delete to trigger the background job or to delete it directly.

Request check

You can specify if 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 if 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 Logfrom 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 on 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 of the InfoCube Administration on tab page Performance using Call Log. It is possible to analyze the process of these actions by using 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 the aggregation, compression, and reconstruction of the InfoCube are all supported by 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 of the logging. You get this information from the short log.