DTP error: Type conflict when calling FM - after transport to Prd

Hi ,
i have asset_attr datasource.it was working in my BW dev.
however after transport to BW prod. when i try to upload data using DTP it gives me an Abrupt error
"0ASSET_ATTR IPDCLNT030 : Type conflict when calling a function module (fiel
Message no. RSDS666"
no more information is given, & the request ends in red.
This is first time i'm using this Infoobject upload.
however all my other transaction data & other master data all are getting uploaded fine.
even Asset_text datasource is working fine.
Did anyone face similiar probs ?
can anyone guide me on this error ?
thanks
ramesh

Hi
Take a look at note 1130907.
Regards,
Chandu.

Similar Messages

Error:Type conflict when calling a function module RFC_ERROR_SYSTEM_Failure

Hi Experts,
When I run my Application in Portal, i am getting the following error.
Type conflict when calling a function module., error key: RFC_ERROR_SYSTEM_FAILURE
When I execute the BAPI, it is getting executed.
My Bapi Strucute:
Import Parameters
IM_MAT_Search --> ZPTIP_MAT --> Import Parameters
Tables
IT_INFO_REC --> ZMM_GET_ITEM --> Output Parameters
When I import the model, i am getting the structure like this
BAPI_Name > ZMM_BAPI_Input> IM_MAT_Search(respective Parameters) , Output (respective Tables and their parameters)
> ZMM_Input1> Parameters
This is the way, how i am executing in webdynpro java
Zmm_Bapi_Ptip_Search_Input eleInput = new Zmm_Bapi_Ptip_Search_Input();
wdContext.nodeZmm_Bapi_Ptip_Search_Input().bind(eleInput);
Zptip_Asset eleInputAsset = new Zptip_Asset();
eleInputAsset.setSearch("ACRS");
wdContext.nodeZptip_Asset().bind(eleInputAsset);
eleInput.setIm_Ast_Search(eleInputAsset);
wdContext.nodeZmm_Bapi_Ptip_Search_Input().bind(eleInput);
wdContext.nodeZmm_Bapi_Ptip_Search_Input().currentZmm_Bapi_Ptip_Search_InputElement().modelObject().execute();
wdContext.nodeOutput().invalidate();
Please let me know, how to do the same.
Thanks in advance.
Regards,
Palani

Hi David,
I checked for the Parameter of setIm_Ast_Search, it is of Zptip_Asset.
Hi Saleem,
When I changed the same, i am getting the Type conflict error,
Type conflict when calling a function module., error key: RFC_ERROR_SYSTEM_FAILURE
Please let me know,what can be done in this regard to solve the problem.
My BAPI Structure when imported as model
SearchBAPI
--> ZMM_BAPI_SEARCH_INPUT
> IM_AST_SEARCH(zPTIP_ASSET)
>Zptip_Asset
>Search (Parameter)
> OutPut(ZMM_BAPI_Search_Output)
>IT_Asser_Rec(ZMM_Asset)
>ZMM_Asset
>TXT100 (output Parameter)
--> ZMM_BAPI_SEARACH_OUTPUT
--> ZPTIP_ASSET
>Search (Parameter)
Thanks & Regards,
Palani
Edited by: Palani Appan on Nov 11, 2009 5:31 PM

ERROR: -Type conflict when calling a function module

hi to all,
when iam executing the program in browser   Type conflict when calling a function module error is showing, i have bind all the attribute correctly still iam getting error, WHEN I CLICK ON THE SEARCH BUTTON DATA IS NOT COMING TO MY TABLE ITAB1 plz help me....
DATA:
      NODE_IP_SELECTION                   TYPE REF TO IF_WD_CONTEXT_NODE,
      ELEM_IP_SELECTION                   TYPE REF TO IF_WD_CONTEXT_ELEMENT,
      STRU_IP_SELECTION                   TYPE IF_PLANNING_HISTORY=>ELEMENT_IP_SELECTION ,
      ITAB TYPE TABLE OF ZSL_PL_UPDATE1,
      WA TYPE ZSL_PL_UPDATE1.
navigate from <CONTEXT> to <IP_SELECTION> via lead selection
    NODE_IP_SELECTION = WD_CONTEXT->GET_CHILD_NODE( NAME = `IP_SELECTION` ).
get element via lead selection
    ELEM_IP_SELECTION = NODE_IP_SELECTION->GET_ELEMENT( ).
