topic Re: Finding caller program in a RFC call in Application Development and Automation Discussions

Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 11:52:39 GMT

Hi experts,

We are having lots of CALL_FUNCTION_NOT_FOUND short dumps in one of our systems. The errors are caused because other systems call a function that does not exist, so the dumps are created.

What we would like to know is what program is doing these calls, since all we can see in the short dump is the caller system and the function it is trying to access, but not the exact program where the call is performed so we can fix the code.

Thanks in advance for your support.

Re: Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 11:54:47 GMT

hello,

Can you provide dump details to help you find the same?

Thanks.

Re: Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 11:59:27 GMT

Sorry if this is too much of a wall of text, I can't find an "attach file" type feature.

ABAP runtime errors CALL_FUNCTION_NOT_FOUND

Occurred on 11.12.2006 at 10:04:34

Function module "Y_EF_DETERMINE_PICTURE" not found.

What happened?

The function module "Y_EF_DETERMINE_PICTURE" was called, but cannot be

found in the Function Library.

The current ABAP/4 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/4 program.

What can you do?

Note the actions and input that caused the error.

Inform your SAP system administrator.

You can print out this message by choosing "Print". Transaction ST22

allows you to display and manage termination messages, including keeping

them beyond their normal deletion date.

Error analysis

The program "SAPMSSY1 " contains a CALL FUNCTION statement. The name

of the function module to be called is "Y_EF_DETERMINE_PICTURE".

No function module exists with the name "Y_EF_DETERMINE_PICTURE".

All function modules are stored in the Function Builder (SE37).

Possible reasons:

a) Wrong name specified. Particular attention should be paid

to upper/lower case and underscores ("_").

b) Transport error

c) In the case of an enqueue/dequeue module, the lock object

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?

If the error occurred in a non-modified SAP program, you may be

able to find a solution in the SAP note system.

If you have access to the note system yourself, use the following

search criteria:

"CALL_FUNCTION_NOT_FOUND"

"SAPMSSY1 " or "SAPMSSY1 "

"REMOTE_FUNCTION_CALL"

Function modules with names similar to "Y_EF_DETERMINE_PICTURE":

Y_EF_USEX_DETERMINE_TAX

Y_GF1_DETERMINE_RECTYPE

Y_GK_DETERMINE_PRCTR

Y_EF_USEX_PICTURE_SUBMIT

Y_EF_USEX_SHOW_PICTURE

Y_EF_RFC_PICTURE_POST

Y_GF1_DETERMINE_SBU

Y_GF_DETERMINE_VERSION

Y_GF_DETERMINE_DATE_PREVMON

Y_GF1_DETERMINE_CURRENT_PERIOD

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.............. "46C"

Application server....... "sapgp1s"

Network address.......... "52.99.71.21"

Operating system......... "AIX"

Release.................. "5.3"

Hardware type............ "00C4449E4C00"

Database server.......... "sapgp1s"

Database type............ "DB6"

Database name............ "GP1"

Database owner........... "SAPR3"

Character set............ "en_US.ISO8859-1"

SAP kernel............... "46D"

Created on............... "Aug 26 2005 22:40:31"

Created in............... "AIX 1 5 0056AA8A4C00"

Database version......... "DB6_71 "

Patch level.............. "2113"

Patch text............... " "

Supported environment....

Database................. "DB6 06., DB6 07., DB6 08.*"

SAP database version..... "46D"

Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3

5, , System build information:, -

, LCHN :

User, transaction...

Client.............. 000

User................ "SAPSYS"

Language............ "E"

Transaction......... " "

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

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

Line of screen...... 2

Information about Remote Function Call (RFC) Caller:

System.............. "WP1 "

Database release.... "46C "

Kernel release. .... "46D "

Connection type. ... "3 " (2 = R/2, 3 = R/3, E = Extern, R = Reg.

Call type........... "S-" (S = synch., a/A = asynch., T = transactional

Client.............. 510

User................ "PC1706 "

Transaction......... "/COCKPIT/1 "

Function module..... "Y_EF_DETERMINE_PICTURE"

Call destination.... "GP1590"

Source server....... "wsdux44_WP1_10"

Source IP address... "52.99.71.124"

Additional information about RFC logon:

Trusted relationship " "

Logon return code... " "

Trusted return code. " "

Note: In Releases earlier than 4.0, some of the above information about

RFC calls may not be available.

Information on where termination occurred

The termination occurred in the ABAP/4 program "SAPMSSY1 " in

"REMOTE_FUNCTION_CALL".

The main program was "SAPMSSY1 ".

The termination occurred in line 67

of the source code of program "SAPMSSY1 " (when calling the editor 670).

Source code extract

000370 ENDMODULE.

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.

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

000650 FORM REMOTE_FUNCTION_CALL USING VALUE(TYPE).

000660 DO.

CALL 'RfcImport' ID 'Type' FIELD TYPE.

000680 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).

000690 RSYN >SCONT SYSC 00011111 0.

000700 ENDDO.

000710 ENDFORM.

000720

000730 FORM REMOTE_FUNCTION_DIASTART.

000740 DO.

000750 CALL 'RfcImport' ID 'Type' FIELD RFCTYPE_RFCDIA.

000760 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).

