INCL_NOT_ENOUGH_PAGING SAP ABAP Runtime Error incl not enough paging

INCL_NOT_ENOUGH_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: & - 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.

INCL_NOT_ENOUGH_PAGING ABAP Runtime Error

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

You can use transaction SM04 and then choose Goto -> Memory to display an overview of roll memory usage and paging memory usage by the active users and their transactions. Clarify whether either this program or another one is using too much memory.

The system log shows you more information about the current termination. Check whether an unexpected recursion has occurred. Determine whether the error also occurs when the data volume is low. Check the profile (parameter "rdisp/PG_MAXFS", -> Installation Guide).
Is the disk or file system where the paging file is located too full to be extended, even if the size specified in the profile has not been reached? Is the operating system configured so that files can actually be this large?

The ABAP processor saves various types of data in SAP Paging memory:

(1) Datencluster (EXPORT ... TO MEMORY ...)
(2) Parameters when calling programs (SUBMIT REPORT ...), dialog modules (CALL DIALOG ...) and transactions (CALL TRANSACTION USING ...)
(3) Macros defined internally in programs (DEFINE ...)

Wherever programs cause an overflow in SAP Paging, the relevant statements should therefore be checked.

The EXPORT statement is particularly critical, especially if many large internal tables are written to internal memory, possibly using different IDs. Include: Paging area full. Please see runtime error for more details about the possible cause of this runtime error and how it could be avoided.

To process requests, the SAP system has an area for SAP Paging. Distribution amongst users is variable. You can define the size of the area in the system profile.

The new block requested in the SAP paging area is no longer available. In the current program, memory has been requested from SAP Paging. This request could not be complied with.