SAP ABAP Data Element EMG_CTRLKSV (Generate field to input higher-level migration object)
Hierarchy
☛ FI-CA (Software Component) FI-CA
   ⤷ IS-U-TO-MI (Application Component) Migration
     ⤷ EEMI (Package) IS-U Migration
Basic Data
Data Element EMG_CTRLKSV
Short Description Generate field to input higher-level migration object  
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 Gen.KSMobj 
Medium 15 Gen. KSM ObjFld 
Long 20 Gen. KSM object fld 
Heading 0   
Documentation

Definition

Use

When this field is set, a field is generated for the migration object to be used in the transfer structure for a higher-level object. This generated field can be used to influence the check of the higher-level object in Key and Status Management (KSM).

You have to set this field (that is, the field for entering the higher-level migration object is generated in the transfer structure) when you want to use the automation data to determine which higher-level migration object will be used for the check in Key and Status Management.

Dependencies

The field that is generated in the transfer structure is called o_<field>, where field is the field name of the higher-level object in the automation data structure.

You use this generated o_<field> as follows:

  • If you enter a value in this field, you will override the higher-level migration objects specified in the field rules for Key and Status Management

    In this case, only the entered higher-level migration object is used in Key and Status Management.

  • If you leave this field blank, the higher-level migration objects specified in the field rules will be processed in Key and Status Management.

Procedure

Example

You create master data (such as devices, for example) using different migration objects and the same legacy system key. During device installation, you can determine the higher-level migration object for Key and Status Management in the automation data.

History
Last changed by/on SAP  20050224 
SAP Release Created in 463