Show TOC

Monitoring Delta QueuesLocate this document in the navigation structure


A delta queue is a data store in the source system. Data records are either written automatically to the delta queue using an update process in the source system (for example, 2LIS_11_VAITM) or retrieved using the extractor interface (for example, 0COSTCENTER_ATTR).

The role of a provider is to provide one or more delta queues of a specific type. The "BW DataSource" is an example of a provider. In this case, the delta queue name matches the DataSource name (for example, 2LIS_11_VAITM). The target application of the delta queue is referred to as the "subscriber" (of a specific data services system, for example). A subscription can be defined as follows: a specific subscriber "orders" data changes from one or more queues and continues processing the transferred data. Subscribers are categorized by their subscriber type (for example, SAP BusinessObjects Data Services). A subscription occurs when the subscriber requests data. Every subscription has a unique transaction number, for example {2010-10-22 08:03:52 000001 CET}. A subscriber can have more than one subscription. A queue can also be in multiple subscriptions for the same subscriber.

The data is stored in a compressed state in the delta queue. A delta request transfers data records from the queue to the subscriber. The data changes to a queue can also be requested by more than one subscriber. A subscriber can also request data from a queue as a one-off request (Full). In this case, the request is not a subscription.

The data is retained in the delta queue for a specified time period for recovery purposes - in other words, in case the subscriber needs to retrieve the data records again.

Delta Queue Monitor

The Delta Queue Monitor (transaction ODQMON) allows you to monitor delta queues in various views:

  • Queues

    Here you see all the queues available in the system with the status of each queue, the number of associated subscriptions and the number of associated requests.

  • Subscriptions

    The detailed information for the subscription level is displayed here.

  • Requests

    The detailed information for the request level is displayed here.

  • Units

    The units are displayed here in which the data from a request can be transferred jointly.

You can access the views using pushbuttons or the Monitor menu.


You are on the Delta Queue Monitor screen (transaction ODQMON).

Checking the Data Volume in Queues

The queue overview allows you to identify which delta queues have a high data volume. Queues with a high data volume could mean that requests cannot be retrieved.

  1. If you only want to check specific queues, restrict the queue data display by using a preselection in the monitor.

    For more information, see Functions of the Delta Queue Monitor.

  2. To display the data volume of the queues, choose Calculate Data Volume (Extended View).

  3. To see which queues contain large volumes of data, you can sort the list of queues by the compressed size in bytes, for example.

  4. If you find requests for a queue that have not been retrieved, check these requests. For more information, see Monitoring Requests in the Delta Queue Monitor.

Checks for When No Data is Delivered to the Subscriber

If no new data from the queue is delivered to the subscriber, check the corresponding requests.

  1. Double-click the row with the relevant queue in the overview. The subscription overview for this queue appears.

  2. Double-click the row with the relevant subscriber in the overview. The request overview for the selected subscriber in the selected queue appears.

  3. Analyze the requests and execute the actions required to continue with the data transfer. For more information, see Monitoring Requests in the Delta Queue Monitor