Re: CALL_FUNCTION_NOT_FOUND

aneesh_shamsudeen · ‎2015 May 11

Hi experts,

I am getting daily 100-200 dumps in R3 production system in tcode-ST22. The cause of error regarding the dump is CALL_FUNCTION_NOT_FOUND in SAPMSSY1 .The short text is shows as Function module "刀䘀䌀开䐀䔀匀吀开匀䠀䤀倀"" is called but not found in library. Plesae advise on this

Regards,

Aneesh S

matt · ‎2015 May 11

What's the call stack?

aneesh_shamsudeen · ‎2015 May 11

Hi Matthew,

Please find the dump error detail

Runtime Errors CALL_FUNCTION_NOT_FOUND

Date and Time 11.05.2015 10:26:50

----------------------------------------------------------------------------------------------------

|Short Text |

| Function module "##############" not found. |

----------------------------------------------------------------------------------------------------

|What happened? |

| The function module "##############" 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 "##############". |

| |

| No function module exists with the name "##############". |

| 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 "##############": |

| |

| 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 |

| (Unconverted)". |

| |

| 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 |

| (Unconverted)". |

| |

| 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 |

| Utilities->Upload/Download->Download". |

| |

| 4. Details about the conditions under which the error occurred or which |

| actions and input led to the error. |

| |

----------------------------------------------------------------------------------------------------

|System environment |

| SAP-Release 700 |

| |

| Application server... "r3pcilh" |

| Network address...... "172.16.22.180" |

| Operating system..... "SunOS" |

| Release.............. "5.10" |

| Hardware type........ "sun4v" |

| Character length.... 16 Bits |

| Pointer length....... 64 Bits |

| Work process number.. 30 |

| Shortdump setting.... "full" |

| |

| Database server... "sapr3pz2" |

| Database type..... "ORACLE" |

| Database name..... "R3P" |

| Database user ID.. "SAPR3P" |

| |

| Terminal................. 172 |

| |

| Char.set.... "C" |

| |

| SAP kernel....... 720 |

| created (date)... "Mar 31 2014 22:21:18" |

| create on........ "SunOS 5.9 Generic_122300-28 sun4u" |

| Database version. "OCI_102, 10.2.0.5.0, V3, default" |

| |

| Patch level. 611 |

| Patch text.. " " |

| |

| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |

| SAP database version. 720 |

| Operating system..... "SunOS 5.9, SunOS 5.10, SunOS 5.11" |

| |

| Memory consumption |

| Roll.... 0 |

| EM...... 4189800 |

| Heap.... 0 |

| Page.... 0 |

| MM Used. 1203392 |

| MM Free. 2983760 |

----------------------------------------------------------------------------------------------------

|User and Transaction |

| Client.............. 500 |

| User................ "DISPOTOOL" |

| Language Key........ "E" |

| Transaction......... " " |

| Transactions ID..... "5550AF6C03026260E1000000AC10158D" |

| |

| Program............. "SAPMSSY1" |

| Screen.............. "SAPMSSY1 3004" |

| Screen Line......... 2 |

| |

| Information on caller of Remote Function Call (RFC): |

| System.............. "########" |

| Database Release.... " " |

| Kernel Release...... " " |

| 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.............. "###" |

| User................ "############" |

| Transaction......... " " |

| Call Program........." " |

| Function Module..... "##############" |

| Call Destination.... " " |

| Source Server....... " " |

| Source IP Address... " " |

| |

| 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 Extract |

----------------------------------------------------------------------------------------------------

|Line |SourceCde |

----------------------------------------------------------------------------------------------------

| 37|endmodule. |

| 38| |

| 39|module %_rfcdia_call output. |

| 40| "Do not display screen ! |

| 41| call 'DY_INVISIBLE_SCREEN'. |

| 42| perform remote_function_diacall. |

| 43|endmodule. |

| 44| |

| 45|module %_cpic_start. |

| 46| if sy-xprog(4) = '%RFC'. |

| 47| perform remote_function_call using rfctype_external_cpic. |

| 48| else. |

| 49| call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid. |

| 50| perform cpic_call using convid. |

| 51| endif. |

| 52|endmodule. |

| 53| |

| 54| |

| 55|form cpic_call using convid type c. |

| 56| communication send id convid buffer header. |

| 57| if sy-subrc eq 0. |

