SAP ABAP Data Element MIGMODE (Migration mode)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
Data Element | MIGMODE |
Short Description | Migration mode |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MIGMODE | |
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 | Mode |
Medium | 15 | Migration mode |
Long | 20 | Migration mode |
Heading | 1 | M |
Documentation
Definition
The migration mode determines the way in which data is updated in the receiver table.
Three modes are currently supported:
- Mode 1
The system assumes that no summarization takes place when the data is converted (1:1 conversion of the data).
The receiver table must not contain any data that could be overwritten during the conversion because the system will otherwise cancel processing with a runtime error.
This is the fastest type of conversion. - Mode 2
The system assumes that a summarization takes place when the data is converted (N:1 conversion of the data).
The receiver table must not contain any data that could be overwritten during the conversion because the system will otherwise cancel processing with a runtime error.
This is the second fastest type of conversion. - Mode 3
The system assumes that data already exists in the receiver table and the new data is to be added to this existing data.
This is the slowest type of conversion.
Example
- Mode 1:
Line item tables can almost always be converted in this way because they have a unique key due to the document number and document line; a summarization cannot therefore take place.
If you are certain that no summarization can take place during the conversion of the summary tables, you can also convert these tables using this method. - Mode 2:
The summary tables will normally be summarized during the migration from R/2 to R/3. In this case, you must use mode 2. - Mode 3:
You can above all use this mode if you are performing a gradual migration, that is, if you want to accumulate the data of the summary table.
It is not recommended to use this type of processing for line items.
History
Last changed by/on | SAP | 19940827 |
SAP Release Created in | 470 |