Skip to Content
Former Member
Jun 09, 2009 at 04:26 PM

SAP paging overflow when storing data in the ABAP/4 memory.


I am trying to create a data source in BI7.0 in the Datawarehousing Workbench. But along the process when i need to select a view i get an error detailed in the following error file extract: Please go through and assist.


Date and Time 06.06.2009 14:21:35



Short text

SAP paging overflow when storing data in the ABAP/4 memory.



What happened?

The current program requested storage space from the SAP paging area,

but this request could not be fulfilled.

of this area in the SAP system profile.



What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator


You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.



Error analysis

The ABAP/4 runtime system and the ABAP/4 compiler use a common

interface to store different types of data in different parts of

the SAP paging area. This data includes the

ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,

CALL DIALOG and CALL TRANSACTION USING, as well as internally defined

macros (specified with DEFINE).

To store further data in the SAP paging area, you attempted to

allocate a new SAP paging block, but no more blocks were


When the SAP paging overflow occurred, the ABAP/4 memory contained

entries for 20 of different IDs.

Please note:

To facilitate error handling, the ABAP/4 memory was




How to correct the error

The amount of storage space (in bytes) filled at termination time was:

Roll area...................... 8176

Extended memory (EM)........... 13587912

Assigned memory (HEAP)......... 0

Short area..................... " "

Paging area.................... 40960

Maximum address space.......... " "

By calling Transaction SM04 and choosing 'Goto' -> 'Block list',

you can display an overview of the current roll and paging memory

levels resulting from active users and their transactions. Try to

decide from this whether another program requires a lot of memory

space (perhaps too much).

The system log contains more detailed information about the

termination. Check for any unwanted recursion.

Determine whether the error also occurs with small volumes of

data. Check the profile (parameter "rdisp/PG_MAXFS", see

Installation Guidelines).

Is the disk or the file system that contains the paging file

full to the extent that it cannot be increased, although it has

not yet reached the size defined in the profile? Is the

operating system configured to accommodate files of such a


The ABAP processor stores different types of data in the SAP

paging area. These include:

(1) Data clusters (EXPORT ... TO MEMORY ...)

(2) Parameters for calling programs (SUBMIT REPORT ...),

Dialog modules (CALL DIALOG ...) and transactions


(3) Internally defined program macros (DEFINE ...)

Accordingly, you should check the relevant statements in a program

that results in an overflow of the SAP paging area.

It is critical when many internal tables, possibly with

different IDs, are written to memory (EXPORT).

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following





If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File


2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File


3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More


4. Details about the conditions under which the error occurred or which

actions and input led to the error.