CALL_FUNCTION_NOT_FOUND

Since January, some data missing in EWA report (e.g. performance data), and I found some short dump in ST22 with CALL_FUNCTION_NOT_FOUND. I found in source systems and those data capture successfully. How can I let the SolMan read those information back and generate EWA reports in normal?
Runtime Errors         CALL_FUNCTION_NOT_FOUND
       Occurred on     14.04.2008 at 02:22:43
Function module "SMY_GET_SDCC_INPUT" not found.
What happened?
The function module "SMY_GET_SDCC_INPUT" was called, but cannot be
found in the Function Library.
Error in ABAP application program.
The current ABAP program "SAPMSSY1 " had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
The program "SAPMSSY1 " contains a CALL FUNCTION statement. The name
of the function module to be called is "SMY_GET_SDCC_INPUT".
No function module exists with the name "SMY_GET_SDCC_INPUT".
All function modules are stored in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
   to upper/lower case and underscores ("_")
b) Transport error
c) If an enqueue/dequeue module has been used, the lock object
   may not have been activated (ABAP Dictionary)
   may not have been activated (ABAP Dictionary).
How to correct the error
Check the last transports to the R/3 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?
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CALL_FUNCTION_NOT_FOUND" C
"SAPMSSY1 " or "SAPMSSY1 "
"REMOTE_FUNCTION_CALL"
Function modules with names similar to "SMY_GET_SDCC_INPUT":
SNC_GET_MY_INFO
SDU_SPECCAT_GET
SMSY_GET_SYSTEM_INFO
SMSY_GET_HOST
SCAN_INPUT
SDU_SPECCAT_PUT
SMAP_SC_INT_GET_CURSOR
SMSY_GET_CVERS_INFO
SWA_G_CONVERT_INPUT
SMSY_BPR_GET_SYSTEM_INFO
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "itcovssm"
Network address.......... "165.108.188.24"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "2x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "ITCOVSSM"
Database type............ "MSSQL"
Database name............ "SOL"
Database owner........... "dbo"
Character set............ "English_United State"
SAP kernel............... "620"
Created on............... "Feb 9 2004 21:59:19"
Created in............... "NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00"
Database version......... "SQL_Server_7.00 "
Patch level.............. "1340"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "620"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 000
User................ "SAPSYS"
Language key........ "E"
Transaction......... " "
Program............. "SAPMSSY1 "
Screen.............. "SAPMSSY1 3004"
Row of screen....... 2
Information about program making the Remote Function Call (RFC):
System.............. "BQ0"
Database Release.... 620
Kernel Release...... 640
Connection type: 3 (2 = R/2, 3 = R/3, E = External, R = Reg.external)
Call type: "S-" (S = Synchronous, a/A = Asynchronous, T = Transaction)
Client.............. 110
User................ "IA9901"
Transaction......... " (Program: /SDF/SAPLCCMS_DL)"
Function module..... "SMY_GET_SDCC_INPUT"
Call destination.... "SOL"
Source server....... "itcovsbq0_BQ0_00"
Source IP address... "165.108.188.37"
Additional RFC logon information:
Trusted Relation....." "
Logon return code...." "
Trusted return code.." "
Note: Prior to Release 4.0, there was less information available on RFC
calling programs.
Information on where termination occurred
The termination occurred in the ABAP program "SAPMSSY1 " in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1 ".
The termination occurred in line 68 of the source code of the (Include)
program "SAPMSSY1 "
of the source code of program "SAPMSSY1 " (when calling the editor 680).
Source code extract
000380
000390   module %_rfcdia_call output.
000400       "Do not display screen !
000410       call 'DY_INVISIBLE_SCREEN'.
000420       perform remote_function_diacall.
000430   endmodule.
000440
000450   module %_cpic_start.
000460     if sy-xprog(4) = '%RFC'.
000470       perform remote_function_call using rfctype_external_cpic.
000480     else.
000490       call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
000500       perform cpic_call using convid.
000510     endif.
000520   endmodule.
000530
000540
000550   form cpic_call using convid type c.
000560     communication send id convid buffer header.
000570     if sy-subrc eq 0.
000580       perform (sy-xform) in program (sy-xprog).
000590     else.
000600       message a800.
000610     endif.
000620   endform.
000630
000640   form remote_function_call using value(type).
000650     do.
000660   *   test if sy-xprog and sy-xform are set
000670   *   sy-xform = 'quatsch'. sy-xprog = 'quatsch'.
>       call 'RfcImport' id 'Type' field type.
000690       perform (sy-xform) in program (sy-xprog).
000700       rsyn >scont sysc 00011111 0.
000710     enddo.
000720   endform.
000730
000740   form remote_function_diastart.
000750     do.
000760       call 'RfcImport' id 'Type' field rfctype_rfcdia.
000770       perform (sy-xform) in program (sy-xprog).
000780       "Parking position for next request
000790       rsyn >scont sysc 00011111 10.
000800       "ALternativ : Free mode
000810       "COMMIT WORK.
000820       "SYSTEM-CALL FREE MODE 0.
000830     enddo.
000840   endform.
000850
000860   form remote_function_diacall.
000870       sy-xcode = '%_@no@'.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 1
SY-TABIX 0                             SY-DBCNT 0
SY-FDPOS 0                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1                             SY-PFKEY
SY-UCOMM                               SY-TITLE CPIC and RFC Control
SY-MSGTY                               SY-MSGID
SY-MSGNO 000                           SY-MSGV1
SY-MSGV2                               SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
       Program
       Include                                  Line
       Class
     2 FORM         REMOTE_FUNCTION_CALL
       SAPMSSY1
       SAPMSSY1                                    68
     1 MODULE (PBO) %_RFC_START
       SAPMSSY1
       SAPMSSY1                                    30
