Show TOC

Function documentationThe rsmemory Report Locate this document in the navigation structure


You can use the rsmemory report to define your memory allocation strategy for work processes. You can specify the memory class assigned to a work process, the extent of the class assigned, and the order in which it is allocated. A distinction is made here between dialog work processes and non-dialog work processes (batch, update, spool).

Note Note

Changes made here only apply to the server on which you are currently logged on, and only remain in effect until the SAP instance is stopped again.

End of the note.


You are familiar with the SAP Memory Management concept and have read section Functions of the SAP Memory Management System.


The SAP system has the following memory classes:

These memory classes are assigned the following values, which are also displayed in the initial screen of the rsmemory report.


Memory Class


Roll Area


Extended Memory (EM)


Private memory (heap)

The initial screen of the report is structured as follows:

This graphic is explained in the accompanying text.

The screen comprises three parts:

  • Quota Dialog

    The allocation strategy for dialog work processes is defined here. You can specify the steps in which each class is allocated memory, and how much memory is allocated.

    Caution Caution

    No entry in the memory class field corresponds to class 0 (roll memory).

    End of the caution.

    The entry here does not have to match the defined memory parameters. If you enter a value for the heap memory in the 4th step that is different from the abap/heaparea_dia parameter, the value entered here takes precedence.

    Note Note

    In this case, 1 byte of roll area is first allocated by a dialog work process (due to technical reasons), and then a maximum of 2 GB of extended memory is available. This does not mean that the work process is assigned too much memory, since the resource is shared by all work processes. If the work process is not assigned any more extended memory, it can allocate another 6.5 MB of roll memory. Then it goes into PRIV mode and allocates heap memory (maximum 2 GB).

    End of the note.
  • Quota Batch/VB/Spool

    As with Quota Dialog the allocation strategy here is specified for non-dialog work processes.

    More information: Allocting Memory for User Contexts (UNIX)

  • Other parameters

    You can change the following memory parameters here for test purposes (these changes only apply until the next server restart):

Displaying the Memory Areas

You can display a list of all the users on the application server, with their respective memory requirements, by choosing   Goto   EM/HEAP Areas  . The used heap memory and extended memory of the user are displayed first, followed by the EM usage according to internal sessions.

This is followed by a history of users who have used more than the MB limit specified by em/stat_log_size_MB.

The available HEAP and EM memory is displayed at the end of the list.

EG Overview

The two pushbuttons EG Overview and EG Dump are used for analysing the extended global memory. This is part of the extended memory available for internal SAP requests. Its size is specified in the em/global_area_MB parameter.


On the initial screen of transaction SE38, enter report rsmemory and choose Execute (Execute) or F8.