CALL_DIALOG_NO_CONTAINER 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: O - Resource Shortage
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.
Please see not enough paging 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.
Area <runtime parameter> was requested.
No more paging area available for parameter transfer.
Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.
A CALL DIALOG statement was used to exchange the (EXPORTING and
IMPORTING) parameters via the ABAP/4 memory, which lies
in the SAP paging area. For the current CALL DIALOG statement,
the size of memory had to be increased, but there were no more
blocks in the paging area.
Please see not enough paging for more details about the possible cause of this runtime error and how it could be avoided.
CALL_DIALOG_NO_CONTAINER - call dialog no container CALL_DIALOG_NOT_FOUND - call dialog not found CALL_DIALOG_NAME_TOO_LONG - call dialog name too long CALL_DIALOG_NAMELIST_EMPTY - call dialog namelist empty CALL_DIALOG_MNNEXT_FAILED - call dialog mnnext failed CALL_DIALOG_MFREE_FAILED - call dialog mfree failed