Chosen variables
     2 FORM         REMOTE_FUNCTION_CALL
       SAPMSSY1
       SAPMSSY1                                    68
%_ARCHIVE
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 80
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 120
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 160
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 200
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 240
                               222222222222222
                               000000000000000
SY-REPID                       SAPMSSY1
                               5454555322222222222222222222222222222222
                               310D339100000000000000000000000000000000
SY-MSGID
                               22222222222222222222
                               00000000000000000000
CONVID
                               22222222
                               00000000
SPACE
                               2
                               0
SY-MSGNO                       000
                               333
                               000
COUNT                          0
                               0000
                               0000
SY-MSGV1
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
SY-MSGV2
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
SY-MSGV3
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
SY-MSGV4
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
%_DUMMY$$
                               2222
                               0000
SYST-REPID                     SAPMSSY1
                               5454555322222222222222222222222222222222
                               310D339100000000000000000000000000000000
TYPE                           3
                               0000
                               3000
SY-XPROG
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
SY-XFORM                       SMY_GET_SDCC_INPUT
                               545544555444544555222222222222
                               3D9F754F3433F9E054000000000000
%_SPACE
                               2
                               0
     1 MODULE (PBO) %_RFC_START
       SAPMSSY1
       SAPMSSY1                                    30
TYPE                           3
                               0000
                               3000
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "link_rfdir" of the SAP
Basis System, specifically in line 165 of the module
"//bas/620/src/krn/runt/ablink.c#5".
The internal operation just processed is "CALY".
The internal session was started at 20080414022243.
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=2432)
When      : 4/14/2008 2:22:43.597
Threads   : 2
Computer Name       : ITCOVSSM
User Name           : SAPServiceSOL
Number of Processors: 2
Processor Type: x86 Family 15 Model 2 Stepping 9
Windows Version     : 5.0 Current Build: 2195
State Dump for Thread Id 97c
eax=7803a770 ebx=03245744 ecx=00000010 edx=00000000 esi=03245744 edi=03245718
eip=77f8850f esp=02ec74dc ebp=02ec7924 iopl=0         nv up ei pl nz ac pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000             efl=00000212
function : <nosymbols>
         77f884ef c21000           ret     0x10
         77f884f2 8bff             mov     edi,edi
         77f884f4 b848000000       mov     eax,0x48
         77f884f9 8d542404         lea     edx,[esp+0x4]          ss:05d8df1b=00000000
         77f884fd cd2e             int     2e
         77f884ff c22800           ret     0x28
         77f88502 8bff             mov     edi,edi
         77f88504 b849000000       mov     eax,0x49
         77f88509 8d542404         lea     edx,[esp+0x4]          ss:05d8df1b=00000000
         77f8850d cd2e             int     2e
         77f8850f c20800           ret     0x8
         77f88512 8bff             mov     edi,edi
         77f88514 b84a000000       mov     eax,0x4a
         77f88519 8d542404         lea     edx,[esp+0x4]          ss:05d8df1b=00000000
         77f8851d cd2e             int     2e
         77f8851f c20800           ret     0x8
         77f88522 8bff             mov     edi,edi
         77f88524 b84b000000       mov     eax,0x4b
         77f88529 8d542404         lea     edx,[esp+0x4]          ss:05d8df1b=00000000
         77f8852d cd2e             int     2e
         77f8852f c21000           ret     0x10
         77f88532 8bff             mov     edi,edi
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
02ec7924 00d9f2e5 03245718 02ec7954 03245718 02ec7948 ntdll!<nosymbols>
02ec79c4 004edcc9 004edc45 7803a770 7803a770 7803a770 disp+work!NTDebugProcess >
> [ntstcdbg.c (388)]
02ec79c8 004edc45 7803a770 7803a770 7803a770 0132f7c4 disp+work!NTStack >
> [dptstack.c (1453)]
02ec79e4 004edc0c 7803a770 00000000 00739ec5 7803a770 disp+work!CTrcStack2 >
> [dptstack.c (327)]
02ec79f0 00739ec5 7803a770 013b527c 30305f59 36313030 disp+work!CTrcStack >
> [dptstack.c (165)]
02ec7a0c 0073388d 00000000 00000001 00000012 01eed480 disp+work!ab_rt100 >
> [abrabax.c (6708)]
02ec7abc 00656e48 013b5294 013b527c 000000a5 013b5210 disp+work!ab_rabax >
> [abrabax.c (952)]
02ec7af4 00656d7b 01a1b44c 00000012 02ec7b18 00000000 disp+work!ab_link >
> [ablink.c (165)]
02ec7b84 007b2c9d 00000001 01a1b44c 00000192 0000185f disp+work!ab_link >
> [ablink.c (358)]
02ec802c 0072993a 02ece67c 02ece688 000000cd 00000000 disp+work!ab_rfcimport >
> [abrfcfun.c (2802)]
02ec8044 0064a967 00000003 50a56c28 00000000 07d97760 disp+work!ab_jcaly >
> [abcall.c (99)]
02ece680 0064a246 00000000 006b3012 00000000 50a56c28 disp+work!ab_extri >
> [abextri.c (389)]
00000000 00000000 00000000 00000000 00000000 00000000 disp+work!ab_extri >
> [abextri.c (201)]
State Dump for Thread Id a94
eax=78008532 ebx=00000103 ecx=7c57b740 edx=00000000 esi=00000000 edi=00000000
eip=77f884ff esp=0531fe70 ebp=0531feb0 iopl=0         nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000             efl=00000246
function : <nosymbols>
         77f884df c20c00           ret     0xc
         77f884e2 8bff             mov     edi,edi
         77f884e4 b847000000       mov     eax,0x47
         77f884e9 8d542404         lea     edx,[esp+0x4]          ss:081e68af=????????
         77f884ed cd2e             int     2e
         77f884ef c21000           ret     0x10
         77f884f2 8bff             mov     edi,edi
         77f884f4 b848000000       mov     eax,0x48
         77f884f9 8d542404         lea     edx,[esp+0x4]          ss:081e68af=????????
         77f884fd cd2e             int     2e
         77f884ff c22800           ret     0x28
         77f88502 8bff             mov     edi,edi
         77f88504 b849000000       mov     eax,0x49
         77f88509 8d542404         lea     edx,[esp+0x4]          ss:081e68af=????????
         77f8850d cd2e             int     2e
         77f8850f c20800           ret     0x8
         77f88512 8bff             mov     edi,edi
         77f88514 b84a000000       mov     eax,0x4a
         77f88519 8d542404         lea     edx,[esp+0x4]          ss:081e68af=????????
         77f8851d cd2e             int     2e
         77f8851f c20800           ret     0x8
         77f88522 8bff             mov     edi,edi
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0531feb0 00e457a7 0000025c 00000000 00000028 04a3fdc8 ntdll!<nosymbols>
0531ff7c 780085bc 00000000 00000028 00000000 04a3fdc8 disp+work!SigILastSig >
> [signt.c (540)]
0531ffb4 7c57b3bc 04a3fdc8 00000028 00000000 04a3fdc8 MSVCRT!<nosymbols>
0531ffec 00000000 00000000 00000000 00000000 00000000 KERNEL32!<nosymbols>
List of ABAP programs affected
| Type| Program                          | Gen. Date Time     | Load Size |
| Prg | SAPMSSY1                         | 31.01.2002 17:21:09 |     18432 |
| Typ | SYST                             | 01.02.2001 17:25:48 |     24576 |
List of internal tables
No dump information available
Directory of Application Tables
Program
Name................ Contents....1........2........3........4........5....+....
SAPMSSY1
SYST                 |\x01\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
Directory of Application Tables (Administrative Information)
Program
Name.......................... Time.......... Length...
SAPMSSY1
SYST                                          00002404
ABAP control blocks CONT
Include                                 Line source code
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl
SAPMSSY1                                   60 message a800.
210 CLEA 00     54
211 CLEA 00     55
212 MESS 00     28
SAPMSSY1                                   62 endform.
213 ENDF 00
214 -
218 -
SAPMSSY1                                   64 form remote_function_call usin
222 PERP 00     1
223 PERP 02
SAPMSSY1                                   65 do.
224 WHIL 00 2
228 WHIL 00 3
232 BRAN 05 Branch to 246
SAPMSSY1                                   68 call 'RfcImport' id 'Type' fie
233 CALY 00 3 56     42    5      5
>>>>> CALY 02     57    P0
SAPMSSY1                                   69 perform (sy-xform) in program
241 xper 02     16     17
243 PERP 80
SAPMSSY1                                   70 rsyn >scont sysc 00011111 0.
244 SYSC 1F
SAPMSSY1                                   71 enddo.
245 BRAX 00 Branch to 228
246 WHIL 00 4
SAPMSSY1                                   72 endform.
250 ENDF 00
251 -
End of runtime analysis

