Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM-DST (Application Component) Data Staging⤷
RSSM (Package) BW: General monitoring and scheduling
Basic Data
| Data Element | RSSDL65 |
| Short Description | Do not delete if routine is sorting the request |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Routine |
| Medium | 15 | Routine |
| Long | 22 | Routine |
| Heading | 33 | Routine |
Documentation
Definition
If you set this indicator, existing requests are deleted from the InfoCube when the new request and the request to be deleted meet the deletion selection conditions.
No requests are deleted if a routine sorts the request you want to delete. Requests are sorted by deleting them from internal table l_t_request_to_delete .
Internal table l_t_request_to_delete is based on DDIC structure rsreqdelstruc. In this internal table, all requests that are to be deleted are transferred to the routine. Only those requests that are returned in the internal table are deleted.
In the routine, you can delete individual requests from this table or add new ones (it is sufficient to fill the request number RNR). All requests in this table are then deleted from the InfoCube for which the routine was created, if possible.
The routine is the last coding route before deletion (it only checks whether the request canno be deleted because it is aggregated or compressed).
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in |
