Welcome to the session Operational Analytics with ODP - Monitoring Delta

Queues

At the end of this module, you will be able to understand the (operational) delta
queues, monitor delta queues, subscriptions, requests, and data units as well as
reorganize delta queues.

The (operational) delta queues are a new framework which enables multiple
subscribers to replicate data from a set of queues of a provider. A queue serves as a
pass-through data store for data changes or data snapshots.

The BW DataSources of a system are available as queues of the provider BW

DataSource for subscribers of type Search and Analysis and SAP Business Objects
Data Services. In parallel the same DataSources can be connected to a SAP BW system
via the old BW delta queues (transaction RSA7).

There are different types of data requests:

Subscribers can request a data snapshot (full or one-off request). This is supported by
almost any BW DataSource and does not require a subscription.

Subscribers can request data changes (delta request). This requires to create a subscription
first (delta initialization) and usually to transfer the initial data. This is supported only by some
BW DataSources, in one of the following two ways:

The application pushes data into the delta queue

The delta queue pulls data into the delta queue via an extractor

Start transaction ODQMON for monitoring the (operational) delta queues

Use the toolbar or monitor menu to navigate between views

Pre-select queues and/or subscribers in the upper area

Monitor the data volume (not calculated by default for performance reasons)

Choose which request types to include (by default delta subscriptions only)

Analyze queue data in the lower area (use ALV functions like sort and filter)

 Use double-click in the subscriptions column to drill down to the

subscriptions
The selected queue is taken over as pre-selection
All subscriptions for the selected queue are shown

Without pre-selection provider and queue are part of the tables key
The IDs of subscriptions for multiple queues appear in multiple lines
Lines without subscription ID belong to data snapshot requests

Monitor the last confirmed transaction sequence number (TSN) to

identify subscribers that fetch the requested data late or not at all
Mark the lines and end obsolete subscriptions to free resources

 Double-click in the requests column to drill down to the requests

Lines without subscription ID belong to data snapshot requests
Lines without extraction request ID fetch data pushed into the delta
queue

Monitor the request status and identify problems

1.

Check and correct status

2.

Analyze background job logs

3.

Repeat (and debug) extraction requests

4.

Close unconfirmed requests

Display further request details like data volume, selections, and TSN
limits

 Double-click in the units column to drill down to the data units

Available data units are displayed in the upper ALV grid.
Data changes are identified by their transaction sequence number
(TSN)
Initial or snapshot data is grouped by request ID and unit number

Double-click in a line to display the data rows in the lower ALV grid

Technical fields are added for record number and change mode

 Choose menu Goto

Reorganize delta queues

Schedule a job for reorganization, e.g. ODQ_CLEANUP_CLIENT_004

By default the job is scheduled each day at 01:23:45 system time
If needed adapt the start time and frequency in transaction SM37
If needed adapt the retention time for recovery (see F1 help for details

You should now be able to

Understand the (operational) delta queues

Monitor delta queues, subscriptions, requests, and data units

Reorganize delta queues

You can find further information on Monitoring Delta Queues in the SAP Library for
SAP NetWeaver 7.0 including Enhancement Package 3 under http://help.sap.com.

10

11