| 58| perform (sy-xform) in program (sy-xprog). |

| 59| else. |

| 60| message a800. |

| 61| endif. |

| 62|endform. |

| 63| |

| 64|form remote_function_call using value(type). |

| 65| data rc type i value 0. |

| 66| do. |

|>>>>>| call 'RfcImport' id 'Type' field type. |

| 68| if sy-xprog = 'JAVA'. |

| 69| system-call plugin |

| 70| id 'JAVA' value 'FORW_JAVA' |

| 71| id 'RC' value rc. |

| 72|* if there is no rollout on the JAVA side which |

| 73|* rolls both, JAVA and ABAP, we return to the |

| 74|* C-Stack and reach this point |

| 75| |

| 76|* in case there was an rollout, the ABAP-C stack is lost |

| 77|* and we jump direkt to this point |

| 78| |

| 79|* here we trigger the rollout on this Abap side with |

| 80|* the following statement |

| 81| system-call plugin |

| 82| id 'JAVA' value 'ROLL_OUT' |

| 83| id 'RC' value rc. |

| 84| else. |

| 85| perform (sy-xform) in program (sy-xprog). |

| 86| rsyn >scont sysc 00011111 0. |

----------------------------------------------------------------------------------------------------

|Contents of system fields |

----------------------------------------------------------------------------------------------------

|Name |Val. |

----------------------------------------------------------------------------------------------------

|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| |

|SY-MODNO|0 |

|SY-DATUM|20150511 |

|SY-UZEIT|102649 |

|SY-XPROG| |

|SY-XFORM|############## |

----------------------------------------------------------------------------------------------------

|Active Calls/Events |

----------------------------------------------------------------------------------------------------

|No. Ty. Program Include Line |

| Name |

----------------------------------------------------------------------------------------------------

| 2 FORM SAPMSSY1 SAPMSSY1 67 |

| REMOTE_FUNCTION_CALL |

| 1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30 |

| %_RFC_START |

----------------------------------------------------------------------------------------------------

|Chosen variables |

----------------------------------------------------------------------------------------------------

|Name |

| Val. |

----------------------------------------------------------------------------------------------------

|No. 2 Ty. FORM |

|Name REMOTE_FUNCTION_CALL |

----------------------------------------------------------------------------------------------------

|%_DUMMY$$ |

| |

| 0000 |

| 2222 |

| 0000 |

|SY-REPID |

| SAPMSSY1 |

| 0000000000000000000000000000000000000000 |

| 5454555322222222222222222222222222222222 |

| 310D339100000000000000000000000000000000 |

|SYST-REPID |

| SAPMSSY1 |

| 0000000000000000000000000000000000000000 |

| 5454555322222222222222222222222222222222 |

| 310D339100000000000000000000000000000000 |

|HEADER |

| ############ |

| 000000000000 |

|TYPE |

| 3 |

| 0000 |

| 0003 |

|SY-XPROG |

| |

| 0000000000000000000000000000000000000000 |

| 2222222222222222222222222222222222222222 |

| 0000000000000000000000000000000000000000 |

|%_ARCHIVE |

| |

| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|

| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222|

| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|

|RC |

| 0 |

| 0000 |

|SY-XFORM |

| ############## |

| 454454455554450000000000000000 |

| 1263F4534F38900000000000000000 |

| 000000000000002222222222222222 |

| 000000000000000000000000000000 |

|%_SPACE |

| |

| 0 |

| 2 |

| 0 |

----------------------------------------------------------------------------------------------------

|No. 1 Ty. MODULE (PBO) |

|Name %_RFC_START |

----------------------------------------------------------------------------------------------------

|%_PRINT |

| 000 0###|

| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|

| 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000|

| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|

|RFCTYPE_INTERNAL |

| 3 |

| 0000 |

| 0003 |

----------------------------------------------------------------------------------------------------

|Application Calls |

----------------------------------------------------------------------------------------------------

|Index|Calls |

----------------------------------------------------------------------------------------------------

| 1|R=1 T=S S=ALMCPPYMSSVR I=C:\Program Files (x86)\Almarai Company\Al F=ZEDI_DOCUMENT_SEG_STATU|

----------------------------------------------------------------------------------------------------

|Internal notes |

| The termination was triggered in function "link_rfdir" |

| of the SAP kernel, in line 207 of the module |

| "//bas/720_REL/src/krn/runt/ablink.c#2". |