000770 "Parking position for next request

000780 RSYN >SCONT SYSC 00011111 10.

000790 "ALternativ : Free mode

000800 "COMMIT WORK.

000810 "SYSTEM-CALL FREE MODE 0.

000820 ENDDO.

000830 ENDFORM.

000840

000850 FORM REMOTE_FUNCTION_DIACALL.

000860 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

Chosen variables

Name.......................... Contents.1........2........3....+....4

SY-XPROG

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

SY-XFORM Y_EF_DETERMINE_PICTURE

554454454544445544555422222222

9F56F45452D9E5F093452500000000

%_SPACE

SY-MSGID

22222222222222222222

00000000000000000000

EBC_TO_ASC-X05 P&QéRêSëTèUíVîWïXìY~ZÜ[$*])^;_^

525E5E5E5E5E5E5E5E575D5252525355

06192A3B485D6E7F8C9EACB4CAD9EBFE

RFCTYPE_QUEUE 6

0000

0006

%_PRINT 000

2222333222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 40

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 80 0 ########

2222222222320000000022222222222222222222

0000000000000000000000000000000000000000

... + 120

22222222

0000000

SY-MSGNO 000

333

000

EBC_TO_ASC-X04 @ A BâC{DàEáFãGåHçIñJÄK.L<M(N+O!

424A4E474E4E4E4E4E4F4C4243424242

0010223B405163758791A4BECCD8EBF1

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

%_?NOT_ASSIGNED?

2222

0000

SPACE

SY-REPID SAPMSSY1

5454555322222222222222222222222222222222

310D339100000000000000000000000000000000

TYPE 3

0000

0003

SYST ########################################

0000000000000000000000000000000000000000

0001000000000000000000000000000000000000

... + 40 ########################################

0000000000000000000000000000000000000000

0000000000010000000100000000000000000000

... + 80 ########################################

0000000000000000000000000000000000000000

... + 120 #######################################T

00000000

0000000

Active calls / events

No.... Type........ Name..........................

Programm

Include Line

1 FORM REMOTE_FUNCTION_CALL

SAPMSSY1

SAPMSSY1 67

2 MODULE (PBO) %_RFC_START

SAPMSSY1

SAPMSSY1 31

Internal notes

The termination occurred in the function "link_rfdir" of the SAP

Basis System, specifically in line 165 of the module

"//bas/46D/src/krn/runt/ablink.c#3".

The internal operation just processed is "CALY".

The internal session was started at 20061211100434.

Active calls in SAP kernel

=> 64 bit R/3 Kernel

=> 64 bit AIX Kernel

=> Heap limit = unlimited

=> Stack limit = unlimited

=> Core limit = 51200000

=> File size limit = unlimited

=> Heap address = 0x118dba360

=> Stack address = 0xfffffffffff5d50

=> Stack low = 0xfffffffffff5d50

=> Stack high = 0xffffffffffff600

=> Stack Trace:

AixStack() at 0x100059364

CTrcStack2() at 0x10005945c

rabax_CStackSave() at 0x10003959c

ab_rabax() at 0x1000425b4

link_rfdir() at 0x100540418

ab_link() at 0x100540a18

ab_rfcimport() at 0x1005f49f0

ab_jcaly() at 0x100024560

ab_extri() at 0x100487474

ab_xevent() at 0x10059c804

ab_dstep() at 0x10043bd98

dynpmcal() at 0x100942f94

dynppbo0() at 0x100941320

dynprctl() at 0x100948f40

dynpen00() at 0x1008f7818

Thdynpen00() at 0x1001429f4

TskhLoop() at 0x100146368

tskhstart() at 0x1001576ac

DpMain() at 0x100e06e38

main() at 0x100de72f4

List of ABAP programs affected

Type

Program

Gen. date time

LoadSize

Prg

SAPMSSY1

04.01.2000 19:06:59

20480

List of internal tables

No dump information available

Directory of application tables (contents)

Program

Name.......... Contents.1........2........3....+....

Directory of data areas (administration information)

Program

No.. Name.......... Lgth Ofsg Type Next Gen date Gen time

SYST

L not assigned -15 0 IN

M /%_LISTTABLE -14 1 CO 0

T global stack -13 1 2 GL 0

SAPMSSY1

A global data 0 3 DA

L constant dat 1 4 LI .0 .0216

L constant dat 2 5 LI SSY .0 .018B

L not assigned 3 6 IN

L SYST 4 7 TA 0

L SY 5 8 TA

L RSJOBINFO 6 9 TA

M /%_SYS%% 7 0 CO

M field symbol 8 1 FS

L TCPIC 9 2 TA

M field symbol 10 3 FS

L text pool 11 4 TP

Directory of data areas (contents)

Program

No.. Name.......... Contents..1........2........3....+....

SYST

L not assigned 0

L text pool 102 |SAPMSSY1

ABAP control blocks CONT

Include Line source code

Index Name F1 Co Par01 Par2. Par3. Par4. Tabl

-- -- -

SAPMSSY1 60 MESSAGE A800.

215 CLEA 00 84

216 CLEA 00 85

217 MESS 00 27

SAPMSSY1 62 ENDFORM.

218 ENDF 00

219 -

223 -

SAPMSSY1 65 FORM REMOTE_FUNCTION_CALL USIN

227 PERP 00 1

228 PERP 02

SAPMSSY1 66 DO.

229 WHIL 00 2

233 WHIL 00 3

237 BRAN 05 Branch to 251

SAPMSSY1 67 CALL 'RfcImport' ID 'Type' FIE

238 CALY 00 3 86 70 71 71

>>>>> CALY 02 87 P0

SAPMSSY1 68 PERFORM (SY-XFORM) IN PROGRAM

246 xper 02 12 13

248 PERP 80

SAPMSSY1 69 RSYN >SCONT SYSC 00011111 0.

249 SYSC 1F

SAPMSSY1 70 ENDDO.

250 BRAX 00 Branch to 233

251 WHIL 00 4

SAPMSSY1 71 ENDFORM.

255 ENDF 00

256 -

End of runtime analysis

Re: Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 12:06:57 GMT

Hello,

Are there any external connections with your system which are performing RFC calls in SAP system.

The program mentioned is of CPIC & RFC control.it's just an routine pool program which is triggering RFC call.but caller can be external.

Thanks.

Re: Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 13:11:15 GMT

Yes, the system with the dump (GP1) is receiving calls from various other systems (CP1, WP1) asking for the Y_EF_DETERMINE_PICTURE function, which does not exist. What I want to know is which programs in the calling systems (CP1, WP1) are performing that call to be able to edit the code and replace it for an existing function.

Thanks for your help.

Re: Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 13:17:57 GMT

Hello,

it's WP1 system which is calling RFC.

Check this from dump :

Information about Remote Function Call (RFC) Caller:

System.............. "WP1 "

Database release.... "46C "

Kernel release. .... "46D "

Connection type. ... "3 " (2 = R/2, 3 = R/3, E = Extern, R = Reg.

Call type........... "S-" (S = synch., a/A = asynch., T = transactional

Client.............. 510

User................ "PC1706 "

Transaction......... "/COCKPIT/1 "

Function module..... "Y_EF_DETERMINE_PICTURE"

Call destination.... "GP1590"

Source server....... "wsdux44_WP1_10"

Source IP address... "52.99.71.124"

Check trnasaction :"/COCKPIT/1

Hope this helps.

Thanks.

Re: Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 13:21:09 GMT

Yes, sometimes it's WP1, on other dumps it's CP1. What I need to know is exactly which programs in these systems are doing the call so I can edit the code and fix it.

Thanks for your help.

Re: Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 13:25:35 GMT

Hello,

Does this transaction exists in called system "/COCKPIT/1' .? or in caller system?

if it's SAP -caller system then check the system for that trnasaction.

I am not sure if the caller system in SAP or non-SAP?

if it's not SAP then just check the timings at which this dump occured & check the caller system log at that time.(you can keep trace on in caller system ).

it should show you the requesting program details .

Hoep this helps.

Thanks.

Re: Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 13:40:12 GMT

Yes, it exists but I am not authorized to run it. Calling systems are R/3, but there are no dumps on those systems when this one is produced on the receiving end.

Thanks a lot for your help!

Re: Finding caller program in a RFC call

Former Member — Tue, 12 Dec 2006 13:47:35 GMT

Hello,

There won't be any dump b'cos RFC call is successful.ONly things at receiving side function does not exists..so dump is on your system.Check the log for those timings & also trnasction mentioned in dump..That should help you..You can also ask someone who has authorisation for those system to look at this part. or ask admin team to get trace log from those systems,which should also help you track down exact calling program.

Hope this helps.

Thanks.