Refer to Note 98458 - SAPMSSY1, CALL_FUNCTION_NOT_FOUND

Similar Messages

XPRA_EXECUTION error in SAPKB70014: CALL_FUNCTION_NOT_FOUND

Hi,
Could anyone give me a hint, please?
Now I'm apllying support packages to ERP 600.
In the XPRA_EXECUTION process of SAPKB70014, an error happens: CALL_FUNCTION_NOT_FOUND.
The current OCS Queue consists of:
   001: SAPKIPYM01
   002: SAPKIPYM02
   003: SAPKIPYM03
   004: SAPKIPYM04
   005: SAPKB70014
   006: SAPKA70014
   007: SAPKW70016
   008: SAPK-60012INFINBASIS
   009: SAPKIPYM05
   010: SAPKB70015
   011: SAPKA70015
   012: SAPKW70017
   013: SAPK-60013INFINBASIS
   014: SAPKIPYM06
   015: SAPKB70016
   016: SAPKA70016
   017: SAPKW70018
   018: SAPK-60014INFINBASIS
Action log:
Import phase 'XPRA_EXECUTION' (2009/12/06, 20:31:13)
Error during executing the tp command 'tp XPA ALL R1S ...'
tp return code: '0012' , tp message: 'A tool used by tp aborted' , tp output:
This is tp version 372.04.40 (release 700, unicode enabled)
standard output from tp and from tools called by tp:
Details of the error situation can also be found in the import logs
Interrupt the import due to an error situation (2009/12/06, 20:32:19)
Display detailed informations concerning the error in phase 'XPRA_EXECUTION'
Abort the import due to an error situation (2009/12/06, 20:42:22)
Import log: SAPKB70014 -> Method Execution
Date        Time      Message
2009/12/06 20:31:14 Job started
2009/12/06 20:31:14 Step 001 started (program RDDEXECL, variant , user ID DDIC)
2009/12/06 20:31:14 All DB buffers of application server ecc60 were synchronized
2009/12/06 20:31:14 ABAP/4 processor: CALL_FUNCTION_NOT_FOUND
2009/12/06 20:31:14 Job cancelled
regards,
Katsumi

