SAP ABAP Data Element IUUC_FULL_INCREM (Full incrementality)
Hierarchy
☛
DMIS (Software Component) DMIS 2011_1
⤷
CA-EUR (Application Component) European Monetary Union: Euro
⤷
CNV_INC_PROCESSING (Package) incremental processing using DB triggers and logging tables
⤷
⤷
Basic Data
| Data Element | IUUC_FULL_INCREM |
| Short Description | Full incrementality |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLEAN | |
| 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 | full incr. |
| Medium | 15 | full increm. |
| Long | 20 | full increment. |
| Heading | 15 | full increm. |
Documentation
Definition
If this indicator is active, the delta replay can be done in a fully incremental way. For this purpose, the data changes in the sender system are logged with a time stamp, to facilitate a data transfer (delta replay) in multiple stages, whereby each time only those data are transferred that haven't been transferred yet in a previous transfer step. On the downside, this means more effort in the delta replay, as the logging tables are defined in a different way, meaning that in the delta replay, all data from the original table need to be re-read instead of being taken directly from the logging table.
History
| Last changed by/on | SAP | 20141029 |
| SAP Release Created in | 2006_1_620 |