get all declared attributes
    ELEM_IP_SELECTION->GET_STATIC_ATTRIBUTES(
      IMPORTING
        STATIC_ATTRIBUTES = STRU_IP_SELECTION ).
CALL FUNCTION 'ZBAPI_PL_UPDATE'
        EXPORTING
          GV_LIFNR           = STRU_IP_SELECTION-LIFNR
          GV_MATNR           = STRU_IP_SELECTION-LIFNR
          GV_GJAHR           = ' '
        GV_WEEK_LOW        =   STRU_IP_SELECTION-FROM_WEEK
         GV_WEEK_HIGH       = STRU_IP_SELECTION-TO_WEEK
      IMPORTING
        RETURN             =
        TABLES
          GT_PL_UPDATE       = ITAB
         DATA:
           NODE_PLANN_NODE                     TYPE REF TO IF_WD_CONTEXT_NODE,
           ELEM_PLANN_NODE                     TYPE REF TO IF_WD_CONTEXT_ELEMENT,
           STRU_PLANN_NODE                     TYPE IF_PLANNING_HISTORY=>ELEMENT_PLANN_NODE,
           WA1 TYPE IF_PLANNING_HISTORY=>ELEMENT_PLANN_NODE,
           ITAB1 TYPE TABLE OF IF_PLANNING_HISTORY=>ELEMENT_PLANN_NODE.
          LOOP AT ITAB INTO WA.
           MOVE-CORRESPONDING WA TO WA1.
           APPEND WA1 TO ITAB1.
          ENDLOOP.
       navigate from <CONTEXT> to <PLANN_NODE> via lead selection
         NODE_PLANN_NODE = WD_CONTEXT->GET_CHILD_NODE( NAME = `PLANN_NODE` ).
         CALL METHOD NODE_PLANN_NODE->BIND_TABLE
           EXPORTING
             NEW_ITEMS            = ITAB1
            SET_INITIAL_ELEMENTS = ABAP_TRUE
            INDEX                =
ENDMETHOD.

CALL FUNCTION 'ZBAPI_PL_UPDATE'
EXPORTING
GV_LIFNR = STRU_IP_SELECTION-LIFNR
GV_MATNR = STRU_IP_SELECTION-LIFNR
GV_GJAHR = ' '
GV_WEEK_LOW = STRU_IP_SELECTION-FROM_WEEK
GV_WEEK_HIGH = STRU_IP_SELECTION-TO_WEEK
IMPORTING
RETURN =
TABLES
GT_PL_UPDATE = ITAB
Problem is here
check out the type GV_GJAHR whether it accepts string type.
thanks
sarbjeet singh

ERM "Unhandled error; type conflict" when clicking Maintain in PFCG button.

I am testing my installation of GRC and when creating a role in ERM with the role designer I click the "Maintain in PFCG" and am receiving an error:
Unhandled error; Type conflict when calling a function module (field length).
I have been doing some searching but have been unable to find a solution for this. I have implemented the items found in SAP Note 1291501 regarding security.
Does anyone have suggestions on what the solution of this problem is or what I can do to troubleshoot this issue more?

Hi Michael,
Can you please share your other details like: What is the GRC AC version you are trying to test and the patch level of ERM and RAR. Try to check the System logs in the Configuration section. Check st22 suggested by Julius and also sm21 in the backend system for system logs . I hope you'll get some hint out of that.
Regards,
Gurugobinda

Type conflict when calling a function module (field length)

Dear All,
            I am getting this following error while executing: Type conflict when calling a function module (field length)
This is piece of coding i have writern in my action button.
method SEARCH_MATERIAL .
data:
        node_mat_input TYPE REF TO if_wd_context_node,
        node_mat_output TYPE REF TO if_wd_context_node,
        material TYPE BAPIMATDET-MATERIAL,
        itab TYPE TABLE OF BAPIMATDOA.
node_mat_input = wd_context->get_child_node( 'NODE_MAT_INPUT' ).
node_mat_output = wd_context->get_child_node( 'NODE_MAT_OUTPUT' ).
node_mat_input->get_attribute( EXPORTING name = 'MATERIAL'
                                 IMPORTING value = material ).
CALL FUNCTION 'BAPI_MATERIAL_GET_DETAIL'
    EXPORTING
      material                    = material
    PLANT                       = plant
    VALUATIONAREA               =
    VALUATIONTYPE               =
    MATERIAL_EVG                =
   IMPORTING
     MATERIAL_GENERAL_DATA       = itab
    RETURN                      =
    MATERIALPLANTDATA           =
    MATERIALVALUATIONDATA       =
