CX_SY_DYN_CALL_ILLEGAL_TYPE

Hello,
I am calling a function from my BSP application (in do_handle_event) and I am getting this exception..
Following error text processed in system:
An exception with the type CX_SY_DYN_CALL_ILLEGAL_TYPE occurred, but was neither handled locally, nor declared in a RAISING clause
i dont find anything in st22. Has anyone got any idea what might be the problem? The actual and formal parameters looks fine....
any help is greatly appreciated
thanks
thilothama

Hi Thilothama v
1) Just match Import/Export parameters of FM with data type of variables that you are passing to that Fm.They should be exactly same(Check data element).
I assume that you are calling that FM as
"CALL FUNCTION 'FM_ABC' destination none",if its on Same WEB AS or else with appropriate logical system name.
Cheers,
Vijay Raheja

Similar Messages

Error in 'CX_SY_DYN_CALL_ILLEGAL_TYPE' problem in smartfrom printing

Dear Friends,
I developed a code for SD module for RAS GAS invoice. It it I m accessing it through VF02. on output there will be a smartform appered for invoice.
I tested the driver code and smartform individually and had no errors.
I attached the driver code and form through NACE for run time.
Now when I m executing it through VF02 , when I clicked on print preview it throws a error as show.
Plz help me to remove it. Error analysis and piece of code is attached.
Thanx and regards,
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 "PROCESSING"
"(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 "/1BCDWB/SF00000193" is incorrect:
In the function module interface, you can specify only
fields of a specific type and length under "ITVBRK".
Although the currently specified field
"ITVBRK" is the correct type, its length is incorrect.
Information on where terminated
The termination occurred in the ABAP program "ZV_RASGAS " in "PROCESSING".
The main program was "SAPMV60A ".
The termination occurred in line 633 of the source code of the (Include)
program "ZV_RASGAS "
of the source code of program "ZV_RASGAS " (when calling the editor 6330).
Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_TYPE"
occurred in the
procedure "PROCESSING" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "ZV_RASGAS ". Its source code starts in line 58
of the (Include) program "ZV_RASGAS ".
Source code extract
006030 no_function_module = 2
006040 OTHERS = 3.
006050 IF sy-subrc <> 0.
006060 * error handling
006070 cf_retcode = sy-subrc.
006080 PERFORM protocol_update.
006090 ENDIF.
006100 ENDIF.
006110
006120 IF cf_retcode = 0.
006130 PERFORM check_repeat.
006140 IF ls_composer_param-tdcopies EQ 0.
006150 nast_anzal = 1.
006160 ELSE.
006170 nast_anzal = ls_composer_param-tdcopies.
006180 ENDIF.
006190 ls_composer_param-tdcopies = 1.
006200 DO nast_anzal TIMES.
006210 * In case of repetition only one time archiving
006220 IF sy-index > 1 AND nast-tdarmod = 3.
006230 nast_tdarmod = nast-tdarmod.
006240 nast-tdarmod = 1.
006250 ls_composer_param-tdarmod = 1.
006260 ENDIF.
006270 IF sy-index NE 1 AND repeat IS INITIAL.
006280 repeat = 'X'.
006290 ENDIF.
006300 * call smartform invoice
006310 append itvbrp.
006320
> CALL FUNCTION lf_fm_name2
006340 EXPORTING
006350 RDT = rdt
006360 BILSDT = min
006370 BILEDT = max
006380 CUMMMSCM = cummmscm
006390 TPCUMMMBTU = tpcummmbtu
006400 TPCUMSCM = tpcumscm
006410 WS_IVBEL = WS_IVBEL
006420 WS_GVBEL = WS_GVBEL
006430 WS_BVBEL = WS_BVBEL
006440 WS_BILDT = WS_BILDT
006450 TPCUMMMBTUX = TPCUMMMBTUX
006460 GINVNO = inv
006470 BILDOC = BILDOC
006480 ZKBETR = ZKBETR
006490 zlng = zlng
006500 zrc = zrc
006510 zkb = zkb
006520 * VOLUM = VOLUM
thanx and regards,
sitendra

Hi Sitendra,
This exception normally occurs when there is a type mismatch.
Kindly check the length of all fields in the structure/table ITVBRK both in your print program and smartforms. There is a mismatch in the field length of 1 or more of the fields.
Reward points if helpful.
Regards,
Senthil G.

I am geting Exception type CX_SY_DYN_CALL_ILLEGAL_TYPE

Hi,
when i am trying to creat sales order using bapi 'BAPI_SALESORDER_CREATEFROMDAT2' in BSP program iam geting the following exception.
An exception with the type CX_SY_DYN_CALL_ILLEGAL_TYPE occurred, but was neither handled locally, nor declared in a RAISING clause
Exception Class: CX_SY_DYN_CALL_ILLEGAL_TYPE
Error Id:
Program: CL_O2AXZG4R3LD7CRXUAEKYMRHCDL8CP
Include: CL_O2AXZG4R3LD7CRXUAEKYMRHCDL8CM007
Line: 78
Long Text

