Hi,
As we are getting the dump error as CALL_FUNCTION_NOT_FOUND
Please give a solution as how to correct it?, As we are getting daily..
Function module "/SSF/CALL_SUBROUTINE_RFC" not found.
What happened?
The function module "/SSF/CALL_SUBROUTINE_RFC" is called,
but cannot be found in the library.
Error in the ABAP Application Program
The current ABAP program "SAPMSSY1" 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
administrator.
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
The program "SAPMSSY1" contains the CALL FUNCTION statement.
The name of the function module to be called is "/SSF/CALL_SUBROUTINE_RFC".
No function module exists with the name "/SSF/CALL_SUBROUTINE_RFC".
All function modules are listed in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Pay particular attention to
upper/lower case and underscores ("_").
or
b) Transport error
c) In the case of an enqueue/dequeue module,
the lock object may not have been activated
(ABAP/4 Dictionary).
How to correct the error
Check the last transports to the SAP System.
Is the program "SAPMSSY1" currently being changed?
If an enqueue/dequeue module is involved, is the activation
of the lock object missing in the ABAP/4 Dictionary?
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
keywords:
"CALL_FUNCTION_NOT_FOUND" " "
"SAPMSSY1" or "SAPMSSY1"
"REMOTE_FUNCTION_CALL"
Function modules with names similar to "/SSF/CALL_SUBROUTINE_RFC":
/SDF/CALL_STAPI
/SDF/MON_ROUTING
/SAPPSPRO/CALL_SRM
/BDL/CALL_SDCC
/OSP/UPDATE_ALL_RFC
/SPE/CALL_PROC_IN_NEW_LUW
/SAPPSPRO/CALL_SRM_IN_HTML
Program............. "SAPMSSY1"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "SML"
Database Release.... 702
Kernel Release...... 721
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchronous and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 005
User................ "SOLMAN_BTC"
Transaction......... " "
Call Program........."/SSA/XAD"
Function Module..... "/SSF/CALL_SUBROUTINE_RFC"
Call Destination.... "SM_XXXCLNT500_TMW"
Source Server....... "SAPSOLMAN_SML_00"
Source IP Address... "000.00.000.000"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "SAPMSSY1" - in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 67
of the (Include) program "SAPMSSY1".
Source Code
form remote_function_call using value(type).
data rc type i value 0.
do.
call 'RfcImport' id 'Type' field type.
if sy-xprog = 'JAVA'.
system-call plugin