Hi, Sunny
As you say, not so many SP should be applied in a time.
I checked these notes.
1101487 - Import of NetWeaver 2004S SP10 fails in XPRA execution phase
1162379 - After Support Package imp: Syntax errors due to ENQUEUE FMs
1381257 - Runtime error CX_SY_DYN_CALL_ILLEGAL_FUNC in transport
However, I did SPAM-update form 700/034 to 700/37 and retried.
The same error did'nt happen somehow...
regards,
Katsumi

CALL_FUNCTION_NOT_FOUND because of wrong reference of XML SOAP Datasource

Hello all,
I have created an XML DataSource (SOAP) and generated an function module XYZ_001.
Due to some changes I have recreated the DataSource and in course of that I have regenerated the function module XYZ_001.
When I execute the infoPackage I get an short dump. After checking st22 I find out that I get an CALL_FUNCTION_NOT_FOUND error because the DataSource refers to function module XYZ_002. This function module was not created. In se37 I can see that there is hust function module XYZ_001.
Why the XML DataSource refers to an other not existing function module? Where can I change the reference or how can I recreate the DataSource/Function module with the correct reference?
The BW release is 3.5. Any help would be great.
Best Regards,
Stefan Leontiadis from Munich/Germany

the message is very clear : Function module "/BOA/ZRFC_READ_TABLE" not found
be sure to have the function on the system where you want to execute it (destination)