Hi Nagaraju,
The Type Definitions while using bapi 'BAPI_SALESORDER_CREATEFROMDAT2' should be as follows:
1.)BAPI header type:
types : order_header_in_struc1 type bapisdhead.
2.)BAPI Item row type for Ordered Material and Ordered Quantity.
types : order_items_in_tab1 type table of bapiitemin.
3.)BAPI Item table type for Ordered Material and Ordered Quantity.
types : order_items_in_tab2 type bapiitemin.
4.)BAPI row type for Partner Details.
types : order_partners_tab1 type table of bapipartnr.
5.)BAPI table type for Partner Details.
types : order_partners_tab2 type bapipartnr.
6.)For Sales Document Number
types : sales_doc_number1 type bapivbeln-vbeln.
7.)For return type.
types : RETURN1 type BAPIRETURN1 .
These types should be strictly follwed or else this exception is thrown.
Regards,
Ravikiran.C

Exception with type CX_SY_DYN_CALL_ILLEGAL_TYPE problem

Hi ,
I am facing an Exception error while mapping the data source in Values Fields of a Measure in Balance Scorecard.
The measure is defined using the local System.
The Excepton is :
An Exception with the type CX_SY_DYN_CALL_ILLEGAL_TYPE occured, but wasneither handeledlocally nor delcared in a RAISING clause
Can anyone slove this plz
Thanks
rani

Hi Rani,
This exception normally occurs when there is a type mismatch.
So check your mapping .
Regards,
Siva.

Exception type CX_SY_DYN_CALL_ILLEGAL_TYPE

Hi,
I have two restricted key figures which are restricted on the same Zdate field. I have used different start and end dates variable. And have used different replacement path variables too.
When I run the query it is giving an error message as below:
An exception with the type CX_SY_DYN_CALL_ILLEGAL_TYPE occurred, but was
and
The attempt to call the subroutine HIERATTRIVL_GET in the program &PROGRA
Please help me understand the error and how to rectify it.
Thanks
SAPBW
Message was edited by: SAPBW

Hi Rani,
This exception normally occurs when there is a type mismatch.
So check your mapping .
Regards,
Siva.

Exception CX_SY_DYN_CALL_ILLEGAL_TYPE when calling function

Hello,
When I call a function module, it gives a runtime error like this:
Runtime error CALL_FUNCTION_CONFLICT_TYPE
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
The problem is that I'm using something like below:
call function zzz
exporting
        xxx             = yyy
with:
xxx type char50
yyy type char2
Is there a possibility to transform my char2 into a char50?
By doing this, I would be able to use the function module.
Thanks

hi,
do one thing just make the type and size of both the importing and exporting parameter same...
example:-
data: a(10) type c.   (importing)
data: b(10) type c.       (exporting)
i think this will help u
with regards,
Ritesh J

Runtime Exception: CX_SY_DYN_CALL_ILLEGAL_TYPE

Hi,
In SRM Functional during creation of internal Catalog, when I tried to Add myself as Manage Approvers (to approve Master Catalog Schema) I get this BSP error CX_SY_DYN_CALL_ILLEGAL_TYPE exception.
Unless I add myself to Approvers list to approve Master/Procurement Schemas, Master to Procurement content mapping will not take place.
Please Advise
Raj Rao.

check the below link...
CX_SY_DYN_CALL_ILLEGAL_TYPE
rg
sam

Error CX_SY_DYN_CALL_ILLEGAL_TYPE with READ_TEXT

Hello,
I've created a class to get Notification information for my BSP application. Whenever I test the code, I'm getting CX_SY_DYN_CALL_ILLEGAL_TYPE error for the READ_TEXT FM (trying to get the long text). It looks like all of the Imports are correct, not sure what is wrong. Any help would be greatly appreciated. (This is my first BSP and class, so sorry if this is an easy question).
Thanks in advance,
Lisa

Make sure the parameter..
LINES is TLINE_T type. in the Call.
CX_SY_DYN_CALL_ILLEGAL_TYPE
Cause: The type of actual parameter does not meet the requirements of the function interface.
Runtime Error: CALL_FUNCTION_CONFLICT_GEN_TYP
Cause: The actual parameter does not have the length expected by the function.
Runtime Error: CALL_FUNCTION_CONFLICT_LENG
Cause: The actual parameter does not have the type expected by the function.
Runtime Error: CALL_FUNCTION_CONFLICT_TYPE
Cause: Only functions in the update task that are designed for this purpose may be called.
Runtime Error: CALL_FUNCTION_NO_VB
Cause: An actual parameter does not meet the alignment requirements of the corresponding formal parameter.
Runtime Error: CALL_FUNCTION_WRONG_ALIGNMENT

Error CX_SY_DYN_CALL_ILLEGAL_TYPE

Hello All
I am making progress on my first page thanks to some great help I have received from this community. I now have another question. I am getting the Illegal type error at run time. I have determined that it is the IMPORTING portion of my BAPI that is casuing the error, I just do not know why. First, here is the code I have in the event handler"
DATA: i_notitem type table of t_notitem,
       i_notifcaus type table of t_notifcaus,
       i_notifactv type table of t_notifactv,
       i_notiftask type table of t_notiftask,
       i_notifpartnr type table of t_notifpartnr,
       i_longtexts type table of t_longtexts,
       i_key_relationships type table of t_key_relationships,
       i_return type table of t_return.