node_mat_output->bind_table( itab ).
endmethod.
Attributes are:
Node name = INPUT its structure is BAPIMATDET
INPUT attributes = MATERIAL of type BAPIMATDET-MATERIAL
Thanks,
Gopi.

Hi Amit,
           I have used service call to fetch records from that bapi..
The following is the code generated by service call:-
METHOD execute_bapi_material_get_deta .
declarations for context navigation
DATA:
    node_bapi_material_get_de   TYPE REF TO if_wd_context_node,
     node_exporting   TYPE REF TO if_wd_context_node,
     node_material_general_dat   TYPE REF TO if_wd_context_node,
     node_importing   TYPE REF TO if_wd_context_node,
      lri_element    TYPE REF TO if_wd_context_element.
declarations for fuba parameters
data:
    stru_c_material_general_dat    TYPE if_componentcontroller=>element_material_general_dat.
DATA:
    attr_material    TYPE bapimatdet-material,
    attr_plant    TYPE bapimatall-plant.
get all involved child nodes
node_bapi_material_get_de = wd_context->get_child_node( `BAPI_MATERIAL_GET_DE` ).
node_exporting = node_bapi_material_get_de->get_child_node( `EXPORTING` ).
node_material_general_dat = node_exporting->get_child_node( `MATERIAL_GENERAL_DAT` ).
node_importing = node_bapi_material_get_de->get_child_node( `IMPORTING` ).
get input from context
node_importing->get_attribute(    EXPORTING      name = `MATERIAL`
                                                     IMPORTING      value = attr_material ).
node_importing->get_attribute( EXPORTING       name = `PLANT`
                                                          IMPORTING       value = attr_plant ).
the invocation - errors are always fatal !!!
CALL FUNCTION 'BAPI_MATERIAL_GET_DETAIL'
    EXPORTING
      material =                        attr_material
      plant =                           attr_plant
"      valuationarea =                   wd_This->Valuationarea
"      valuationtype =                   wd_This->Valuationtype
"      material_Evg =                    wd_This->Material_Evg
    IMPORTING
      material_general_data =           stru_c_material_general_dat
"      return =                          wd_This->Return
"      materialplantdata =               wd_This->Materialplantdata
"      materialvaluationdata =           wd_This->Materialvaluationdat
node_material_general_dat->bind_structure( stru_c_material_general_dat[] ).
ENDMETHOD.
                             but the problem is I am getting the following error while compiling...
" stru_c_materialplantdata " is not an internal table - the " OCCOURS n" specification is missing.
Thanks,
Gopi.
Edited by: Yegalaivan on Nov 18, 2009 8:30 AM

TRFC type conflict when calling the function module

Hi,
When I schedule, it is stucking up with TRFC and giving error message in SM58 as" TRFC type conflict when calling the function module" .
even if I execute the trfc LUWs ,load is not successful.
could you please any body suggest for this error.
Thanks
R

Hi Guys,
could any suggest why this is happening.
TRFC is stuck up and giving error message.
Thanks
Ram

Select options field is giving type conflict when calling a class.

hai guys,
i have a field SALESORD in subscreen as a SELECT-OPTIONS field for vbeln.
Now i created a class,with SALESDETAILS of type TABLE as a parameter of a method.
when i call the method(after creating an object) the SALESDETAILS parameter is supposed to take the SALESORD field.
but it gives me a type conflict error.
i wonder why..coz both fileds have same type..
how to resolve the issue..
helpful answers will be rewarded.
thank you.

Hi Shravan,
Pass the select-options vbeln values into a temporary table and pass this table into the method.
<b>Reward for helpful answers</b>
Satish

Type conflict when calling a FORM

Hi,
when we have callled function module "PYXX_READ_PAYROLL_RESULT" in out HR-ABAP program then shows the short dump as:
procedure "PYXX_READ_PAYROLL_RESULT" "(FUNCTION)", nor was it propagated by
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:
Call to FORM "IMPORT_RESULT" is incorrect:
The actual parameter no. 2 has a different data type in the
PERFORM than requested for the FORM "IMPORT_RESULT" in program "%_T02E40".
Please provide the solution any one.
regards,

In the function module PYXX_READ_PAYROLL_RESULT the call to this form is dynamic:
PERFORM import_result IN PROGRAM (subroutine_pool-name)
                                   USING key
                                          payroll_result
                                          import_subrc
                                          pcl2_version_number
                                          typepool_version_number
                             IF FOUND.
As you can see second parameter is payroll_result which is also a changing parameter of the function module PYXX_READ_PAYROLL_RESULT, however it is untyped in the interface of the function module. Therefore, you probably do not supply the function module with the variable of the correct type. My suggestion is to place a break point on the SUBMIT statement, check the content of the subroutine_pool-name, find the program that is called, read its source and determine the right type from there.
Regards

Type conflict when calling a function module.CEI0_COMPARE_CONFIGURATIONS

hi all,
while doing post goods issuse for a delivery causing a following dump
The call to the function module "CEI0_COMPARE_CONFIGURATIONS" is incorrect:
The function module interface allows you to specify only fields
of a particular type under "IV_EXCL_IND". The field "'#'" specified here
has a different field type.
"IV_EXCL_IND" is of type CHAR1 and default is value 2.
in debugging fields is empty, that must be a reason for dump.
please help me out.
regards,
rajyalaxmi

Hello Rajyalaxmi,
Always remember,as a rule of thumb that whenever you call a FM, make sure that the parameters you pass to the FM are of the same data type as they are declared inside the FM. This will avoid CONFLICT DUMPS.
Assign points, if it helps.
Rgds,
Raghu.

Type conflict when calling a function module!

friends,
i have given a F4 value request help for a field in the at selection-screen on value-request for fieldname..but when i click the f4 it's showing dump..
The function module interface allows you to specify only fields of a particular type under "RETFIELD". The field "S_SGLTX-LOW" specified here has a different field type. what could be wrong? thanks all.

Hi,
Actually, we are using the function module for the F4 help that returns the values selected in an internal table. Very handy when programming your very own F4 help for a field.
Here is the sample code.
tables kna1.
data:
begin of t_values occurs 2,
value like kna1-begru,
end of t_values,
t_return like ddshretval occurs 0 with header line.
select-options s_begru for kna1-begru.
at selection-screen on value-request for s_begru-low.
t_values = 'PAR*'.
append t_values.
t_values = 'UGG'.
append t_values.
call function 'F4IF_INT_TABLE_VALUE_REQUEST'
exporting
retfield = 'BEGRU'
value_org = 'S'
tables
value_tab = t_values
return_tab = t_return
exceptions
parameter_error = 1
no_values_found = 2
others = 3.
if sy-subrc = 0.
read table t_return index 1.
endif.
If your problem solved,Kindly reward points by clicking the star on the left of reply.

BPM Error: Timeout condition of pipeline reached- After transporting to Prd

Hi,
I am doing Sync/Async BPM scenario.
-> Receive message and process it and send to BI and response has to send back to the sender.
start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoR/3)->Send(Send Response) ---> stop.
It is working correctly in Test system. We transported to production and we are getting the below error.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
I crossed checked with the test system configuration and evything looks similar. Moreover there are someother Sync/Async BPM scenarios which are all working perfectly.
Kindly help me , What might be the reason. ?
Thanks
Deepthi.

Some of the trace:
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">No mapping required</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="SA_COMM">
<Trace level="1" type="T">Start Sync/Async Communication</Trace>
<Trace level="1" type="Timestamp">2009-08-17T04:48:09Z AUSNSW Starting Processing</Trace>
<Trace level="1" type="T">Pipeline Timeout: 17.08.2009 15:08:10 AUSNSW</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface OS_Payment</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/FOC/DirectSales/Payments</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface AS_Payment</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/SAP_PI/DirectSales/Payment</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>

I am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

