topic Re: Problem with Function Module in Application Development and Automation Discussions

Problem with Function Module

Former Member — Wed, 02 Jul 2008 12:34:19 GMT

I am working on Function Modules i am facing some Peculiar problem with table paramenters.

I created one Z function module while i created i used 2 tables parameter both are Z structures

1. ZLFZA which is exactly similar to LFZA structure

2. ZLFBK which is exactly similar to LFBK structure ( include/append structure not added copied the

fileds )

Table Parameters for this funciton module goes like this

ALTERNATIVEPAYEEDATA LIKE ZLFZA

BANKDATA LIKE ZLFBK

At this stage function module is working fine.

Later i removed MANDT field from both the structures and i activated both the structure without any problem

But when i try to excute the function module it is giving error as

In the function module interface, you can specify only

fields of a specific type and length under "BANKDATA".

Although the currently specified field

"%_OBANKDATA" is the correct type, its length is incorrect.

I tried to execute the funciton module by adding MANDT Field again to ZLFBK structure it is working fine.

Function module is working even i deleted MANDT field in ZLFZA structure but it is giving dump if i remove mandt field can any body give me a solution or idea why it is going to dump

Re: Problem with Function Module

vinod_vemuru2 — Wed, 02 Jul 2008 12:48:38 GMT

Hi,

This might be because of buffering problem. Instead of directly activating ur FM, Just delete these 2 tables parameters(With delete icon) and create new entries with same name. It will work fine. Get back in case of any issues.

Thanks,

Vinod.

Re: Problem with Function Module

Former Member — Wed, 02 Jul 2008 12:57:53 GMT

Hi,

Have you written any native SQL statements.

Native SQL statements brings the data from all clients where as open sql statements rings the current logon clint data.

However why are you deleting the mandt field,Kepp as it is but don't use it.

regards,

rama.

Re: Problem with Function Module

former_member196065 — Wed, 02 Jul 2008 13:01:26 GMT

Hi Vinod

Thanks for your reply. I tried that option still it is giving same old error. My surpize is it working for other structure and it is not working for ZLFBK structure if i include MANDT field again into the structure it is working fine

Re: Problem with Function Module

former_member196065 — Wed, 02 Jul 2008 13:03:29 GMT

Hi Rama

Nothing to do with data, at first step ( not even it is entering into Function module ) itself i am getting this error it is something related to Structure

Re: Problem with Function Module

vinod_vemuru2 — Wed, 02 Jul 2008 13:15:54 GMT

Hi,

Did u created structures or tables? Ideally it should work.

Also check whether ur structures are active /pertly active.

Are u getting error while activation or while running? If it is while running then the problem must be something else. Debug and see what is the proble,.

Thanks,

Vinod.

Re: Problem with Function Module

former_member196065 — Wed, 02 Jul 2008 13:19:46 GMT

Hi Vinod,

They are structures, i used these structues in TABLE parameters in Function module.

After removing the MANDT fields from these Z structure i am able to activate sucessfully

No warnings nothing.

Re: Problem with Function Module

former_member196065 — Wed, 02 Jul 2008 13:20:42 GMT

this is dump analysis

Runtime Errors CALL_FUNCTION_CONFLICT_LENG

Exception CX_SY_DYN_CALL_ILLEGAL_TYPE

Occurred on 02.07.2008 at 07:27:02

Type conflict when calling a function module (field length).

What happened?

Error in ABAP application program.

The current ABAP program "Z_BOA_BAPI_VENDOR_MAINTAIN====FT " had to be

terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

A function module was called incorrectly.

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.

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',

was neither

caught nor passed along using a RAISING clause, in the procedure

"FUNCTION_CALL" "(FORM)"

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

The call to the function module "Z_BOA_BAPI_VENDOR_MAINTAIN" is incorrect:

In the function module interface, you can specify only

fields of a specific type and length under "BANKDATA".

Although the currently specified field

"%_OBANKDATA" is the correct type, its length is incorrect.

How to correct the error

The exception must either be prevented, caught within the procedure

"FUNCTION_CALL"

"(FORM)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

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_CONFLICT_LENG" CX_SY_DYN_CALL_ILLEGAL_TYPEC

"Z_BOA_BAPI_VENDOR_MAINTAIN====FT " or "Z_BOA_BAPI_VENDOR_MAINTAIN====FT "

"FUNCTION_CALL"

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.

If the error occurs in the program SAPCNVE, it could be for any of

the following reasons:

1. The field

05a9ffb8 77e6608b 03abfa80 00000000 00000000 03abfa80 MSVCRT!endthreadex

05a9ffec 00000000 77bcb4bc 03abfa80 00000000 00000000 kernel32!GetModuleFileNameA

List of ABAP programs affected

Type Program Gen. Date Time Load Size

Prg RS_TESTFRAME_CALL 13.12.2002 12:22:58 20480

Prg SAPMSSY0 31.05.2005 00:51:53 62464

Prg SAPMSSYD 05.06.2002 17:09:33 16384

Prg SAPFSYSCALLS 14.02.2002 14:22:47 6144

Prg RSDBRUNT 31.05.2005 00:26:18 219136

Typ RSSCR . . : m:15 4096

Prg RSDBSPBL 13.12.2002 12:24:35 57344

Prg SAPDB__S 14.02.2002 14:22:47 15360

Typ VARID 12.05.1997 16:51:30 4096

Prg %_CSYDB0 14.02.2002 14:22:46 27648

Prg RSDBSPVA 31.05.2005 00:59:24 106496

Typ RSVAMEMKEY 07.05.1997 13:07:49 2048

Prg RSDBSPMC 05.06.2002 17:09:26 65536

Typ DDSHDESCR 03.09.1997 03:05:16 3072

Typ SPPARAMS 07.05.1997 13:10:38 1024

Prg SAPLICON 04.02.2004 05:57:09 23552

Prg %_CICON 14.02.2002 14:22:46 57344

Prg SAPLSABE 14.02.2002 14:22:47 11264

Prg SAPLSECU 31.05.2005 01:02:52 63488

Prg SAPLDSYA 14.02.2002 14:22:47 38912

Prg SAPFSDS1 13.12.2002 12:14:34 47104

Typ TDCLD 02.11.1998 09:51:35 4096

Prg SAPLSDOD 31.05.2005 00:26:00 38912

Typ DOKIL 12.05.1997 16:46:17 2048

Prg SAPCNVE 14.02.2002 14:22:47 6144

Prg SAPLLANG 14.02.2002 14:22:47 8192

Typ T002 14.02.1998 10:24:58 2048

Typ RSEXFCODE 13.08.1997 12:52:57 1024

Typ RSPARINT 10.04.1995 09:58:38 1024

Prg SAPLSCNT 14.02.2002 14:22:47 22528

Prg SAPLSVSM 13.12.2002 12:16:46 22528

Prg SAPLSGUI 13.12.2002 12:27:47 29696

Prg SAPLSTTM 31.05.2005 00:56:52 73728

Prg SAPLSBDC 13.12.2002 12:13:58 37888

Prg CL_DATAPROVIDER===============CP 14.02.2002 14:22:46 38912

Prg %_CCNTL 14.02.2002 14:22:46 13312

Typ OBJ_RECORD 14.02.1998 08:30:43 2048

Prg SAPLSTUP 31.05.2005 01:02:33 62464

Prg SAPLCNDP 31.05.2005 00:50:26 155648

Prg SAPFGUICNTL 13.12.2002 12:30:03 20480

Prg SAPLOLEA 31.05.2005 01:02:43 77824

Prg SAPLSFES 31.05.2005 01:02:48 176128

Prg SAPLSPLUGIN 14.02.2002 14:22:48 6144

Prg SAPLGRFC 14.02.2002 14:22:47 13312

Prg SAPSHDTV 04.02.2004 00:06:43 27648

Typ SSCRTEXTS 03.09.1997 03:12:33 2048

Typ SSCRFIELDS 13.05.1997 12:54:26 3072

Prg SAPLSEUJ 31.05.2005 00:50:52 285696

Typ RSEUMOD 06.05.2002 10:38:04 25600

Prg SAPLSUNI 31.05.2005 00:24:58 126976

Typ TFDIR 29.07.1998 19:49:08 2048

Typ TRDIR 02.11.1998 09:59:17 5120

Typ D010SINF 22.01.2001 11:11:06 6144

Typ ENLFDIR 09.11.2000 14:07:35 3072

Prg SAPMS38L 31.05.2005 00:55:49 566272

Prg SAPLSEWORKINGAREA 31.05.2005 01:02:35 225280

Typ FUPARAREF 13.08.1997 13:26:52 4096

Prg RSAQGENI 13.12.2002 12:18:51 16384

Typ STOKES 26.02.2001 12:01:12 2048

Typ RSSOURCE 23.05.1995 16:37:10 1024

Typ PROGDIR 02.11.1998 09:58:34 5120

Prg SAPLSYDB 31.05.2005 00:52:20 49152

Prg SAPLSEUF 31.05.2005 00:30:19 273408

Typ RSINFDIR 29.07.1998 19:07:56 2048

Typ FUNCT 14.02.1998 07:22:14 2048

Typ TFTIT 14.02.1998 13:28:57 2048

Prg %_CNF2TY 14.02.2002 14:22:46 6144

Prg Z_BOA_BAPI_VENDOR_MAINTAIN====FT 02.07.2008 07:26:55 122880

Prg SAPLSNF2 31.05.2005 01:03:40 342016

Prg %_CSYDES 14.02.2002 14:22:46 6144

Typ LFA1 09.01.2008 13:07:52 16384

Prg CL_ABAP_CHAR_UTILITIES========CP 31.05.2005 00:41:06 11264

Typ ZLFA1X 09.03.2007 04:35:09 16384

Typ LFB1 02.07.2002 16:31:13 10240

Typ ZLFB1X 09.03.2007 04:40:59 10240

Typ LFM1 07.06.2001 17:42:37 8192

Typ ZLFM1X 09.03.2007 04:43:55 8192

Typ LFAS 26.07.2007 10:35:16 2048

Typ ZLFASX 09.03.2007 02:40:44 2048

Typ LFB5 08.03.1992 03:50:48 3072

Typ ZLFB5X 09.03.2007 03:51:26 3072

Typ ZLFBK 02.07.2008 07:24:41 3072

Typ ZLFBKX 09.03.2007 04:06:22 3072

Typ LFZA 10.07.1997 00:30:40 2048

Typ ZLFZAX 09.03.2007 04:10:19 2048

Typ ZBAPI_KNVK 29.02.2008 11:26:35 11264

Typ ZBAPI_KNVKX 29.02.2008 11:27:49 11264

Typ LFM2 17.05.2007 06:33:24 7168

Typ ZLFM2X 07.05.2007 04:06:22 7168

Typ WYT1T 04.06.1997 19:30:53 2048

Typ ZWYT1TX 17.05.2007 01:08:59 2048

Typ FWYT3 23.03.2000 23:05:15 3072

Typ ZWYT3X 14.06.2007 05:40:59 3072

Typ LFBW 10.07.1997 00:30:39 3072

Typ ZLFBWX 12.03.2007 06:02:23 3072

Typ LFAT 19.11.2007 09:37:20 2048

Typ ZLFATX 12.03.2007 06:04:49 2048

Typ BAPIPAREX 02.11.1998 09:43:19 2048

Typ BAPIPAREXX 12.04.1999 15:52:21 2048

Typ BAPIRET2 20.08.1998 11:11:35 3072

Typ RSSOURCEL 09.11.2000 14:11:36 1024

Typ LFAS 26.07.2007 10:35:16 2048

Typ ZLFASX 09.03.2007 02:40:44 2048

Typ LFB5 08.03.1992 03:50:48 3072

Typ ZLFB5X 09.03.2007 03:51:26 3072

Typ ZLFBK 02.07.2008 07:24:41 3072

Typ LFAS 26.07.2007 10:35:16 2048

Typ ZLFASX 09.03.2007 02:40:44 2048

Typ LFB5 08.03.1992 03:50:48 3072

Typ ZLFB5X 09.03.2007 03:51:26 3072

Typ ZLFBK 02.07.2008 07:24:41 3072

Prg SAPMSDYP 14.02.2002 14:22:48 31744

Prg SAPLCSTR 31.05.2005 01:03:36 63488

Typ SMP_DYNTXT 25.01.1999 13:03:11 2048

Prg CL_GUI_PROPS_CONSUMER=========CP 13.12.2002 12:11:27 27648

Prg SAPLTHFB 31.05.2005 00:57:05 294912

Prg CL_DYNAMIC_GUI_EXTENSIONS=====CP 14.02.2002 14:22:46 33792

Prg CL_GUI_DATAMANAGER============CP 31.05.2005 00:50:46 69632

Prg SAPLSMON 31.05.2005 00:58:50 349184

Prg SAPLSETF 04.02.2004 06:01:30 78848

Prg %_CSETST 13.12.2002 12:10:31 25600

Prg SAPLSDBG 04.02.2004 05:50:57 23552

Prg SAPLZBOA_VENDOR 02.07.2008 07:26:48 637952

Prg CX_SY_DYN_CALL_ILLEGAL_TYPE===CP 19.11.2001 15:52:28 10240

Typ SCX_SRCPOS 09.11.2000 14:12:15 1024

Prg CX_SY_DYN_CALL_PARAMETER_ERRORCP 19.11.2001 15:52:28 9216

Prg CX_SY_DYN_CALL_ERROR==========CP 14.02.2002 14:22:47 9216

Prg CX_DYNAMIC_CHECK==============CP 14.02.2002 14:22:47 8192

Prg CX_ROOT=======================CP 14.02.2002 14:22:47 9216

Prg CX_NO_CHECK===================CP 14.02.2002 14:22:47 8192

Prg CX_SY_NO_HANDLER==============CP 14.02.2002 14:22:47 8192

Typ FUSEQDIR 29.07.1998 18:32:47 2048

List of internal tables

No dump information available

Directory of Application Tables

Program

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

RS_TESTFRAME_CALL

SYST x010000000x01000000000000000000

SSCRFIELDS

SSCRTEXTS

RSDBRUNT

VARID