DATA: wa_notitem type t_notitem,
       wa_notifcaus type t_notifcaus,
       wa_notifactv type t_notifactv,
       wa_notiftask type t_notiftask,
       wa_notifpartnr type t_notifpartnr,
       wa_longtexts type t_longtexts,
       wa_key_relationships type t_key_relationships,
       wa_return type t_return.
CALL FUNCTION 'BAPI_SERVNOT_GET_DETAIL'
EXPORTING
    NUMBER            = P_QMNUM
IMPORTING
NOTIFHEADER       = BAPI2080_NOTHDRE
NOTIFHDTEXT       = BAPI2080_NOTHDTXTE
TABLES
    NOTLONGTEXT       = i_longtexts
    NOTITEM           = i_notitem
    NOTIFCAUS         = i_notifcaus
    NOTIFACTV         = i_notifactv
    NOTIFTASK         = i_notiftask
    NOTIFPARTNR       = i_notifpartnr
    RETURN            = i_return.
Based on other comments, I defined both BAPI2080_NOTHDRE and BAPI2080_NOTHDTXTE in the type definitions tab as:
types: htab1 type standard table of BAPI2080_NOTHDRE .
types: htab2 type standard table of BAPI2080_NOTHDTXTE.
I then declared them in the Page Attributes as:
BAPI2080_NOTHDRE TYPE HTAB1
BAPI2080_NOTHDTXTE TYPE HTAB2
When I still received the error, I went into the structure of the BAPI and confirmed that I had the right data types:
function bapi_servnot_get_detail.
""Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(NUMBER) LIKE BAPI2080_NOTHDRE-NOTIF_NO
*" EXPORTING
*"     VALUE(NOTIFHEADER) LIKE BAPI2080_NOTHDRE
*"       STRUCTURE BAPI2080_NOTHDRE
*"     VALUE(NOTIFHDTEXT) LIKE BAPI2080_NOTHDTXTE
*"       STRUCTURE BAPI2080_NOTHDTXTE
*" TABLES
*"      NOTLONGTEXT STRUCTURE BAPI2080_NOTFULLTXTE OPTIONAL
*"      NOTITEM STRUCTURE BAPI2080_NOTITEME OPTIONAL
*"      NOTIFCAUS STRUCTURE BAPI2080_NOTCAUSE OPTIONAL
*"      NOTIFACTV STRUCTURE BAPI2080_NOTACTVE OPTIONAL
*"      NOTIFTASK STRUCTURE BAPI2080_NOTTASKE OPTIONAL
*"      NOTIFPARTNR STRUCTURE BAPI2080_NOTPARTNRE OPTIONAL
*"      RETURN STRUCTURE BAPIRET2 OPTIONAL
One posting suggested that you needed to add DESTINATION NONE to the end of the BAPI, but when I did that I got a CX_SY_DYN_CALL_ILLEGAL_FUNC error
Not sure what to do now
John
Edited by: John Esposito on Mar 24, 2010 3:00 PM

Thank you. hopefully this is a better copy to read.
I am making progress on my first page thanks to some great help I have received from this community. I now have another question. I am getting the Illegal type error at run time. I have determined that it is the IMPORTING portion of my BAPI that is casuing the error, I just do not know why.
First, here is the code I have in the event handler:
DATA: i_notitem type table of t_notitem,
       i_notifcaus type table of t_notifcaus,
       i_notifactv type table of t_notifactv,
       i_notiftask type table of t_notiftask,
       i_notifpartnr type table of t_notifpartnr,
       i_longtexts type table of t_longtexts,
       i_key_relationships type table of t_key_relationships,
       i_return type table of t_return.
DATA: wa_notitem type t_notitem,
       wa_notifcaus type t_notifcaus,
       wa_notifactv type t_notifactv,
       wa_notiftask type t_notiftask,
       wa_notifpartnr type t_notifpartnr,
       wa_longtexts type t_longtexts,
       wa_key_relationships type t_key_relationships,
       wa_return type t_return.
clear: BAPI2080_NOTHDRE.
refresh: i_notitem,
         i_notifcaus,
         i_notifactv,
         i_notiftask,
         i_notifpartnr,
         i_longtexts.
CALL FUNCTION 'BAPI_SERVNOT_GET_DETAIL'
EXPORTING
    NUMBER            = P_QMNUM
IMPORTING
NOTIFHEADER       = BAPI2080_NOTHDRE
NOTIFHDTEXT       = BAPI2080_NOTHDTXTE
TABLES
    NOTLONGTEXT       = i_longtexts
    NOTITEM           = i_notitem
    NOTIFCAUS         = i_notifcaus
    NOTIFACTV         = i_notifactv
    NOTIFTASK         = i_notiftask
    NOTIFPARTNR       = i_notifpartnr
    RETURN            = i_return