CALL_FUNCTION_NOT_FOUND -- its Urgent

Hi,
I am trying to print a document (Packing List). I have created OUTPUT Type "ZPAK" and assigned the Form and Program to this output type, When I try to Print the document through VL02N, I get this Message in my SAP INBOX:
00 671: ABAP/4 Processor: CALL_FUNCTION_NOT_FOUND
Can anyone help.
Regards,
Sagun Desai.

Hi,
I am doing modification in PO sapscirpt,in that
i have display delivery address for each item
format show be like this
item
material description
qty
price
per unit
amount
10
materterial desc
2
EA
2
4
delivery address :
pepsi industry
20,mumbai
like that i have display for all items ,when we use address command ,
i am not able to put vertical line it display like below on
item
material description
qty
price
per unit
amount
10
materterial desc
2
EA
2
4
   delivery address :
   pepsi industry
    20,mumbai
please give me solution how to make table formte to display addres and other things

CALL_FUNCTION_NOT_FOUND dump on RFC eventhough it exists and is active.

Hi,
From SRM system in a BAdi, I am calling a custom function module (RFC) which exists in remote ECC system to make certain checks.
The problem is that when the system calls the customer function module, it gives dump in ST22 as :
Runtime Errors : CALL_FUNCTION_NOT_FOUND
details as below :
What happened?
    The function module "YLN_TAXCODE_SELECTION_IN" is called,
    but cannot be found in the library.
    Error in the ABAP Application Program
    The current ABAP program "YCL_IM_LEN_TAXCODEDET_IN======CP" 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.
I have checked that the above Custom Function module exists and is active in ECC system.
Please give inputs and suggest.
Thanks.

I tried around a little bit:
1) valid function name and valid destination: works fine
2) valid function name and destination 'NONE':
- dumps CALL_FUNCTION_REMOTE_ERROR and CALL_FUNCTION_NOT_FOUND in calling system
3) valid function name and invalid destination:
- dump CALL_FUNCTION_NO_DEST in calling system
4) invalid function name and valid destination:
- dumps CALL_FUNCTION_REMOTE_ERROR in calling system and CALL_FUNCTION_NOT_FOUND in remote system
5) valid function name and empty destination:
- dump CALL_FUNCTION_NOT_FOUND in calling system
Are you sure you don't have a typo in your function name, as in 4), and that you are calling the correct destination (not sure how many you have in your landscape)?
Thomas

