SAP ABAP Data Element RSREPAIRFULL (Indicate Full Request as Repair Request)
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSSM (Package) BW: General monitoring and scheduling
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSSM (Package) BW: General monitoring and scheduling
Basic Data
Data Element | RSREPAIRFULL |
Short Description | Indicate Full Request as Repair 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 | Rep. Full |
Medium | 15 | Repair Full |
Long | 22 | Repair Full Request |
Heading | 22 | Repair Full Request |
Documentation
Definition
Use
If you indicate a request in full update mode as a repair request, then it is able to be updated in all data targets. This is also true if they already contain data from initial runs or deltas for this DataSource / source system combination, and they have overlapping selections.
Consequently, a repair request can be updated at any time without checking each DataStore object. The system supports loading in a DataStore object by using the repair request without having to check the data for overlapping or request sequencing. This is because you can also delete selectively without checking a DataStore object.
Note
Posting such requests can lead to duplicate data records in the data target.
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 30A |