Based on other comments, I defined both BAPI2080_NOTHDRE and BAPI2080_NOTHDTXTE in the type definitions tab as
types: htab1 type standard table of BAPI2080_NOTHDRE.
types: htab2 type standard table of BAPI2080_NOTHDTXTE.
I then declared them in the Page Attributes as:
BAPI2080_NOTHDRE TYPE HTAB1
BAPI2080_NOTHDTXTE TYPE HTAB2
When I still received the error, I went into the structure of the BAPI and confirmed that I had the right data types: function bapi_servnot_get_detail.
VALUE(NOTIFHEADER) LIKE BAPI2080_NOTHDRE
*"       STRUCTURE BAPI2080_NOTHDRE
*"     VALUE(NOTIFHDTEXT) LIKE BAPI2080_NOTHDTXTE
*"       STRUCTURE BAPI2080_NOTHDTXTE
T
John

CALL_FUNCTION_CONFLICT_TYPE Standard Data loading

Hi,
I am facing a data loading problem using Business content on CPS_DATE infocube (0PS_DAT_MLS datasource).
The R/3 extraction processes without any error, but the problem occurs in the update rules while updating the milestone date. Please find hereunder the log from the ST22.
The real weird thing is that the process works perfectly in development environment and not in integration one (the patch levels are strongly the same: BW 3.5 Patch #16).
I apologise for the long message below... this is a part of the system log.
For information the routine_0004 is a standard one.
Thanks a lot in advanced!
Cheers.
 CALL_FUNCTION_CONFLICT_TYPE
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
Symptoms. Type conflict when calling a function module
Causes Error in ABAP application program.
 The current ABAP program "GP420EQ35FHFOCVEBCR6RWPVQBR" 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.
Errors 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 "ROUTINE_0004"
 "(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 "RS_BCT_TIMCONV_PS_CONV" is incorrect:
The function module interface allows you to specify only fields of a particular type under "E_FISCPER".
 The field "RESULT" specified here is a different field type.
How to correct the error.
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_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC
 "GP420EQ35FHFOCVEBCR6RWPVQBR" or "GP420EQ35FHFOCVEBCR6RWPVQBR"
 "ROUTINE_0004"
 If you cannot solve the problem yourself and you wish to send
 an error message to SAP, include the following documents:
 1. A printout of the problem description (short dump)
 To obtain this, select in the current display "System->List->
 Save->Local File (unconverted)". 2. A suitable printout of the system log To obtain this, call the system log through transaction SM21. Limit the time interval to 10 minutes before and 5 minutes after the short dump. In the display, then select the function
 "System->List->Save->Local File (unconverted)".
 3. If the programs are your own programs or modified SAP programs, supply the source code.
 To do this, select the Editor function "Further Utilities-> Upload/Download->Download".
 4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
 The exception must either be prevented, caught within the procedure
 "ROUTINE_0004"
 "(FORM)", or declared in the procedure's RAISING clause.
 To prevent the exception, note the following:
Environment system SAP Release.............. "640"
Operating system......... "SunOS" Release.................. "5.9"
Hardware type............ "sun4u"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 2
Short dump setting....... "full"
Database type............ "ORACLE"
Database name............ "BWI"
Database owner........... "SAPTB1"
Character set............ "fr"
SAP kernel............... "640"
Created on............... "Jan 15 2006 21:42:36" Created in............... "SunOS 5.8 Generic_108528-16 sun4u"
Database version......... "OCI_920 "
Patch level.............. "109"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version..... "640"
Operating system......... "SunOS 5.8, SunOS 5.9, SunOS 5.10"
SAP Release.............. "640"
The termination occurred in the ABAP program "GP420EQ35FHFOCVEBCR6RWPVQBR" in
 "ROUTINE_0004".
 The main program was "RSMO1_RSM2 ".
The termination occurred in line 702 of the source code of the (Include)
 program "GP420EQ35FHFOCVEBCR6RWPVQBR"
 of the source code of program "GP420EQ35FHFOCVEBCR6RWPVQBR" (when calling the editor 7020).
 Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_TYPE" occurred in the procedure "ROUTINE_0004" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.
 The procedure is in the program "GP420EQ35FHFOCVEBCR6RWPVQBR ". Its source code starts in line 685 of the (Include) program "GP420EQ35FHFOCVEBCR6RWPVQBR ".
672 'ROUTINE_0003' g_s_is-recno
673 rs_c_false rs_c_false g_s_is-recno
674 changing c_abort.
675 catch cx_foev_error_in_function.
676 perform error_message using 'RSAU' 'E' '510'
677 'ROUTINE_0003' g_s_is-recno
678 rs_c_false rs_c_false g_s_is-recno
679 changing c_abort.
680 endtry.
681 endform.
682 ************************************************************************
683 * routine no.: 0004
684 ************************************************************************
685 form routine_0004
686 changing
687 result type g_s_hashed_cube-FISCPER3
688 returncode like sy-subrc
689 c_t_idocstate type rsarr_t_idocstate
690 c_subrc like sy-subrc
691 c_abort like sy-subrc. "#EC *
692 data:
693 l_t_rsmondata like rsmonview occurs 0 with header line. "#EC *
694
695 try.
696 * init
variables
697 move-corresponding g_s_is to comm_structure.
698
699 * fill the internal table "MONITOR", to make monitor entries
700
701 * result value of the routine
>>>> CALL FUNCTION 'RS_BCT_TIMCONV_PS_CONV'
703 EXPORTING
704 I_TIMNM_FROM = '0CALDAY'
705 I_TIMNM_TO = '0FISCPER'
706 I_TIMVL = COMM_STRUCTURE-CALDAY
707 I_FISCVARNT = gd_fiscvarnt
708 IMPORTING
709 E_FISCPER = RESULT.
710 * if the returncode is not equal zero, the result will not be updated
711 RETURNCODE = 0.
712 * if abort is not equal zero, the update process will be canceled
713 ABORT = 0.
714
715 catch cx_sy_conversion_error
716 cx_sy_arithmetic_error.
717 perform error_message using 'RSAU' 'E' '507'
718 'ROUTINE_0004' g_s_is-recno
719 rs_c_false rs_c_false g_s_is-recno
720 changing c_abort.
721 catch cx_foev_error_in_function.
System zones content
Name Val.
SY-SUBRC 0
SY-INDEX 2
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 65
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY 0400
SY-UCOMM OK
SY-TITLE Moniteur - Atelier d'administration
SY-MSGTY E
SY-MSGID RSAU
SY-MSGNO 583
SY-MSGV1 BATVC 0000000000
SY-MSGV2 0PROJECT
SY-MSGV3
SY-MSGV4
Selected variables
Nº 23 Tpe FORM
Name ROUTINE_0004
GD_FISCVARNT
 22
 00 RS_C_INFO I
 4
 9
COMM_STRUCTURE-CALDAY
20060303
33333333
20060303
SYST-REPID GP420EQ35FHFOCVEBCR6RWPVQBR 4533345334444454445355555452222222222222 704205135686F365232627061220000000000000
RESULT
000
333
00

You have an update routine in which youar callin FM 'RS_BCT_TIMCONV_PS_CONV'. Parameter e_fiscper must be the same that type of the variable you use (you can see the data tyoe in FM definition, transaction se37). You should do somethin like the following.
DATA: var type <the same that e_fiscper in FM definition>
CALL FUNCTION 'RS_BCT_TIMCONV_PS_CONV'
EXPORTING
I_TIMNM_FROM = '0CALDAY'
I_TIMNM_TO = '0FISCPER'
I_TIMVL = COMM_STRUCTURE-CALDAY
I_FISCVARNT = gd_fiscvarnt
IMPORTING
E_FISCPER = var.
result = var.
--- ASSIGN POINTS IS USEFUL.

Error when using BAPI

Please find herewith my below code. This program i have created for transferring goods with mvt type '657' to '555' using BAPI 'BAPI_GOODSMVT_CREATE' for TCODE MB1A.
*& Report Z_BAPI_FOR_MB1A
REPORT Z_BAPI_FOR_MB1A.
Tables : mkpf, mseg, WB2_V_MKPF_MSEG2.
DATA:
it_mb1a LIKE BAPI2017_GM_ITEM_CREATE OCCURS 0 WITH HEADER LINE,
it_return LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE,
it_ex_headret LIKE BAPI2017_GM_HEAD_RET OCCURS 0 WITH HEADER LINE,
it_im_header LIKE BAPI2017_GM_HEAD_01, " OCCURS 0, " WITH HEADER LINE,
it_im_gmcode LIKE BAPI2017_GM_CODE, " OCCURS 0, "WITH HEADER LINE,
mat_doc type bapi2017_gm_head_ret-mat_doc,
mat_docyear type bapi2017_gm_head_ret-doc_year.
*data : lv_intense(01).
data : it_mseg like WB2_V_MKPF_MSEG2 occurs 0 with header line,
       it_cost like csks occurs 0 with header line.
selection-screen begin of block a with frame title text-001.
parameters: p_date type sy-datum default sy-datum.
select-options: so_budat for WB2_V_MKPF_MSEG2-budat,
                so_werks for WB2_V_MKPF_MSEG2-werks_i,
                so_matnr for WB2_V_MKPF_MSEG2-matnr_i,
                so_lgort for WB2_V_MKPF_MSEG2-lgort_i.
selection-screen end of block a.
select * from WB2_V_MKPF_MSEG2 into
table it_mseg where
budat in so_budat and
werks_i in so_werks and
matnr_i in so_matnr and
lgort_i in so_lgort and
bwart_i = '657'.
select * from csks into table it_cost
for all entries in it_mseg where
gsber = it_mseg-werks_i.
*Filling BAPI Header Tables
it_im_header-pstng_date = sy-datum.
it_im_header-doc_date = sy-datum.
it_im_gmcode-gm_code = '03'.
*Filling BAPI Item Tables
loop at it_mseg.
read table it_cost with key gsber = it_mseg-werks_i.
it_mb1a-material = it_mseg-matnr_i.
it_mb1a-plant = it_mseg-werks_i.
it_mb1a-stge_loc = it_mseg-lgort_i.
it_mb1a-batch = it_mseg-charg_i.
it_mb1a-move_type = 555. " '103'.
it_mb1a-entry_qnt = it_mseg-menge_i.
it_mb1a-costcenter = it_cost-KOSTL.
it_mb1a-gl_account = '530089'.
append it_mb1a.
clear it_mb1a.
clear it_cost.
endloop.
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
EXPORTING
    goodsmvt_header               = it_im_header
    goodsmvt_code                 = it_im_gmcode
*   TESTRUN                       = ' '
*   GOODSMVT_REF_EWM              =
IMPORTING
   GOODSMVT_HEADRET              = it_ex_headret
   MATERIALDOCUMENT              = mat_doc
   MATDOCUMENTYEAR               = mat_docyear
tables
    goodsmvt_item                 = it_mseg
*   GOODSMVT_SERIALNUMBER         =
    return                        = it_return
*   GOODSMVT_SERV_PART_DATA       =
*   EXTENSIONIN                   =
if sy-subrc = 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
   WAIT          = 'X'
* IMPORTING
*   RETURN        =
endif.
But when i execute the above i am getting the following error.
Runtime Errors         CALL_FUNCTION_UC_STRUCT
Except.                CX_SY_DYN_CALL_ILLEGAL_TYPE
Date and Time          27.01.2009 14:43:06
Short text
     Type conflict during structure parameter transfer at CALL FUNCTION.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "Z_BAPI_FOR_MB1A" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was
      not caught and
     therefore caused a runtime error.
     The reason for the exception is:
     In the function "BAPI_GOODSMVT_CREATE", the STRUCTURE parameter "GOODSMVT_ITEM"
      is typed in such a way
     that only actual parameters are allowed, which are compatible in Unicode
      with respect to the fragment view. However, the specified actual
     parameter "IT_MSEG" has an incompatible fragment view.
Missing Handling of System Exception
     Program                                 Z_BAPI_FOR_MB1A
Trigger Location of Exception
    Program                                 Z_BAPI_FOR_MB1A
    Include                                 Z_BAPI_FOR_MB1A
    Row                                     72
    Module Name                             START-OF-SELECTION
Source Code Extract
Line SourceCde
   42 lgort_i in so_lgort and
   43 bwart_i = '657'.
   44
   45 select * from csks into table it_cost
   46 for all entries in it_mseg where
   47 gsber = it_mseg-werks_i.
   48 *Filling BAPI Header Tables
   49 it_im_header-pstng_date = sy-datum.
   50 it_im_header-doc_date = sy-datum.
   51 it_im_gmcode-gm_code = '03'.
   52
   53 *Filling BAPI Item Tables
   54 loop at it_mseg.
   55
   56 read table it_cost with key gsber = it_mseg-werks_i.
   57
   58 it_mb1a-material = it_mseg-matnr_i.
   59 it_mb1a-plant = it_mseg-werks_i.
   60 it_mb1a-stge_loc = it_mseg-lgort_i.
   61 it_mb1a-batch = it_mseg-charg_i.
   62 it_mb1a-move_type = 555. " '103'.
64 it_mb1a-costcenter = it_cost-KOSTL.
65 it_mb1a-gl_account = '530089'.
66
67 append it_mb1a.
68 clear it_mb1a.
69 clear it_cost.
70 endloop.
71
72*>>>> CALL FUNCTION 'BAPI_GOODSMVT_CREATE'* 73   EXPORTING
74     goodsmvt_header               = it_im_header
75     goodsmvt_code                 = it_im_gmcode
76 *   TESTRUN                       = ' '
77 *   GOODSMVT_REF_EWM              =
78 IMPORTING
79    GOODSMVT_HEADRET              = it_ex_headret
80    MATERIALDOCUMENT              = mat_doc
81    MATDOCUMENTYEAR               = mat_docyear
82   tables
83     goodsmvt_item                 = it_mseg
84 *   GOODSMVT_SERIALNUMBER         =
85     return                        = it_return
86 *   GOODSMVT_SERV_PART_DATA       =
87 *   EXTENSIONIN                   =
88           .
89 if sy-subrc = 0.
90 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
91 EXPORTING
Can u explain why this is coming. Your valuable suggestions are required.
Thanks,
Jitesh M Nair

Hi,
Try this Code.
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
        EXPORTING
          GOODSMVT_HEADER       = WF_HEADER
          GOODSMVT_CODE         = WF_CODE
          TESTRUN               = WL_space
        IMPORTING
          MATERIALDOCUMENT      = FS_MATERIAL_DOC
        TABLES
          GOODSMVT_ITEM         = INT_ITEM
          GOODSMVT_SERIALNUMBER = INT_SERIALNO
          RETURN                = INT_RETURN1.
*VARIABLES for goods movement creation bapi
DATA : WF_HEADER TYPE   BAPI2017_GM_HEAD_01,
       WF_CODE    TYPE   BAPI2017_GM_CODE.
DATA : FS_MATERIAL_DOC   TYPE BAPI2017_GM_HEAD_RET-MAT_DOC,
       FS_SERIALNO       TYPE BAPI2017_GM_SERIALNUMBER,
       FS_ITEM           TYPE BAPI2017_GM_ITEM_CREATE,
       FS_RETURN1        TYPE BAPIRET2,
data declaration for goods movement creation bapi
DATA : INT_ITEM     TYPE TABLE OF BAPI2017_GM_ITEM_CREATE,
       INT_SERIALNO TYPE TABLE OF BAPI2017_GM_SERIALNUMBER,
       INT_RETURN1 TYPE TABLE OF BAPIRET2.
Hope this will help.
Regards,
Rohan.

"CALL_FUNCTION_CONFLICT_TYPE" runtime error while running tcode BPS0 in BW

Hi ,
Can anybody have any idea about this dump error in BW quality system while user running tcode BPS0 and getting this dump repeatedly please help me out on this.
Error in the ABAP Application Program
The current ABAP program "SAPLZBSV_BPS_E_PLA_VARIABLES" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
A function module was called incorrectly.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE'
     not caught in
    procedure "CHECK_FILE_ENTRIES2" "(FORM)", nor was it propagated by a RA
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The call to the function module "RSD_CHKTAB_GET_FOR_CHA_BAS" is incorre
    The function module interface allows you to specify only
    fields of a particular type under "E_CHNTAB".
    The field "L_TABNM" specified here is a different
    field type
How to correct
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_CONFLICT_TYPE" "CX_SY_DYN_CALL_ILLEGAL_TYPE"
"SAPLZBSV_BPS_E_PLA_VARIABLES" or "LZBSV_BPS_E_PLA_VARIABLESF01"
"CHECK_FILE_ENTRIES2"
Thanks & Regards
    Rituraj

Hello,
I get the answer. In program personal_data is associated with bapip0002 structure.
where as in function personal_data is associated with BAPIP0002B. and the structure of BAPIP0002 is differ to BAPIP0002B.
minaxi shah

ECC = SNC ReplenishmentOrderNotification custom message through SAP PI

Helllo,
I have one issue during proxy call in SNC. We are implementing SNC system with our ECC 6.0 system for PO processing, PO Confirmation Processing. The interfaces used is the standard SNC PI package from SAP through SAP PI; however, we have extended PO IDOCs in ECC for some Z-fields and created a new message type in SAP PI and mapped them properly. The problem, when it reached SNC, I checked the XML message and it was as expected with the new Z-fields but when the inbound proxy is called, I got the following error:
Error during proxy processing An exception with the type CX_SY_DYN_CALL_ILLEGAL_TYPE occurred, but was neither handled locally, nor declared in a RAISING clause The function call of /SCA/BIF_REPLORD_BO failed; a field may have been assigned to the parameter IS_REPLORD_NOTIF whose type is not compatible with this parameter
it seems that the newly generated service interface is not reconginzing the new ReplenishmentOrderNotification message structure with the Z-fields
How can we resolve this issue and make the inbound proxy reconginze the new message stucture?
By the way, I found this Badi: BAdI for ReplenishmentOrderNotification_In? and I have no clue how it works if we need to implement it?
Thank you,

Hi Alan,
Please check below threads.
1. INTERFACE_REGISTRATION_ERROR (inbound ABAP proxy)
2. ABAP ->INTERFACE_REGISTRATION_ERROR for outboud sync ABAP proxy
3. INTERFACE_REGISTRATION_ERROR using File-to-File method
Regards,
Deepak

If Excise invoice required for finished goods.

Hi All
I have doubt, whether excise invoice is required for finished goods or not. As I am trying to create MIGO doc for PO of finished material, and it is saying, no excise invoice possible for finished material RG1.
Can you advise please.
Regards
Mukta

HI
Thanks for this. When we are executing Utilization transaction J2IU, it is giving dump after prompting popup with 'Data will be lost PLA NCCD B35', 'No record selected , excise invoice cancelled'.
Run time error is saying -
Short text
    Structure-type conflict when calling a FORM
What happened?
    Error in the ABAP Application Program
    The current ABAP program "J_1IRUTZ" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was
not caught and
therefore caused a runtime error.
The reason for the exception is:
The call of the FORM "DETERMINE_DEFAULT_VALUES" is incorrect:
The actual parameter no. 2 is at PERFORM not compatible with the
structure type requested by FORM "DETERMINE_DEFAULT_VALUES".
The FORM "DETERMINE_DEFAULT_VALUES" is defined in program "SAPMJ1II".
This error occurs in Unicode if the fragment view of the types is
incompatible.
Can some one suggest if we need to apply any OSS NOTE.
Regards
Mukta

ERROR WHILE USING SO_NEW_DOCUMENT_ATT_SEND_API1

An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was
not caught in
procedure "ENTRY_NEU" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
In the function "SO_NEW_DOCUMENT_ATT_SEND_API1", the STRUCTURE parameter
"CONTENTS_HEX" is typed in such a way
that only actual parameters are allowed, which are compatible in Unicode
with respect to the fragment view. However, the specified actual
parameter "I_OBJBIN" has an incompatible fragment view.
*Declararions Used
*Internal Table declarations
DATA: i_otf TYPE itcoo OCCURS 0 WITH HEADER LINE,
i_tline TYPE TABLE OF tline WITH HEADER LINE,
i_receivers TYPE TABLE OF somlreci1 WITH HEADER LINE,
i_record LIKE solisti1 OCCURS 0 WITH HEADER LINE,
*Objects to send mail.
i_objpack LIKE sopcklsti1 OCCURS 0 WITH HEADER LINE,
i_objtxt LIKE solisti1 OCCURS 0 WITH HEADER LINE,
i_objbin LIKE solisti1 OCCURS 0 WITH HEADER LINE,
i_reclist LIKE somlreci1 OCCURS 0 WITH HEADER LINE,
*Work Area declarations
w_objhead TYPE soli_tab,
w_ctrlop TYPE ssfctrlop,
w_compop TYPE ssfcompop,
w_return TYPE ssfcrescl,
w_doc_chng typE sodocchgi1,
w_data TYPE sodocchgi1,
w_buffer TYPE string,"To convert from 132 to 255
Please help me thanks in advance
Points will be rewarded

Sending External Mail via ABAP
REPORT ZSENDEXTERNAL.
DATA: OBJPACK   LIKE SOPCKLSTI1 OCCURS 2 WITH HEADER LINE.
DATA: OBJHEAD   LIKE SOLISTI1 OCCURS 1 WITH HEADER LINE.
DATA: OBJBIN    LIKE SOLISTI1 OCCURS 10 WITH HEADER LINE.
DATA: OBJTXT    LIKE SOLISTI1 OCCURS 10 WITH HEADER LINE.
DATA: RECLIST   LIKE SOMLRECI1 OCCURS 5 WITH HEADER LINE.
DATA: DOC_CHNG LIKE SODOCCHGI1.
DATA: TAB_LINES LIKE SY-TABIX.
Creation of the document to be sent
File Name
DOC_CHNG-OBJ_NAME = 'SENDFILE'.
Mail Subject
DOC_CHNG-OBJ_DESCR = 'Send External Mail'.
Mail Contents
OBJTXT = 'Minimum bid : $250000'.
APPEND OBJTXT.
OBJTXT = 'A representation of the pictures up for auction'.
APPEND OBJTXT.
OBJTXT = 'was included as attachment.'.
APPEND OBJTXT.
DESCRIBE TABLE OBJTXT LINES TAB_LINES.
READ TABLE OBJTXT INDEX TAB_LINES.
DOC_CHNG-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + STRLEN( OBJTXT ).
Creation of the entry for the compressed document
CLEAR OBJPACK-TRANSF_BIN.
OBJPACK-HEAD_START = 1.
OBJPACK-HEAD_NUM = 0.
OBJPACK-BODY_START = 1.
OBJPACK-BODY_NUM = TAB_LINES.
OBJPACK-DOC_TYPE = 'RAW'.
APPEND OBJPACK.
Creation of the document attachment
(Assume that the data in OBJBIN is in BMP format)
*OBJBIN = ' \O/ '. APPEND OBJBIN.
*OBJBIN = ' | '. APPEND OBJBIN.
*OBJBIN = ' / \ '. APPEND OBJBIN.
*DESCRIBE TABLE OBJBIN LINES TAB_LINES.
*OBJHEAD = 'PICTURE.BMP'.
*APPEND OBJHEAD.
Creation of the entry for the compressed attachment
*OBJPACK-TRANSF_BIN = 'X'.
*OBJPACK-HEAD_START = 1.
*OBJPACK-HEAD_NUM = 1.
*OBJPACK-BODY_START = 1.
*OBJPACK-BODY_NUM = TAB_LINES.
*OBJPACK-DOC_TYPE = 'BMP'.
*OBJPACK-OBJ_NAME = 'PICTURE'.
*OBJPACK-OBJ_DESCR = 'Representation of object 138'.
*OBJPACK-DOC_SIZE = TAB_LINES * 255.
*APPEND OBJPACK.
Completing the recipient list
RECLIST-RECEIVER = '[email protected]'.
RECLIST-REC_TYPE = 'U'.
APPEND RECLIST.
*RECLIST-RECEIVER = 'SAPUSERNAME'.
*RECLIST-REC_TYPE = 'P'.
*APPEND RECLIST.
Sending the document
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
   DOCUMENT_DATA = DOC_CHNG
   PUT_IN_OUTBOX = 'X'
TABLES
   PACKING_LIST = OBJPACK
   OBJECT_HEADER = OBJHEAD
   CONTENTS_BIN = OBJBIN
   CONTENTS_TXT = OBJTXT
   RECEIVERS = RECLIST
EXCEPTIONS
   TOO_MANY_RECEIVERS = 1
   DOCUMENT_NOT_SENT = 2
   OPERATION_NO_AUTHORIZATION = 4
OTHERS = 99.
CASE SY-SUBRC.
   WHEN 0.
   WRITE: / 'Result of the send process:'.
LOOP AT RECLIST.
   WRITE: / RECLIST-RECEIVER(48), ':'.
   IF RECLIST-RETRN_CODE = 0.
      WRITE 'The document was sent'.
   ELSE.
      WRITE 'The document could not be sent'.
ENDIF.
ENDLOOP.
WHEN 1.
   WRITE: / 'No authorization for sending to the specified number',
            'of recipients'.
WHEN 2.
   WRITE: / 'Document could not be sent to any recipient'.
WHEN 4.
   WRITE: / 'No send authorization'.
WHEN OTHERS.
   WRITE: / 'Error occurred while sending'.
ENDCASE.
Reward if helpful
Regards
Vodka.

CX_SY_DYN_CALL_ILLEGAL_TYPE

Similar Messages

Maybe you are looking for