Hierarchy
⤷ BC-BW-SRV (Application Component) BW Generation Tool and Set Object
⤷ SODQS (Package) Operational Delta Queue Services
Basic Data
Data Element | ODQ_RETENTION_TIME |
Short Description | Retention Period |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ODQ_RETENTION_TIME | |
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 11 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Retn. Per. |
Medium | 18 | Retention Period |
Long | 20 | Retention Period |
Heading | 10 | Retn. Per. |
Documentation
Definition
Retention Period for Data in the Delta Queue. 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.
Use
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.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |