Skip to Content
Former Member
Jul 28, 2010 at 01:22 PM

Tcode SM52 shows Runtime error.



This is newly installed CRM server on windows 2003, oracle 10i, basis rel 701, kernel patch level 55

Runtime error shows once executing SM52 FOR VIRTUAL MACHINE CONTAINer. Please check the below runtime error.



Date and Time 28.07.2010 16:37:46



Short text

Divide by 0 (type F) In program "RSM52000_ALV"



What happened?

Error in the ABAP Application Program

The current ABAP program "RSM52000_ALV" had to be terminated because it has

come across a statement that unfortunately cannot be executed.



What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system


Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.



Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_ZERODIVIDE', was not caught in

procedure "CREATE_HEADER" "(FORM)", nor was it propagated by a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

In the current program "RSM52000_ALV", an arithmetic operation ('DIVIDE',

'/', 'DIV' or 'MOD') attempted to use operands of type F to divide

by 0.

The operands involved were:

1. Operand: 100

2. Operand: 0

(If "?" is output, the value of the operand can no longer be




How to correct the error

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

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



"RSM52000_ALV" or "RSM52000_ALV"


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.

The exception must either be prevented, caught within proedure

"CREATE_HEADER" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following: