call_function_format_not_sup

Former Member — Fri, 31 Jul 2009 08:48:42 GMT

Hi,

I am getting this dump call_function_format_not_sup for user sapsys and client 000.

I am attaching st22 dump details.

Daily i am getting this dump 5 to 10 time not in frequent interval.

Sap release is 3.1h and oracle 7.3 sunos.

plz kindly help me.

ABAP/4 runtime error CALL_FUNCTION_FORMAT_NOT_SUP

Occurred on 07.07.2009 at 15:15:18

RFC data format not supported.

What happened?

An error occurred when executing a Remote Function Call.

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?

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.

Error analysis

A data error occurred when executing a Remote Function Call.

The data format used is not supported by the recipient.

How to correct the error

A 'Remote Function Call' passed data in the incorrect format or

length. If both the calling program and the called program are

ABAP/4 function modules, there is an error in the

SAP system.

If one of these programs is a CPIC program which interprets the

RFC log itself, the error has probably occurred because the program

does not conform to the standards defined by SAP.

System environment

SAP Release.............. "31H"

Application server....... "PCPPROD1"

Network address.......... "10.106.128.71"

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

Release.................. "5.6"

Hardware type............ "sun4u"

Database server.......... "PHYPLW02"

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

Database name............ "ALP"

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

Character set............ "en"

SAP kernel............... "31I"

Created on............... "Jul 24 2001 05:20:53"

Created in............... "SunOS 5.5.1 Generic_10364019 sun4u"

Database version......... "ora OCI_73400"

Patch level.............. "616"

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

Supported environment....

Database................. "ORACLE 7.2..., ORACLE 7.3..., ORACLE

8.0...*"

SAP database version..... "31I"

Operating system......... "SunOS 5.5.1, SunOS 5.6, SunOS 5.7, SunOS 5.8"

User, transaction...

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

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

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

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

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

Screen.............. "SAPMSSY13004"

Screen line......... 2

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 SYXPROG(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 SYSUBRC EQ 0.

000580 PERFORM (SYXFORM) IN PROGRAM (SYXPROG).

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 (SYXFORM) IN PROGRAM (SYXPROG).

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 (SYXFORM) IN PROGRAM (SYXPROG).

000770 "Parking position for next request

000780 RSYN >SCONT SYSC 00011111 10.

000790 "ALternativ : Free mode

000800 "COMMIT WORK.

000810 "SYSTEMCALL FREE MODE 0.

000820 ENDDO.

000830 ENDFORM.

000840

000850 FORM REMOTE_FUNCTION_DIACALL.

000860 SYXCODE = '%_@no@'.

Contents of system fields

SY field contents..................... SY field contents.....................

SYSUBRC 0 SYINDEX 1

SYTABIX 0 SYDBCNT 0

SYFDPOS 0 SYLSIND 0

SYPAGNO 0 SYLINNO 1

SYCOLNO 1

Chosen variables

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

SYMSGV1

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 40

2222222222

0000000000

SYMSGV2

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 40

2222222222

0000000000

SYMSGV3

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 40

2222222222

0000000000

SYMSGV4

2222222222222222222222222222222222222222

0000000000000000000000000000000000000000

... + 40

2222222222

0000000000

TYPE 3

0000

0003

SYXPROG

22222222

00000000

SYXFORM

222222222222222222222222222222

000000000000000000000000000000

Active calls / events

No.... Program INCLUDE Line Type.... Name.....................

1 SAPMSSY1 SAPMSSY1 67 FORM REMOTE_FUNCTION_CALL

2 SAPMSSY1 SAPMSSY1 30 MODULE %_RFC_START

Internal notes

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

Basis System, specifically in line 1178 of the module " ".

The internal operation just processed is "CALY".

List of ABAP/4 programs affected

Program

Load size

Roll size

Gen. date

/ time Changed by

SAPMSSY1

20480

83050

21.05.1997

16:27

21.05.1997

SAP

List of internal tables

No dump information available

Directory of application tables (contents)

Program name........... Contents.1........2........3....+....

SAPMSSY1 TCPIC

Directory of data areas (administration information)

No Program name........... Length Gen.date Gen.time Ofst Type Next

0 SAPMSSY1 /%_LISTTABLES 3128 3 DATA

1 SAPMSSY1 stack area 65536 2 DATA

2 SAPMSSY1 text pool 4064 1 DATA

3 SAPMSSY1 global data 1136 0 DATA

4 SAPMSSY1 local data 0 1 STCK

5 SAPMSSY1 constant data 647 2 LITL

6 SAPMSSY1 not assigned 0 3 INVL

7 SAPMSSY1 SYST 2232 4 TABL

8 SAPMSSY1 SY 2232 5 TABL

9 SAPMSSY1 RSJOBINFO 84 6 TABL

10 SAPMSSY1 /%_SCREEN 56 7 DATA

11 SAPMSSY1 /%_SYS%% 480 8 DATA

12 SAPMSSY1 TCPIC 70 9 TABL

Directory of data areas (contents)

No Program name........... Contents.1........2........3....+....

0 SAPMSSY1 /%_LISTTABLES |00000x0C000000000x0C0

1 SAPMSSY1 stack area |000x030000ÿÿÿÿ00000000

2 SAPMSSY1 text pool |ÿÿ000006E000000x01R00000

3 SAPMSSY1 global data | 0 x04

4 SAPMSSY1 local data SCONT SYSC 0

177 BRAX 00 Branch to 161 SAPMSSY1 70 ENDDO.

178 WHIL 00 4 SAPMSSY1 70

182 ENDF 00 SAPMSSY1 71 ENDFORM.

187 WHIL 00 2 SAPMSSY1 74 DO.

End of runtime analysis

Thanx

kvl

Re: call_function_format_not_sup

Former Member — Fri, 31 Jul 2009 09:06:01 GMT

Hi,

Please check this sap note : 730677.

Hope it helps

Regards

Hiren K.Chitalia

Re: call_function_format_not_sup

Former Member — Fri, 31 Jul 2009 09:37:58 GMT

Hi,

I checked this sap note. but it is not supporting for our sap release.

kindly let me know what could be the impact of this dump i am getting this on daily basis and which event is triggering this.

plz kindly help me.

Thanx

kvl

Re: call_function_format_not_sup

Former Member — Fri, 31 Jul 2009 11:13:50 GMT

Hi,

I checked this sap note. but it is not supporting for our sap release.

kindly let me know what could be the impact of this dump i am getting this on daily basis and which event is triggering this.

How can i trace this which event trigerring?

plz kindly help me.

Thanx

kvl

Re: call_function_format_not_sup

Former Member — Wed, 05 Aug 2009 11:07:32 GMT

Hi,

Now i found which RFC trigerring this dump. it is autocad rfc. In autocad is connected to sap using pisoft interface. when give command bom some times they are getting connection. whenever they are not getting connection this dump is occuring. how to check this kindly help me.

kvl

topic Re: call_function_format_not_sup in Application Development and Automation Discussions

call_function_format_not_sup

Re: call_function_format_not_sup

Re: call_function_format_not_sup

Re: call_function_format_not_sup

Re: call_function_format_not_sup