Hierarchy
⤷ IS-U-TO-MI (Application Component) Migration
⤷ EEMI (Package) IS-U Migration
Basic Data
Data Element | EMG_D_UBER |
Short Description | Automation data field filled with KSM value |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | EMG_CHECK | |
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 | Via KSM |
Medium | 15 | Via KSM |
Long | 20 | Via KSM |
Heading | 8 | Via KSM |
Documentation
Definition
Selection of the processing type "Values from KSM".
Use
Exactly one processing type must be specified for each field of the automation data of a migration object.
The field selected in this way is supplied with data from key and status management during the data import. The value transferred from the legacy system is interpreted in this field as the key of the higher-level migration object in the data model.
The specified key must exist in key and status management, meaning that the data has already been created in the IS-U database. If the key is not contained in key and status management, an error message is issued and import processing for the current data record is cancelled.
Procedure
Examples
Dependencies
The field is added to the customer structure, but is set to a field length of 30 characters and field type CHAR (format of the legacy system key).
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |