GEN_PEXT_DESTROYED SAP ABAP Runtime Error gen pext destroyed

GEN_PEXT_DESTROYED is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: I - Internal Kernel Error

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

GEN_PEXT_DESTROYED ABAP Runtime Error

The error will probably not occur again next time. Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.

Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

An attempt was made to initialize sc_pext in C function <runtime parameter>. sc_pext contained <runtime parameter> elements. The last element, which should actually contain EMPTY_STRING = <runtime parameter> as its end marker, contained <runtime parameter>, meaning that the end marker of sc_pext was destroyed.
To find out the cause, use abap/dimponerror =GEN_PEXT_DESTROYED next time you start the system. Internal error in syntax check: End marker of sc_pext destroyed. Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.

Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.

Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.