| The internal operation just processed is "CALY". |

| Internal mode was started at 20150511102346. |

----------------------------------------------------------------------------------------------------

|Active Calls in SAP Kernel |

----------------------------------------------------------------------------------------------------

|Lines of C Stack in Kernel (Structure Differs on Each Platform) |

----------------------------------------------------------------------------------------------------

|[0] DoStack2 ( 0xffffffff7fff6c10, 0x0, 0xffffffff7fff6411, 0x10b8f4dc8, 0x35a327c, 0x103bf0720 ),|

|[1] CTrcStack2 ( 0x10b8f4dc8, 0x0, 0x153800, 0x359efbc, 0x103bf0720, 0x2 ), at 0x1006517b0 |

|[2] __1cQrabax_CStackSave6F_v_ ( 0x1e0028, 0x104c00, 0x104c00, 0x103d9c16a, 0x103d9c, 0x10b8f4dc8 |

|[3] ab_rabax ( 0x104c00, 0x103d44000, 0x104f66, 0x2000, 0x1000, 0x103c00 ), at 0x100930f4c |

|[4] __1cKlink_rfdir6FpkHipnFTFDIR_kC_i_ ( 0x103c00, 0xe, 0xffffffff7fff7e04, 0x0, 0x10c4f42e0, 0x1|

|[5] ab_link ( 0x1, 0x107ce5aa0, 0x1a, 0x506c, 0x0, 0x0 ), at 0x100c9959c |

|[6] ab_LinkRfc ( 0x107ce5aa0, 0xe, 0x0, 0xffffffff7fff810e, 0xffffffff7fff82cc, 0xffffffff7fff82cb|

|[7] ab_rfcimport ( 0x0, 0x1c, 0x107c00, 0x107ce5, 0xe, 0x0 ), at 0x10110453c |

|[8] __1cIab_jcaly6F_v_ ( 0x38, 0xfffffff69bd2dec8, 0xfffffff69bd2b4fc, 0x107ed8c88, 0xfffffff69bd2|

|[9] __1cIab_extri6F_i_ ( 0x208c, 0xf4, 0x104f5f, 0x0, 0x0, 0x107d94000 ), at 0x10089e188 |

|[10] __1cJab_xevent6FpkH_i_ ( 0x0, 0x0, 0x0, 0x2f, 0x0, 0xa ), at 0x100955bbc |

|[11] ab_dstep ( 0x0, 0x8, 0xfffffff8ca8bab00, 0xfffffff69bd2b008, 0x0, 0x107db49c0 ), at 0x10088fc|

|[12] dynpmcal ( 0xfffffff8ca8c6c60, 0x0, 0xfffffff8ca8c7cf0, 0x103d441a4, 0x80, 0x16 ), at 0x10067|

|[13] dynppbo0 ( 0xfffffff8ca8c6c60, 0x103c00, 0x103d441a4, 0x1, 0x103d44000, 0xfffffff8ca8c7c70 ),|

|[14] dynprctl ( 0xfffffff8ca8c6c60, 0x0, 0x103ce2dc4, 0x6, 0x1, 0x100677f00 ), at 0x100677adc |

|[15] dynpen00 ( 0x3, 0x103000, 0x1, 0x103d44000, 0x103d44, 0x103c00 ), at 0x100673600 |

|[16] TskhLoop ( 0x103ce2, 0x103d44000, 0x103ce0, 0x10e, 0xffffffff60413e78, 0x103ce0000 ), at 0x10|

|[17] DpMain ( 0x2, 0x107f6c960, 0x2, 0x103ce0000, 0x103ce0, 0x103c00 ), at 0x1002bb788 |

----------------------------------------------------------------------------------------------------

|List of ABAP programs affected |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

| 0|Prg|SAPMSSY1 | 0|11.04.2005|09:27:15| 24576|E |

| 1|Typ|SYST | 0|09.09.2004|14:18:12| 30720| |

----------------------------------------------------------------------------------------------------

|Directory of Application Tables |

----------------------------------------------------------------------------------------------------

|Name Date Time Lngth |

| Val. |

----------------------------------------------------------------------------------------------------

|Program SAPMSSY1 |

----------------------------------------------------------------------------------------------------

|SYST . . : : 00004612 |

| \0\x0001\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0 |

|SY . . : : 00004612 |

| \0\x0001\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0 |

----------------------------------------------------------------------------------------------------

|ABAP Control Blocks (CONT) |

----------------------------------------------------------------------------------------------------

|Index|Name|Fl|PAR0|PAR1|PAR2|PAR3|PAR4|PAR5|PAR6|Source Code |Line |

----------------------------------------------------------------------------------------------------

| 116|CLEA|00|0035| | | | | | |SAPMSSY1 | 60|

| 117|CLEA|00|0036| | | | | | |SAPMSSY1 | 60|

| 118|CLEA|00|0037| | | | | | |SAPMSSY1 | 60|

| 119|MESS|00|001C| | | | | | |SAPMSSY1 | 60|

| 120|ENDF|00|0000| | | | | | |SAPMSSY1 | 62|

| 121|----|00|0000| | | | | | |SAPMSSY1 | 62|

| 122|PERP|00|0001| | | | | | |SAPMSSY1 | 64|

| 123|PERP|02|0000| | | | | | |SAPMSSY1 | 64|

| 124|WHIL|00|0002|0000|0000|0000|0000|0000|0000|SAPMSSY1 | 66|

| 128|WHIL|00|0003|0000|0000|0000|0000|0000|0000|SAPMSSY1 | 66|

| 132|BRAN|05|001E| | | | | | |SAPMSSY1 | 66|

| 133|CALY|00|0003|0038|002A|0005|002B|0000|0000|SAPMSSY1 | 67|

|>>>>>|CALY|02|0000|0039|8000|0000|0000|0000|0000|SAPMSSY1 | 67|

| 141|COMP|00|0002|0010|003A| | | | |SAPMSSY1 | 68|

| 143|BRAF|02|000E| | | | | | |SAPMSSY1 | 68|

| 144|SRFC|01|0000|003A|003B| | | | |SAPMSSY1 | 69|

| 146|SRFC|01|0000|003C|C000| | | | |SAPMSSY1 | 69|

| 148|SRFC|02|0000|0000|0000| | | | |SAPMSSY1 | 69|

| 150|SRFC|01|0000|003A|003D| | | | |SAPMSSY1 | 81|

| 152|SRFC|01|0000|003C|C000| | | | |SAPMSSY1 | 81|

----------------------------------------------------------------------------------------------------

avanida · ‎2015 May 11

Hi Aneesh,

Your function module might be a calling as Remote function and this type of error comes due to RFC fails.

Can you please check the function module is remote enable or not?

Regards

Avanida

aneesh_shamsudeen · ‎2015 May 11

Hi Avanida,

Function module is remote enabled

Regards,

Aneesh S

RaymondGiuseppi · ‎2015 May 11

Look as a wrong call of RFC function. Does the name "ZEDI_DOCUMENT_SEG_STATU" inspires you, did you check the log of recent import in system, did you check recently modified RFC destination (e.g. box Unicode System) ?

Regards,

Raymond

aneesh_shamsudeen · ‎2015 May 11

Hi Raymond,

I checked recent transport and rfc destinations. My RFC name is "ZEDI_DOCUMENT_SEG_STATUS".

Regards,

Aneesh S

matt · ‎2015 May 11

Does the ZEDI_DOCUMENT_SEG_STATU exist in your system?

What is calling the RFC?

aneesh_shamsudeen · ‎2015 May 11

Hi Matthew,

ZEDI_DOCUMENT_SEG_STATUS exist in our R3 production system. Please find the below source code to call this RFC from non sap system.

- function {FUNCTION ZEDI_DOCUMENT_SEG_STATUS (IMPORT PARAMETER CREDAT=2015-05-07, IMPORT PARAMETER DIRECT=2, IMPORT PARAMETER MESTYP=ZIYMSME, IMPORT PARAMETER SEGNAM=Z1YMS, IMPORT PARAMETER ZZIDOCNUM=YMD0000000000171900, TABLES PARAMETER INT_EDIDS=TABLE )} SAP.Middleware.Connector.IRfcFunction {SAP.Middleware.Connector.RfcFunction}

Regards,

Aneesh S

matt · ‎2015 May 11

Looks like a code page / unicode translation mismatch. Beyond that I'm out of ideas. Try asking your Basis team about the code page settings on your R/3 and your middleware systems. Also check how your R/3 is defined as a destination on the middleware.

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My Account

My Account

CALL_FUNCTION_NOT_FOUND