Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KC (Package) Cost Accounting Controlling EIS
Basic Data
| Data Element | CFREPEAT |
| Short Description | Flag: Complete repeat of data transfer |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Retries |
| Medium | 17 | Repeat run |
| Long | 39 | Complete repeat of transfer |
| Heading | 1 | R |
Documentation
Definition
If the flag has not been set, only those values which have not yet been transferred are selected when you repeat a data transfer. When this so-called 'read delta process' is used, you need to define the SAP-EIS transfer rules so that the 'delta' values are added to the existing values.
If the flag has been set, then all data records are selected when you repeat the data transfer, including the values which have already been transferred. To do this, you need to set up the transfer rules so that the newly selected values overwrite the existing values. If values have been cancelled or deleted in the sender application between transfers, you are recommended to delete the data already transferred to EIS before you repeat the entire data transfer. This prevents old data, for combinations of characteristics which no longer exist in the new transfer, from remaining in EIS.
History
| Last changed by/on | SAP | 19970812 |
| SAP Release Created in |