i am trying to generate purchase order and i create a BAPI also which is active.
But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Hi,
Yeah i tried my Z_BAPI in R3 and then giving some ERROR.
This is my CODE-
FUNCTION ZBAPIPOTV2.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(POHD) TYPE ZPOHD OPTIONAL
*"     VALUE(POITEM) TYPE ZPOITEM OPTIONAL
*" TABLES
*"      RETURN STRUCTURE BAPIRET1 OPTIONAL
data: ls_pohd type bapimepoheader,
         ls_pohdx TYPE bapimepoheaderx,
         lt_poit TYPE TABLE OF bapimepoitem,
         lt_poitx TYPE TABLE OF bapimepoitemx,
         ls_poit TYPE bapimepoitem,
         ls_poitx TYPE bapimepoitemx.
   MOVE-CORRESPONDING pohd to ls_pohd.
   MOVE-CORRESPONDING poitem to ls_poit.
   ls_pohdx-comp_code = 'x'.
   ls_pohdx-doc_type = 'x'.
   ls_pohdx-vendor = 'x'.
   ls_pohdx-purch_org = 'x'.
   ls_pohdx-pur_group = 'x'.
   ls_poit-po_item = '00010'.
   APPEND ls_poit to lt_poit.
   ls_poitx-po_item = '00010'.
   ls_poitx-po_itemx = 'x'.
   ls_poitx-material = 'x'.
   ls_poitx-plant = 'x'.
   ls_poitx-quantity = 'x'.
   APPEND ls_poitx to lt_poitx.
CALL FUNCTION 'BAPI_PO_CREATE1'
   EXPORTING
     POHEADER                     = ls_pohd
    POHEADERX                    = ls_pohdx
*   POADDRVENDOR                 =
*   TESTRUN                      =
*   MEMORY_UNCOMPLETE            =
*   MEMORY_COMPLETE              =
*   POEXPIMPHEADER               =
*   POEXPIMPHEADERX              =
*   VERSIONS                     =
*   NO_MESSAGING                 =
*   NO_MESSAGE_REQ               =
*   NO_AUTHORITY                 =
*   NO_PRICE_FROM_PO             =
*   PARK_COMPLETE                =
*   PARK_UNCOMPLETE              =
* IMPORTING
*   EXPPURCHASEORDER             =
*   EXPHEADER                    =
*   EXPPOEXPIMPHEADER            =
TABLES
    RETURN                       = return
    POITEM                       = lt_poit
    POITEMX                      = lt_poitx
*   POADDRDELIVERY               =
*   POSCHEDULE                   =
*   POSCHEDULEX                  =
*   POACCOUNT                    =
*   POACCOUNTPROFITSEGMENT       =
*   POACCOUNTX                   =
*   POCONDHEADER                 =
*   POCONDHEADERX                =
*   POCOND                       =
*   POCONDX                      =
*   POLIMITS                     =
*   POCONTRACTLIMITS             =
*   POSERVICES                   =
*   POSRVACCESSVALUES            =
*   POSERVICESTEXT               =
*   EXTENSIONIN                  =
*   EXTENSIONOUT                 =
*   POEXPIMPITEM                 =
*   POEXPIMPITEMX                =
*   POTEXTHEADER                 =
*   POTEXTITEM                   =
*   ALLVERSIONS                  =
*   POPARTNER                    =
*   POCOMPONENTS                 =
*   POCOMPONENTSX                =
*   POSHIPPING                   =
*   POSHIPPINGX                  =
*   POSHIPPINGEXP                =
*   SERIALNUMBER                 =
*   SERIALNUMBERX                =
*   INVPLANHEADER                =
*   INVPLANHEADERX               =
*   INVPLANITEM                  =
*   INVPLANITEMX                 =
ENDFUNCTION.
i am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Error Dynamic type conflict when assigning references in EHP4

Hi Experts,
We are facing problem while customizing application wizard in EHP4.
Based on our requirement, we need to create one more tab named "Notes" to add instructions for applicants while applying for Job. It contains only instruction. To achieve this, we have done below set up.
1. We have created new WD component (WD window), OTR Alias
2. Created one more additional steps in T77RCF_RM_STEP called "Notes" and maintained step 1 information
3. In table T77RCF_RM_SEQ, under Application wizard (employee), we have added notes in sequence 1.
Now our new tab "Notes" is reflecting in application wizard. But while cliking on send application, we are getting error "The following error text was processed in the system GEG : Dynamic type conflict when assigning references".
Error Details:-
u2022     The following error text was processed in the system GEG : Dynamic type conflict when assigning references
u2022     The error occurred on the application server sapgeg_GEG_59 and in the work process 0 .
u2022     The termination type was: RABAX_STATE
u2022     The ABAP call stack was:
Can anybody guide what we are doing wrong?
It would be great help.
Regards,
purnima

Hi Rajasekhar,
     Facing the same issue, can you please let me know how you solved the above issue.
Best Regards,
Laxman

Type conflict at call of a method

