CALL_DIALOG_MNNEXT_FAILED 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.
The cause of the paging shortage should be resolved (too little space for SAP paging installed or excessive requests made by users).
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.
Name of current parameter: <runtime parameter>.
No paging area available for list of return parameters.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
There was probably no more space in SAP paging for the list of
return parameters in the CALL DIALOG statement.
Please see runtime error for more details about the possible cause of this runtime error and how it could be avoided.
CALL_DIALOG_MNNEXT_FAILED - call dialog mnnext failed CALL_DIALOG_MFREE_FAILED - call dialog mfree failed CALL_DIALOG_ILLEGAL_EXPORTMODE - call dialog illegal exportmode CALL_DIALOG_ILLEGAL_CODE - call dialog illegal code CALL_DIALOG_DATAAREA_NOT_EMPTY - call dialog dataarea not empty CALL_DIALOG_CONTAINER_MISSING - call dialog container missing