Managing Short Dumps
For every runtime error that occurs in an ABAP system a socalled short dump is created in the error log in the SNAP database table. Unless they are intended for retention and marked accordingly, these long texts are automatically released for deletion four weeks after they are generated.
Old short dumps are deleted successively: If a program that is running in a window of the SAP GUI terminates with a runtime error and the short dump is displayed directly, older short dumps are searched for and deleted (maximum 100, for performance reasons). The number of short dumps not intended for retention in an ABAP system is therefore regulated on a regular basis.
Manually Reorganizing Short Dumps
This mechanism does not apply, however, if a runtime error occurs during background processing, an RFC call (including JCo), or an HTTP call. It is therefore also possible to selectively manually delete short dumps from the database. To do this, on the initial screen of the transaction ABAP Dump Analysis (ST22), choose the Goto menu and the Reorganize option.
A selection screen appears, on which you can define the age as of which the short dumps are to be deleted.
Reorganization as Automatically-Scheduled Operation (by the System Administrator)
If you need to regularly perform reorganization operations in a system and want to automate this step, you can schedule the program RSSNAPDL. This program provides the same function as the menu option Reorganize.
You can view the current size of table SNAP at any time by choosing the Statistics option from the Goto menu.
Stopping Short Dumps from Being Automatically Deleted
You can prevent a short dump being automatically deleted. Start the ABAP Dump Analysis (St22) for this and select the related runtime error. Choose 
Runtinme Error 
Save/Release 
from the menu. The short dump is then stored in the database until you revoke the lock using the same function.
See also SAP Note 11838 
.