We have seen the same problem. The user was executing KES1 (which he shouldn't have been, we are in testing for an FS-CD installation). recieved the exact short dump described at the beginning of this thread. Immediately after we say contract account views short dumping with :
The internal system error cannot be fixed by ABAP means only.
You may be able to find a solution in the SAP note system. If you have
access to the SAP note system, try searching for the following terms:
"DDIC_TYPE_INCONSISTENCY" " "
"SAPLTAX1" or "LTAX1TOP"
The termination occurred during generation of the ABAP/4 program "SAPLTAX1".
-
The termination occurred in line 25
of the source code of program "LTAX1TOP" (when calling the editor 250).
The termination was triggered in function "ab_RxDdicTypeError"
of the SAP kernel, in line 1053 of the module
"//bas/700_REL/src/krn/runt/abucutil.c#3".
The internal operation just processed is " ".
Internal mode was started at 20110413071247.
There is an inconsistency in the DDIC structure "KOMP". This means there is
an error in the corresponding Dictionary runtime object (NAMETAB).
The number of components in the structure (NAMETAB component "fldcnt")
is given as 352. However, when all substructures are resolved, and the
actual total number of components is calculated (recursively), the value
is different.
This error was caused by a change being made to the structure "KOMP" or one
of its substructures, and an error occurring during the subsequent
activation. To find out the exact cause of the error, examine the
runtime object of the structure "KOMP" in the Dictionary.
If the program RSDDCHECK is in your system, you can use it check the
structure "KOMP".
found that this program had structure KOMPAKE partially activated
We reactivated the structure KOMPAKE which fixed the error but would like to know if anyone has any idea of a permanent solution to prevent this problem (besides removing all access to transaction KES1)
Bluesky
