SAP Basis

ADM100 Lesson: Trace Options
A short dump is divided into different sections that document the error.
The overview shows which other informationisoutputintheshortdump,
such as contents of data objects, active calls, control structures, and so on.
You can branch to the ABAP Debugger at the termination point from the
short dump view. The following different error situations exist:
• Internal Error
The kernel identifies an error state. In this case, notify SAP.
• Installation and Environment/Resource Error
In this case, an error occurred that was caused by incorrect system
installation or missing resources (such as the database being
shutdown).
• Error in Application Program
Typicalcausesoferrorsare:
– Content of a numerical field not in the correct format.
– Arithmetic overrun.
– An external procedure is not available.
– Type conflict when transferring parameters to an external
procedure.
By default, short dumps are stored in the system for 14 days. The
transaction for managing short dumps is ST22. You can delete short dumps
in accordance with a time specification using the Reorganize function,
whichyoucancallbychoosingGoto → Reorganize. Youcansaveashort
dump without a time limit using the Keep function, which you can choose
under Short Dump → Keep/Release.
If problems that you cannot solve yourself occur with ABAP programs,
you can send an extract of the short dump to SAP. A short dump is the
basis on which the SAP Hotline and remote consulting solve problems.
• If a runtime error occurs, a short dump is generated. You can use
transaction ST22 to analyze this short dump.
• Dump data is stored in the database.
• Dump data can be reorganized.
• Individual short dumps can be flagged for retention.
The short dumps are stored in table SNAP. If there are too many entries
in table SNAP, problems can occur during the reorganization (see SAP
Note 11838). There are different options for deleting short dumps from
table SNAP:
2003/Q3 © 2003 SAP AG. All rights reserved. 539