ABAP error: CALL_FUNCTION_NOT_FOUND

Hi,
I am getting Message having CALL_FUNCTION_NOT_FOUND after saving my document in ME22N Tcode.
Message i am getting in my inbox:
Transaction.. ME22N
Update key... 80234FDE6D51F11C9004001A6435E8C6
Generated.... 02.06.2009, 05:15:29
Completed.... 02.06.2009, 05:15:31
Error Info... 00 671: ABAP/4 processor: CALL_FUNCTION_NOT_FOUND
Can any one please tell what will be the problem?
My out type also configured correctly with function module routine and program name.
Please reply.
Regards,
Kusuma.

Hi
But wich name for fm are u using?
The name is automatically generated by the system and it can change in every enviroment (dev, test and prod) or in the same enviroment.
So u should run the fm to return the name of fm generated as soon as the smartform is activated:
DATA: FM_NAME TYPE RS38L_FNAM,
      SF_NAME TYPE TDSFNAME.
SF_NAME = <smartform name>.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
           FORMNAME           = SF_NAME
      IMPORTING
           FM_NAME            = FM_NAME
      EXCEPTIONS
           NO_FORM            = 1
           NO_FUNCTION_MODULE = 2
           OTHERS             = 3.
IF SY-SUBRC <> 0.
* ----> No function
ELSE.
* Call smartform
CALL FUNCTION FM_NAME
ENDIF.
Max

ABAP error: Call_function_not_found after saving the document in ME22N Tcod

Hi,
I am getting Message having CALL_FUNCTION_NOT_FOUND after saving my document in ME22N Tcode.
Message i am getting in my inbox:
Transaction..   ME22N
Update key...   80234FDE6D51F11C9004001A6435E8C6
Generated....   02.06.2009, 05:15:29
Completed....   02.06.2009, 05:15:31
Error Info...   00 671: ABAP/4 processor: CALL_FUNCTION_NOT_FOUND
Can any one please tell what will be the problem?
My out type also configured correctly with function module routine and program name.
Please reply.
Regards,
Kusuma.

Hi Karthik,
Thank you for ur reply.
I did not implement any user exit/ badi. Dump is saying that my smarform function module does not exist in the se37 library.
I have excuted my form through se38, that time is working fine. When i tried through output type it is going to dump.
Regards,
Kusuma.

CALL_FUNCTION_NOT_FOUND, garbage in function module name

Hello group
We had a Disaster/Recovery test this weekend.
We have a sync-ed SAP database on a second server which we activated.
SAP starts OK, normal functionality within SAP works fine, however incoming RFC calls seem to fail consistently.
Dumps CALL_FUNCTION_NOT_FOUND occur, with following details :
Function module "ÃÖmÆæmÇÖÖÄâmÔÖåÅÔÅÕãâmÂèmÁÆÆæ" not found.
So, the function module that needs to be called contains garbage in the name.
Any hints on this one ?
I already replaced the kernel with a copy if the Productive kernel, but no change.
Thanks
Jo

Hi Jo,
I converted ÃÖmÆæmÇÖÖÄâmÔÖåÅÔÅÕãâmÂèmÁÆÆæ from EBCDIC back to ASCII and saw the following:
CO_FW_GOODS_MOVEMENTS_BY_AFFW
=> I'm pretty sure, that you did this on a sysem where you had EBCDIC before and either IFS files or profiles are still "somehow EBCDIC" or whatever ...
at least it is surely an EBCDIC-ASCII issue ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

CALL_FUNCTION_NOT_FOUND runtime error with SXMS_GET_METERING_RECORDS

Hi,
we are facing this dump , past one month, any one can please suggest us..
please find error details..
we checked communication between solman and CRP is seems tobe fine..
Runtime Errors         CALL_FUNCTION_NOT_FOUND
Date and Time          15.09.2010 09:30:44
Short text
     Function module "SXMS_GET_METERING_RECORDS" not found.
