Runtime Errors PERFORM_NOT_FOUND
Date and Time 03/20/2009 01:31:52
Call (PERFORM) to a non-existent routine.
There exist various options:
Error in the ABAP Application Program
The current ABAP program "RSDBRUNT" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error in the SAP kernel.
The current ABAP "RSDBRUNT" program had to be terminated because the
ABAP processor detected an internal system error.
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.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FORM', was
not caught in
procedure "%_LDB_CALLBACK" "(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:
The program "RSDBRUNT" is meant to execute an external PERFORM,
namely the routine "CB_DDF_GET_KNA1 " of the program "RFITEMAP ", but
this routine does not exist.
This may be due to any of the following reasons:
1. One of the programs "RSDBRUNT" or "RFITEMAP " is currently being developed.
The name "CB_DDF_GET_KNA1 " of the called routine may be incorrect, or
the routine "CB_DDF_GET_KNA1 " is not yet implemented in the program "RFITEMAP
2. If the program SAPMSSY1 is involved in the runtime error, one of
the function modules called via RFC is not flagged as remote-capable.
(see Transaction SE37 Goto -> Administration -> RFC flag)
3. There is an inconsistency in the system. The versions of the
programs "RSDBRUNT" and "RFITEMAP " do not match.
How to correct the error
- Check that transports to the system are complete.
- Conclude any developments already begun ("RSDBRUNT" and/or "RFITEMAP ").
- Check routine names
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
"RSDBRUNT" or "RSDBRUNT"
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
Information on where terminated
Termination occurred in the ABAP program "RSDBRUNT" - in "%_LDB_CALLBACK".
The main program was "RFITEMAP ".
In the source code you have the termination point in line 5433
of the (Include) program "RSDBRUNT".
Error occurred during batch input processing
The termination is caused because exception "CX_SY_DYN_CALL_ILLEGAL_FORM"
procedure "%_LDB_CALLBACK" "(FORM)", but it was neither handled locally nor
in the RAISING clause of its signature.
The procedure is in program "RSDBRUNT "; its source code begins in line
5414 of the (Include program "RSDBRUNT ".
Seems like you are trying to call a FORM...ENDFORM of another program.
In order to catch this exception, use IF FOUND option in your call.
CALL PERFORM(PROGRAM) IF FOUND.
This way it calls the form if it exists else it does nothing and there would be no dump.
Seems like the program you are calling has no PERFORM with name you specified.