SAPLSABE

TRDIR Z_BOA_BAPI_VENDOR_MAINTAIN====FT X SD$ 1SS

SAPFSDS1

TDCLD RE DOKU 8R XX XXLIMUDOKUX x1E0XR3TRPROGX

SAPLSDOD

DOKIL

SAPLLANG

T002 ES1EN

SAPLSEUJ

RSJOBINFO 00000000000000

EUFUNC FLZBOA_VENDOR Z_BOA_BAPI_VENDOR_MAINTAIN

TFDIR Z_BOA_BAPI_VENDOR_MAINTAIN SAPLZBOA_VENDOR

TRDIR Z_BOA_BAPI_VENDOR_MAINTAIN====FT X SD$ 1SS

D010SINF Z_BOA_BAPI_VENDOR_MAINTAIN====FT A XD$ 1SS

*TRDIR LZBOA_VENDOR$03 XXSD$ IS

*D010SINF LZBOA_VENDOR$03 A XD$ IS

RS38L

RFCDES

RSEUMOD VPATHOORI X2G K

SAPLSUNI

RS38L

TFTIT EZ_BOA_BAPI_VENDOR_MAINTAIN Vendor Master Maintan

TFDIR Z_BOA_BAPI_VENDOR_MAINTAIN SAPLZBOA_VENDOR

ENLFDIR Z_BOA_BAPI_VENDOR_MAINTAIN ZBOA_VENDOR X

SAPMS38L

RSINFDIR

RSAQGENI

AQGDB PRLSEUJFDN

SAPLSEUF

TFDIR Z_BOA_BAPI_VENDOR_MAINTAIN SAPLZBOA_VENDOR

CL_GUI_PROPS_CONSUMER=========CP

EUDB %CQ0I5DkZCRjcANUVDADc3ADg1AXUPrq_vr0I4NDYz 0000

Directory of Application Tables (Administrative Information)

Program

Name.......................... Time.......... Length.. .

CL_GUI_PROPS_CONSUMER=========CP

SYST 20010612125650 00002404

SSCRFIELDS 20000323224119 00000854

SSCRTEXTS 00000371

RSDBRUNT

VARID 00000132

SAPLSABE

TRDIR 00000170

SAPFSDS1

TDCLD 00000050

SAPLSDOD

DOKIL 00000076

SAPLLANG

T002 00000005

SAPLSEUJ

RSJOBINFO 00000084

EUFUNC 00003936

TFDIR 00000094

TRDIR 00000170

D010SINF 00000184

*TRDIR 00000170

*D010SINF 00000184

RS38L 00002479

RFCDES 00001033

RSEUMOD 00001664

SAPLSUNI

RS38L 00002479

TFTIT 00000105

TFDIR 00000094

ENLFDIR 00000073

SAPMS38L

RSINFDIR 00000076

RSAQGENI

AQGDB 00002956

SAPLSEUF

TFDIR 00000094

CL_GUI_PROPS_CONSUMER=========CP

EUDB 00003940

ABAP control blocks CONT

Caution: Program has changed

Caution: At time of termination, Active source code no longer available

Include Line source code

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

Z_BOA _ BAPI _ VE N DO R _MAIN T AIN== = =FT 479 IF DEBUG = '1'. BREAK-POINT AT

528 BREA FF

Z_BOA_BAPI_VENDOR_MAINTAIN====FT 481 DEBUG = SPACE.

530 mvqb 01 12 47 195

Z_BOA_BAPI_VENDOR_MAINTAIN====FT 482 GET RUN TIME FIELD TIME1.

532 TIME 01 2

533 LREG 42 4 2 26

Z_BOA_BAPI_VENDOR_MAINTAIN====FT 483 CALL FUNCTION 'Z_BOA_BAPI_VEND

535 FUNC 00 V1303

536 FUNC 00 198

537 PAR2 02 24 52

539 PAR2 02 25 53

541 PAR2 02 22 50

543 PAR2 02 23 51

545 PAR2 02 26 54

547 PAR2 02 27 55

>>>>> FUNC 10 49

550 PAR2 01 28 56

552 PAR2 03 35 96

554 PAR2 03 36 102

556 PAR2 03 33 84

558 PAR2 03 34 90

560 PAR2 03 37 108

562 PAR2 03 38 114

End of runtime analysis

Re: Problem with Function Module

vinod_vemuru2 — Wed, 02 Jul 2008 15:16:32 GMT

Hi Shankar,

In the function module interface, you can specify only

fields of a specific type and length under "BANKDATA".

Although the currently specified field

"%_OBANKDATA" is the correct type, its length is incorrect.

This shows that while calling this FM what ever internal table u r passing to BANKDATA parameter is not refering to the same structure u r refering in ur FM. Check this thing first. Also check whether ur structures are active or not.

Thanks,

Vinod.