SAP ABAP Data Element EMG_CONVOBJECT (Conversion object)
Hierarchy
☛
FI-CA (Software Component) FI-CA
⤷
IS-U-TO-MI (Application Component) Migration
⤷
EEMI (Package) IS-U Migration
FI-CA (Software Component) FI-CA⤷
IS-U-TO-MI (Application Component) Migration⤷
EEMI (Package) IS-U Migration
Basic Data
| Data Element | EMG_CONVOBJECT |
| Short Description | Conversion object |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EMG_CONVOBJECT | |
| Data Type | CHAR | Character String |
| Length | 15 | |
| Decimal Places | 0 | |
| Output Length | 15 | |
| Value Table | TEMCNV |
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 | Conv. obj. |
| Medium | 15 | Conversion obj. |
| Long | 20 | Conversion object |
| Heading | 16 | Conversion obj. |
Documentation
Definition
A conversion object defines a unique mapping rule of discrete input values to output values during the IS-U migration.
Use
A conversion object can be used in several field rules during IS-U migration. This ensure that identical fields are always supplied with data in the same manner.
Procedure
Users maintain the individual values of a conversion object. This is part of the migration Customizing.
Example
During a RIVA migration, the two-digit company code of the R/2 system has to be mapped to the four-digit company code of the R/3 System.
For example, you can determine that "01" will be mapped to "0010", "02" to "0020", and so on.
Dependencies
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
