CALL_TRANSACTION_MSG_NO_PAGING 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 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.
Error in internal storage administration (ABAP-MEMORY)
Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.
In the current program <runtime parameter>, an administration line was supposed to be
allocated in the global paging, but no more lines were available.
-
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
This is due to an error in the internal MEMORY administration.
CALL_TRANSACTION_MSG_NO_PAGING - call transaction msg no paging CALL_TRANSACTION_LOCKED - call transaction locked CALL_TRANSACTION_IS_MENU - call transaction is menu CALL_TRANSACTION_FAILED - call transaction failed CALL_SYSTEM_DISABLED - call system disabled CALL_RPERF_SLOGIN_READ_ERROR - call rperf slogin read error