HI Guru's,
My name is Sreekar, i am working on FS-RI Workflow. i want to trigger a workflow when status change in standard screen after pressing save button my workflow will trigger.my abap code is follows.
TYPES: BEGIN OF TY_LT_CONTAINER,
               VTGNR TYPE /MSG/RVTG-VTGNR,
               STATUS TYPE /MSG/RVTG-STATUS,
    END OF TY_LT_CONTAINER.
Data: lt_container TYPE TABLE OF ty_lt_container,
         WA_CONTAINER TYPE TY_LT_CONTAINER,
         ls_container type TABLE OF SWCONT,
         wa_ls_container type SWCONT,
         ls_new_status TYPE SWR_WISTAT,
         ls_wi_id TYPE SWR_STRUCT-WORKITEMID,
         lv_sy-subrc TYPE sy-subrc.
*         WA_CONTAINER TYPE Lt_CONTAINER.
if Zstatus NE /MSG/RZ_VTGPER-STATUS.
    BREAK-POINT.
*    WA_ls_container-ELEMENT = 'Treaty'.
*    WA_ls_CONTAINER-VALUE = /MSG/RZ_VTGPER-VTGNR.
    WA_ls_container-ELEMENT = /MSG/RZ_VTGPER-VTGNR.
    WA_ls_CONTAINER-VALUE = /MSG/RZ_VTGPER-STATUS.
    APPEND WA_ls_CONTAINER TO Ls_CONTAINER.
*    wa_ls_container-element =
*    CLEAR WA_CONTAINER.
CALL FUNCTION 'SAP_WAPI_START_WORKFLOW'
EXPORTING
    TASK                      = 'WS90000026'
   LANGUAGE                  = SY-LANGU
   DO_COMMIT                 = 'X'
   USER                      = SY-UNAME
*   START_ASYNCHRONOUS        = ' '
*   DESIRED_START_DATE        =
*   DESIRED_START_TIME        =
*   DESIRED_START_ZONLO       = SY-ZONLO
*   IFS_XML_CONTAINER         =
IMPORTING
*   RETURN_CODE               = lv_sy-subrc
   WORKITEM_ID               = ls_wi_id
   NEW_STATUS                = ls_new_status
TABLES
   INPUT_CONTAINER           = ls_container.
*   MESSAGE_LINES             =
*   MESSAGE_STRUCT            =
*   AGENTS                    =
IF SY-SUBRC NE 0.
   MESSAGE ID 'AT' TYPE 'E' NUMBER '104'. " workflow not trigger
   ELSE.
     MESSAGE ID 'AT' TYPE 'E' NUMBER '103'. " workflow triggered
    endif.
endif.
this is my coding. when i am calling my standard screen with transaction code and i changed the status and after when i press save button i am getting dump
type conflict at call of a method.
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 in
    procedure "SAP_WAPI_START_WORKFLOW" "(FUNCTION)", 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:
    The call of the method "IF_SWF_CNT_CONVERSION_SERVICE~IMPORT_FROM_SIMPLE_CONTAI
    NER" of the class "CL_SWF_CNT_CONVERSION_SERVICE" is incorrect. It was tried
    to transfer a non-compatible variable to the formal parameter "VALUES".
Please help me to get out from this issue.

Hi Sreekar,
The table ls_container should be of type SWR_CONT & not SWCONT.
      ls_container type TABLE OF SWCONT, " Change this to
           ls_container type TABLE OF SWR_CONT, "This is the correct type
Best regards,
Prashant Patil

Dump while testing Function- Dynamic type conflict when assigning reference

Hi Gurus,
I have the following checked and activated-
- Function with 1 Ruleset
- The Ruleset containing couple of DBlookup expressions
- Value range
- Decision Table
- Decision tree,
- Procedure call
After I give test data while Simulating the function, I get this dump-
Short text
    Dynamic type conflict when assigning references
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_FDT_DB_LOOKUP==============CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Have I missed something? We are on SAPKA70207.

Hi Carsten,
I couldn't find an OSS note featuring-
"MOVE_CAST_ERROR" "CX_SY_MOVE_CAST_ERROR"
"CL_FDT_DB_LOOKUP==============CP" or "CL_FDT_DB_LOOKUP==============CM01K"
"BUILD_WHERE_CLAUSE_LIMIT"
Raised OSS note.

DTP error: Type conflict when calling FM - after transport to Prd

Similar Messages

Maybe you are looking for