Hierarchy
PI_BASIS (Software Component) Basis Plug-In⤷
BC-BW (Application Component) BW Service API⤷
RSU0 (Package) BW Service API: Data Transfer
Basic Data
| Data Element | RODMUPDMOD |
| Short Description | BW Delta Process: Record Mode |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RODMUPDMOD | |
| 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 | RecordMode |
| Medium | 15 | Record Mode |
| Long | 20 | Record Mode |
| Heading | 1 | R |
Documentation
Definition
This attribute describes how a record is updated in the delta process. The various delta processes support different combinations of the seven possible characteristic values. If a DataSource implements a delta process that uses several characteristic values, the record mode must be a part of the extract structure and the name of the corresponding field has to be entered in the DataSource (ROOSOURCE-INVFIELD).
The seven characteristic values are as follows:
' ': The record delivers an after image.
The status is tranferred after something is changed or added. You can update the record into an IncoCube only if the corresponding before image exists in the request.
'X': The record delivers a before image
The status is transferred before data is changed or deleted.
All record attributes that can be aggregated have to be transferred with a reverse +/- sign. The reversal of the sign is carried out either by the extractor (default) or the Service API. In this case, the indicatorField is inverted in case of cancellationmust be set in the DataSource for the relevant extraction structure field.
These records are ignored if the update is a non-additive update of a DataStore object.
The before image is complementary to the after image.
'A': The record delivers an additive image.
For attributes that can be aggregated, only the change is transferred. For attributes that cannot be aggregated, the status after a record has been changed or created is transferred. This record can replace an after image and a before image if there are no non-aggregation attributes or if these cannot be changed. You can update the record into an InfoCube without restriction, but this requires an additive update into a DataStore object.
'D': The record has to be deleted.
Only the key is transferred. This record (and its DataSource) can only be updated into a DataStore object.
'R': The record delivers a reverse image.
The content of this record is the same as the content of a before image. The only difference is with a DataStore object update: Existing records with the same key are deleted.
'N': The record delivers a new image.
The content of this record is the same as for an after image without a before image. When a record is created, a new image is transferred instead of an after image.
The new image is complementary to the reverse image.
' Y':The record is an update image.
This kind of record is used in the change log of a Data Store object in order to save the value from the update. This is for a possible rollback and roll- forward for key figures with minimum or maximum aggregation. This record also has the update value for characteristics (in this case, it is the same as the after image).
Null values are stored for key figures with totals aggregation. An update image is only required when the value from the update is smaller or larger than the before image for at least one key figure with minimum or maximum aggregation.
Table RODELTAM determines which characteristic values a delta process uses (columns UPDM_NIM, UPDM_BIM, UPDM_UIM, UPDM_AIM, UPDM_ADD, UPDM_DEL and UPDM_RIM). The table has to ensure that only meaningful combinations of the above values are used within a delta process.
When extracting in the Delta update mode in the extracted records for the record mode, a DataSource that uses a delta process can deliver only those characteristic values that are specified in the delta process.
History
| Last changed by/on | SAP | 20080415 |
| SAP Release Created in |
