Child pages
  • Operational Delta Queue Cleanup (ODQ_CLEANUP)
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 Queue Cleanup.

Overview

Operational Delta Queue Cleanup in general

The main purpose of the Operation Delta Queue Cleanup is to delete all confirmed and canceled requests, which are older than 24 hours (default value). By default the job is scheduled each day at 01:23:45 system time. The technical name of the job contains also the client number, in which the cleanup has to be done e.g. ODQ_CLEANUP_CLIENT_004. It refers to a cleanup job in client 004. If needed start time and frequency can be adapted in transaction SM37. If needed the retention time for recovery can also be adapted.

You can access it in ODQMON in Menu 'Goto' and 'Reorganize delta queues'. This will open the ABAP program ODQ_CLEANUP (in transaction SE38).

Retention Period

There are three different period:

To recover a delta process that has been canceled: This is the minimum retention period for data in the queue tables that is flagged as retrieved in the delta process or as canceled. Once this period has expired, all data flagged as retrieved or invalid is deleted from the delta queue by a periodically scheduled reorganization process. A delta process can always be reset or repeated at this time for individual subscribers.The minimum retention period is given in hours. The default setting is 24 hours.

For data with low relevance: Once this period has elapsed, the periodic reorganization process deletes all data in the queue that meets the following conditions:

  •  It has not yet been declared as retrieved or invalid
  • All subscribers have subscribed to it with low relevance. This period is given in days. The default is 1 week.

For data with medium relevance: Once this period has elapsed, the periodic reorganization process deletes all data in the queue that meets the following conditions:

  • It has not yet been declared as retrieved or invalid
  • All subscribers have subscribed to it with at most medium relevance.

This period is given in days. The default is 31 days (4 weeks plus an extra weekend).

Classification of relevance of data

Data that has not yet been retrieved and is business critical is never automatically deleted by the reorganization process.

At present, the system does not make any relevance-related distinction of delta data. All data in the delta queue is considered business-critical and is therefore not deleted until it has been flagged as either retrieved or invalid.

Because of the particularly high volume expected, data from delta initialization requests and standard requests is also classified as being of low relevance.

Scheduling the reorganization run

When a delta queue is activated, the reorganization run (program ODQ_CLEANUP) is scheduled automatically if there is no periodic scheduling yet. The periods specified above can be modified either by manually scheduling them before the first delta request or by subsequently changing the automatically scheduled job. To do this, you can call Job Administration directly from program ODQ_CLEANUP or perform "rapid scheduling" with modified selection parameters.

In the default setting, the reorganization run is scheduled to run once daily at between one and two in the morning (in system time). The start time and period can be changed if required.

There is no automatic scheduling if periodic scheduling has been performed for program ODQ_CLEANUP in the same client. To delay reorganzation by a certain time, for troubleshooting purposes for example, the scheduled job must therefore be reset from status Released to status Planned or Released/Suspended. If the scheduled job is deleted, it is rescheduled next time a delta initialization or a standard request is made.

Simulation Run

You can also schedule a 'Simulation run' by setting the flag.

 

Please ensure that the corrections in SAP Note 2286619 are applied. The SAP Note is relevant for following releases/SPs:

Release From To 
 Release 2005_1_700 SAPKIPYJ7N SAPKIPYJ7Q
 Release 2006_1_700 SAPKIPYM13 SAPKIPYM23
 Release 701 SAPK-70108INPIBASIS SAPK-70118INPIBASIS
 Release 702 SAPK-70207INPIBASIS SAPK-70218INPIBASIS
 Release 730 SAPK-73003INPIBASIS SAPK-73014INPIBASIS
 Release 731 SAPK-73101INPIBASIS SAPK-73117INPIBASIS
Release 740  SAPK-74002INPIBASIS SAPK-74014INPIBASIS
Release 750  SAPK-75001INSAPBW SAPK-75003INSAPBW

Dependencies

If data with low or medium relevance that has not yet been declared retrieved or invalid is deleted by the periodic reorganization process, the delta processes (subscriptions) that belong to it are also reset. These then have to be re-initialized.

Related Documents

SAP Help: Functions of the Delta Queue Monitor

SAP SCN Wiki: Introduction to Operational Delta Queues

Related SAP Notes/KBAs

SAP Note 2286619: ODQ_CLEANUP deletes entries in simulation mode

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

SAP KBA 2166526: Solution to delete unconfirmed requests in transaction ODQMON

SAP KBA 1836773: How to delete outdated entries from delta queues - SAP Data Services

SAP Note 1745317: ODQ: Cleanup Notifcation does not pass Queue Names

SAP Note 1735928: ODQ: Improvements for Cleanup

SAP Note 1655273: ODQ: More than one cleanup job per client

SAP Note 1599248: ODQ: Real-time Support

SAP Note 1507908: ODQ: Client dependency of the Cleanup Job is undefined

SAP Note 706478: Preventing Basis tables from increasing considerably