SET_PARAMETER_MEMORY_OVERFLOW SAP ABAP Runtime Error set parameter memory overflow

SET_PARAMETER_MEMORY_OVERFLOW 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.

SET_PARAMETER_MEMORY_OVERFLOW ABAP Runtime Error

The memory available for the parameters can be set using parameter "ztta/parameter_area". This value is preset to 2000 bytes.
If this termination occurs again despite the SAP memory being increased accordingly, try to find out whether the current program is attempting to store too much data. In the ABAP debugger, you can display the SAP memory by choosing "Goto -> System -> System Areas" and specifying area SMEM. Please see memory size 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.

Name of field...............: <runtime parameter>.
Length of field.............: <runtime parameter>.
Content of field..........: <runtime parameter>. No more space in SPA/GPA memory for parameter <runtime parameter>. Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.

When you log off from the SAP system, the session-specific SPA/GPA memory is deleted. When you log on again, you can therefore continue processing with a blank SPA/GPA memory. The SPA/GPA memory has been used up. The size of this memory can be set in the profile. Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.