User and Transaction
    Client.............. 000
    User................ "SAPSYS"    Language Key........ "V"
    Transaction......... " "
    Transactions ID..... "4C8F117F84FC007BE10080000A281E0E"
    Client.............. 700
    User................ "SMD_RFC"
    Transaction......... " "
    Call Program........."SAPLE2E_FUNC"
    Function Module..... "SXMS_GET_METERING_RECORDS"
    Call Destination.... "SM_CRPCLNT700_READ"    Source Server....... "untmvgc170_SMP_01"
What happened?
    The function module "SXMS_GET_METERING_RECORDS" 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.
Error analysis
    The program "SAPMSSY1" contains the CALL FUNCTION statement.
    The name of the function module to be called is "SXMS_GET_METERING_RECORDS".
    No function module exists with the name "SXMS_GET_METERING_RECORDS".
    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).
we found related to this note 1340170

Hi,
The function module SXMS_GET_METERING_RECORDS is only available as of
a certain BASIS SP level of the managed system. As note 1340170 describes
the problem in detail. It also explains the option of deactivating the
E2E_SERVICE_METERING_EXTRACTOR to avoid the short dumps, if updating
the BASIS SP level is not an option for you?
Regards,
Aidan

Dump CALL_FUNCTION_NOT_FOUND for KO02/KO01

Hi Experts.
We created a field exit in DEV and Quality to male a substitution in Settlement rules, but we didnt transport it to production.
In productiuon, ee were creating internal orders with no errors, but today the DUMP "CALL_FUNCTION_NOT_FOUND", exception "CX_SY_DYN_CALL_ILLEGAL_FUNC" occurred when trying to modify or visualize the settlement rule, saying that the FM FIELD_EXIT_AUFKOSTV wasn't found.
We didn't find the requests that could cause this error, but the fact is that the request that created and activated the Field Exit wasnt transported at all to Production, and now something is calling this FM, that really doesn't exist in PRD because we didn't transport (it is not working in test environment.)
Do you know what is the program, routine or something like that, that could cause this error? I found so many notes that I could't get the answer.
Kind Regards
Mayumi

First step is to find the tool name you are trying to execute for which function has not been maintained.
Go to ST22 and enter the dump. Search for TOOLNAME text. Check the value stored against this variable in the dump.
Then we need to maintain the function module name against this TOOLNAME in the table,.
I am not a 100% of which T code to use for this maintenance however - by going through package search I found some like: RZ25. Check if this helps.
Please consult BASIS/ Developer to help with this setup.

RFC sender connect to PI results in ST22 error - CALL_FUNCTION_NOT_FOUND

Hello,
we are doing an RFC connect with a self defined RFC (simply a trigger, a report that calls a FM with a single value) to
PI.
The connectivity is working, sender channel in comm.channel monitoring is in green.
The function module is imported to PI and implemented in the related scenario.
But when we try to start the call to PI this will simply result in an ST22 error on PI with the message
CALL_FUNCTION_NOT_FOUND.
Does anybody here have an idea about that issue?
We are on SAP PI 7.0 SP 15.
Regards
Dirk

> Out implementation:
> We have a TCP IP connection in SM59 of the R/3 with host and service entries for the R/3 system and the registered server prg. name that is the same as in the comm.channel (know about case sensivity).
> The prog. is registered in SMGW on the R/3 now.
This looks perfect!
> In the report where we are calling the function module the destination is the PI connection added as a ABAP Type 3 connection in SM59 of the R/3 system.
Suppose you created TCP IP connection with a name R3_TO_XI, then in the report you have to code it as shown below.
CALL FUNCTION 'your RFC FM name here'
IN BACKGROUND TASK
DESTINATION 'R3_TO_XI'
TABLES
COMMIT WORK.
Update:-
You can also refer this wiki..
https://wiki.sdn.sap.com/wiki/display/XI/RFCtoFILE
Regards,
Sarvesh
Edited by: Sarvesh Singh on Mar 11, 2010 5:04 PM

Error on delta load 2LIS_04_MATNR CALL_FUNCTION_NOT_FOUND

