Child pages
  • Introduction to Operational Delta Queues
Skip to end of metadata
Go to start of metadata

Purpose

 The purpose of this page is to clarify the understanding of the system logic and requirements in relation to Operational Delta Queues.

Overview

The Operational Delta Queue (ODQ)

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: 

  1. 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.
  2. 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

Monitoring Delta Queue Subscriptions

Start transaction ODQMON  for monitoring the (operational) delta queues:

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 table’s 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

  

Monitoring Delta Queue Requests

 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:
ButtonsMeanings

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.

Monitoring Delta Queue Data Units

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

Reorganize Delta Queues

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)

Related Content

Related Documents

 Monitoring Delta Queues - SAP HELP

Related SAP Notes/KBAs

2166526 - Solution to delete unconfirmed requests in transaction ODQMON

2190229 - Composite request can only be confirmed by the subscriber (Message No. SODQ313)

 

 

2 Comments

  1. If the delta request has been deleted accidentally from BW side, is it possible to recove the delta?


    Thanks,

    Galland

    1. Hi Galland,


      This depends on the retention period you set on the source system in ODQMON. If the retention period has expired, the data is deleted during the delta queue reorganization and this case, delta data cannot be retrieved.

      I think when you delete the delta request in BW system, you will get a pop-up window like this: