Show TOC

Traffic LightsLocate this document in the navigation structure

The status of a request is shown using traffic lights in the Monitor for InfoPackages. The overall status of the request is displayed in the Monitor overview tree. The meaning of the status lights is explained in the following section.

Tab Page Status

Technical Status

  • A yellow traffic light indicates that the request is still running. If a request has a yellow traffic light after the loading process has completed, this means that warnings or errors occurred during processing. This means that post-processing steps are not performed, and the request is "not completed".
    Note

    There are two ways of setting the traffic light color if warnings have arisen during processing:

    • You can adjust the setting for the entire system in Customizing, under SAP NetWeaver → Business Warehouse → Automated Processes → Extraction Monitor Settings → Set Traffic Light Color or in the Monitor, under Settings → Valuation of Requests (Traffic Light Color).
    • You can set by InfoPackage the status that the request will have if warnings occur in the Scheduler, by choosing Scheduler → Warning Handling. This setting overrides the system-wide setting.

    We advise against assigning the status yellow to the request when a warning arises, since this prevents subsequent processing steps from starting. The request would then be denoted as incorrect after the time-out time had elapsed anyway.

  • A red traffic light indicates that the request has errors or that the maximum wait time has been exceeded.
    Note

    The traffic light is set to red and the error classified as containing errors if the time the last IDoc for a request was received exceeds the maximum wait time.

    Even though the request has the status red, it is not terminated. The traffic light turns to yellow if the monitor receives a new log for this request after the wait time has elapsed.

    Even if you set the overall status (QM status) in the monitor manually, this does not prevent data being posted fort his request. In this case, the request cannot still have status green, however, as the overall status overrides the monitor's technical status.

    There are two ways of setting the wait time after which requests are to be considered as having errors:

    • You can adjust the setting for the entire system in Customizing, under SAP NetWeaverSAP NetWeaver Business Warehouse → Automated Processes → Extraction Monitor Settings → Set Traffic Light Color or in the Monitor, under Settings → Waiting Time Until Status Incorrect.
    • In the Scheduler, via Scheduler → Timeout-Time, you can set the maximum wait time after which a request is set to red in the Monitor per InfoPackage. This setting overrides the system-wide setting.

    The status can only be changed after the maximum wait time has run if the request is monitored by the Monitor assistant. Only then are any subsequent processing processes triggered for the request.

    We recommend periodically scheduling the assistant in Customizing (SAP NetWeaver → Business Warehouse → Automated Processes → Extraction Monitor Settings).

  • A green traffic light indicates that the loading process has been completed.

In Customizing, under SAP NetWeaver → Business Warehouse → Automated Processes → Extraction Monitor Settings → Set Traffic Light Color or in the Monitor, under Settings → Valuation of Requests (Traffic Light Color), you can define which status a request is given if there is no data in the source system.

Overall Status

In the default setting, the overall status of a request is set by the technical status. You can change the overall status of a request using the QM action. To do this, press Overall/Total on the Status tab page. You can create a quick-info text for the status you have assigned. This is then displayed if you place the mouse over the total status for the request.

Caution

If you set the delta request from red to green, BW sends a delta request to the source system with the next request. The source system then delivers a delta. Data for the request that was originally red can no longer be provided by the source system (even with a repeat). This can lead to data loss.

Note

For a better understanding of the relationship between the request status in the monitor and the request status in InfoProvider administration, see the following:

  • When you post data to InfoProviders using an InfoPackage or a process chain with process variant Read PSA and Update Data Target, a QM action does not change the request status in the InfoProvider administration. You need to perform the QM action again in the InfoProvider administration in order to change the request status.
  • The status of a request in the monitor can be different to the status of this request in the InfoProvider administration. This is the case as soon as a subsequent action is started for the request in the InfoProvider, for example activation of data in the DataStore object or compression of InfoCube data. In this case, the status display in the InfoProvider administration then refers to the subsequent action. The statuses are also different to each other if you have posts the request to the InfoProvider using a reconstruction. In this case, you can also see the log for reconstruction in the monitor. The result of this log determines the status of the request in the InfoProvider administration. However, the result of this log does not influence the status of the request in the monitor.
  • If a request has status red because activation of the data in the DataStore object has been cancelled, the overall status cannot be set to green by a QM action. This can lead to data inconsistencies, since some request data has been activated before termination.
Tab Page Detail

On this tab page, the Monitor displays details for all actions executed with the request in an overview tree.

  • Request
  • Extraction
  • Transfer
  • Processing
  • Posting
  • Process chains (for dataflow 3.x without DTP)

You can display information and messages using a node's context menu.

Note

When determining the technical status, the status of the displayed nodes and the root nodes of the overview tree are not necessarily relevant. For example, you might have completed the request, extraction, transfer and processing steps successfully (status green), but errors could still occur while posting the data with a data transfer process (status red). The technical status of the request would then be green, although a node on the Detail tab page in the overview tree would have the status red.

The status of the root nodes in the overview tree is aggregated from the status of all displayed nodes and therefore does not have the same meaning as the technical status of the request.