Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BW-SRV (Application Component) BW Generation Tool and Set Object⤷
SODQS (Package) Operational Delta Queue Services
Basic Data
| Data Element | ODQ_STATUS_ICON |
| Short Description | Status |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ODQ_STATUS_ICON | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | Status |
| Medium | 15 | Status |
| Long | 20 | Status |
| Heading | 3 | St. |
Documentation
Definition
Possible Statuses of an Extraction Request
@6Q@ Extraction scheduled:
With this status, an extraction request is started.
@9Y@ Extraction is running:
Before the background job starts extraction, it sets this status.
@9O@ Extraction failed:
This status is set if errors occur during extraction.
@9P@ Extraction successful:
This status is set if extraction is completed without errors.
@0V@ Confirmed:
This status is inherited by the composite request (see below).
@0W@ Invalid:
This status is set if extraction of data changes fails and needs to be repeated.
Possible Statuses of a Composite Request:
A composite request consolidates the statuses of its extraction requests.
@9P@ Extraction successful:
If extraction is required because the queue is provided with data changes directly from the application, the composite request starts directly in this status.
@6Q@ Extraction scheduled:
If all extraction requests in a composite request are scheduled, this status is set for the composite request.
@9Y@ Extraction is running:
As soon as a background job starts extracting, it sets this status for the composite request. This status will be kept until all extractions have finished with status Extraction successful or Extraction failed.
@9P@ Extraction successful:
If all extractions have completed with status Extraction successful, this status is set for the composite request.
@9O@ Extraction failed:
If one or more of the extractions have completed with status Extraction failed, this status is set for the composite request.
@0V@ Confirmed:
Once the data has been transferred, the subscriber can confirm a composite request with status "Extraction successful". The composite request then has status "Confirmed". This status is passed on to the extraction requests.
@0W@ Invalid:
If the data could not be transferred, the subscriber can cancel a composite request with status "Extraction failed" or "Extraction successful". The composite request then has status "Invalid". This status is passed on to the extraction requests.
Note:
To complete a composite request, you can also set statuses @0V@ Confirmed and @0W@ Invalid for other subscribers in the Delta Queue Monitor.
Once the retention period has elapsed, a periodic background jobs deletes all completed requests from the delta queue.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 702 |
