Message Number list used by SAP ABAP Class CL_MDG_MDF_CM_MAP (Change Managment: Check and Convert)
SAP ABAP Class
CL_MDG_MDF_CM_MAP (Change Managment: Check and Convert) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | MDG_MDF8 - 120 | Internal error: Result of simulation cannot be displayed | ||
| 2 | MDG_MDF8 - 128 | Conversion unnecessary; the existing table has no data | ||
| 3 | MDG_MDF8 - 127 | No target table specified | ||
| 4 | MDG_MDF8 - 126 | RFC conversion exits are not supported | ||
| 5 | MDG_MDF8 - 125 | Conversion may contain errors due to use of a conversion exit | ||
| 6 | MDG_MDF8 - 124 | Conversion can cause inconsistent database tables! | ||
| 7 | MDG_MDF8 - 123 | Conversion damages unique indexes | ||
| 8 | MDG_MDF8 - 122 | Internal error: Tables cannot be interpreted | ||
| 9 | MDG_MDF8 - 121 | Internal error during building of GUI objects | ||
| 10 | MDG_MDF8 - 101 | Changing &1 causes duplicate keys &2 | ||
| 11 | MDG_MDF8 - 112 | Characteristic values of the characteristic changes cannot be converted | ||
| 12 | MDG_MDF8 - 111 | Conversion generates inconsistent SID tables or check tables | ||
| 13 | MDG_MDF8 - 108 | Renaming of fields is not possible | ||
| 14 | MDG_MDF8 - 107 | New key fields are not possible | ||
| 15 | MDG_MDF8 - 105 | Field &1 &2 cannot be converted; data types are incompatible | ||
| 16 | MDG_MDF8 - 104 | Field &1 will not be used | ||
| 17 | MDG_MDF8 - 103 | Field &1 cannot be converted without loss of data: &2 | ||
| 18 | MDG_MDF8 - 102 | Deleted field &1 contains various data &2 |