Hello Everyone,
When trying to load delta from 2LIS_04_MATNR i get the below error message.
Please any suggestions on how to fix this?
Function module "/BI0/QI2LIS_04_PEMATNR0002" not found.
The function module "/BI0/QI2LIS_04_PEMATNR0002" was called, but cannot be
found in the Function Library.
The current ABAP/4 program "SAPMSSY1 " had to
one of the statements could not be executed.
If you have access to the note system yourself, use the following
search criteria:
"CALL_FUNCTION_NOT_FOUND"
"SAPMSSY1 " or "SAPMSSY1 "
"XAB_RUN_DRIVER"
Function modules with names similar to "/BI0/QI2LIS_04_PEMATNR0002":
/BI0/QI2LIS_04_PEMATNR0001
/BI0/QI2LIS_04_PEMATNR
/BI0/QI2LIS_04_PECOMP0001
/BI0/QI2LIS_04_PECOMP
/BI0/QI2LIS_03_BF0002
/BI0/QI2LIS_02_CGR0001
/BI0/QI2LIS_02_HDR0001
/BI0/QI2LIS_02_SCL0004
/BI0/QI2LIS_02_SGR0001
/BI0/QI2LIS_02_SCL0002
The termination occurred in the ABAP/4 program "SAPMSSY1 " in
"XAB_RUN_DRIVER".
The main program was "RSFHGEN2 ".
The termination occurred in line 232
of the source code of program "SAPMSSY1 " (when calling the editor 2320).

Hi,
did it ever work? Does it work with a full upload? Did you transport it and does it work in a other system but not in the transported system? What Version are we talking about? Did you activate it from Business Content?
br
Joerg

While executing 'Z' BAPI Runtime error CALL_FUNCTION_NOT_FOUND has occurred

Dear Friends,
We Customized 'Z' BAPI but not transported to QA yet,
Is it possible to test with QA by fetch QA data by giving RFC target sys: (QA RFC Destination Name)
If I give RFC target sys: (QA RFC Destination), I am getting Runtime error CALL_FUNCTION_NOT_FOUND has occurred.
How to resole this....
What is method to check this customized BAPI with different server...../
It is working fine for Standard BAPI.
Regards

But you should be able to call it in the DEV system from QA. This will prove that the RFC part works.
Rob

Run Time Error "CALL_FUNCTION_NOT_FOUND"

Hi Friends,
I am not able to create Material Master Record in Material Master Table due to Run time Error " CALL_FUNCTION_NOT_FOUND"
The Following information found in the error screen,
Short text :
"CRM_GET_TRANSFER_STRUCNT" not found.
what happend:
The Function Module "CRM_GET_TRANSFER_STRUCNT" is called,but cannot be found in the library.
Error in the ABAP Application program
The Current ABAP Program "SAPLCRMO" had to be terminated because it has come across a statement that unfortunately cannot be excuted.
Thanks
Anver

open SAPLCRMO with SE38 find the place where the "CRM_GET_TRANSFER_STRUCNT" is called.
Check then this program part if it was modified in your company or if it is standard SAP coding.
then either talk to the modifier, or open a message a SAP.
(I dont find "CRM_GET_TRANSFER_STRUCNT" as function module in my system, and I dont have a call of this FM in my SAPLCRMO program)

Run-time error "CALL_FUNCTION_NOT_FOUND" occurred

Hi everyone:
I am proving an interface from a ficticious R/3 system to XI, but there is a problem when connecting with XI.
The outbound channel(sender to XI) is not created in the directory because of from a R/3 service you dont need to create one. In the system log of XI(sm21) appears this error log:
12:58:00 DIA 000 100 XIRWBUSER         R68 Perform rollback
12:58:00 DIA 000 100 XIRWBUSER         AB0 Run-time error "CALL_FUNCTION_NOT_FOUND" occurred
12:58:00 DIA 000 100 XIRWBUSER         AB1 > Short dump "060320 125800 slde1s30 XIRWBUSER " generated
CAN SOMEBODY HELP ME PLEASE????

Hi Alvaro,
you have to import a RFC to IB Repository, where it is to use as Outbound-Interface.
Call (asynchronous) at R/3 side with
CALL FUNCTION 'myFunction'
DESTINATION 'myDestination'
IN BACKGROUND TASK
... "parameters
COMMIT WORK.
Regards,
Udo

CALL_FUNCTION_NOT_FOUND

Similar Messages

Maybe you are looking for