GENERAL_EXC_CLEANUP_LEFT 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: & - Text Include (no Short Dump, only Text Module)
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.
The exception must either be prevented or handled in the CLEANUP
block.
To prevent the exception, note the following:
Termination was caused because exception <runtime parameter> was not caught locally in
a CLEANUP block.
The CLEANUP area is in program <runtime parameter>, and its source code begins in line
<runtime parameter> of (include) program <runtime parameter>.
An exception has occurred which is explained in more detail below. This
exception, which is assigned to class '<runtime parameter>', occurred in a CLEANUP
block, but was not caught there. Since the CLEANUP block was processed
due to a previous exception being caught, the new exception would
change the control flow, and program would then not switch to the
handler of the original exception. This is a critical error situation.
Processing has therefore been terminated. The reason for the exception
is:
GENERAL_EXC_CLEANUP_LEFT - general exc cleanup left GENERAL_EXC_APPL_IN_ABAP_EVENT - general exc appl in abap event GENERAL_ENVIRONMENT - general environment FUNC_PARM_IS_NOT_SEQUENCE_OF_C - func parm is not sequence of c FREE_BUFFER_ILLEGAL_POINTER - free buffer illegal pointer FREE_BUFFER_ILLEGAL_HEADER - free buffer illegal header