Symptom
The short dump contains the message ABAP/4 runtime error DDIC_TYPELENG_INCONSISTENT. You will be getting the dump everything you executing transaction code SM66, ST03N.
Inconsistency in length of DDIC data type "SWN*".
Caused
You are implementing kernel upgrade from 700 to 720.
Solution
1. Refer to SAP Note 1610716, 1229062 & 1222907.
2. Execute transaction code SNOTE. Download the SAP Note 1610716. If SAP Note 1222907 is not active in your system, it will automatically download for you.
3. Implement the SAP Note, create the transport and run the report RUT_NOTE_1610716. For the first time, execute the report in check mode in background using transaction code SE38. You will get the output something like below,
Program start============================================================ Report RUT_NOTE_1610716 ========================================================================= Process..................: ARADAEMCICI_12 User.....................: ITSITI Date, time...............: 22.10.2013, 11:47:35 Platform.................: CUSTOMER-DEV(700)/MSSQL/WindowsNT/ARADAEMCICI Tool.....................: BATCH/RUT_NOTE_1610716 Log......................: T, NOTE1610716_20131022114735 Program parameters: Task.....................: Check and correct nametab alignment PCHECK...................: X REPAIR...................: space ========================================================================= ADBOS_ECP_S_GUI_KIS1_EXT: Include EXTENDED_VALUES has wrong alignment. CMAC_FKKEPOS: Include .INCLUDE_29 has wrong alignment. EECIC_OBJ_LIST_1: Include .INCLUDE_23 has wrong alignment. EECIC_OBJ_LIST_2: Include .INCLUDE_29 has wrong alignment. EEDEREGMAOP: Include .INCLUDE_29 has wrong alignment. FKKCLM: Include .INCLUDE_29 has wrong alignment. FKKEPOS: Include .INCLUDE_28 has wrong alignment. FKKEPOSS: Include .INCLUDE_8 has wrong alignment. FKKEPOSSUM_ALL: Include .INCLUDE_1 has wrong alignment. Summary of the checks: 303452 types checked. 9 errors found. Date, time...............: 22.10.2013, 11:49:08 Program end ==============================================================
4. Once completed, you can execute in repair mode. Detail of executions and steps can be referred from SAP Note 1610716.
========================================================================= All inconsistencies repaired. Return code..............: 0 Date, time...............: 22.10.2013, 11:59:29 Program end ==============================================================
5. You can try to execute transaction code SM66 and ST03N again.
