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

Similar Messages

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

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

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

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.

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)".

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.

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

Problem in transfer rules-- Calling the function module.

Hi All,
when we r extracting the data from r3, the infoobject 0wbs_elem the data pulled is in internal format in which wbs element is stored.
wbs element gets stored in a different way compared to front end.
Eg. The external format is /abc/123 the internal format is 00012300.
I have written a transfer routine using the function module CONVERSION_EXIT_ABPSP_OUTPUT.
the code goes like this
data ifield(30) type c.
call function CONVERSION_EXIT_ABPSP_OUTPUT
Exporting
input = tran_structure-wbselem (Field in transfer structure---name of the field in source system) .
Importing
output = ifield.
result = ifield.
End of code.
Problem
When I am Scheduling the package the job doesnt get completed for a long time and fails.Is there a problem with the code. When trying for the Simulation of the datapackets, the system says no data package number could be determined.
Please help me out...
Thank You
Mahesh

Hi Mahesh,
Could you please check ST22 and see if there is any short dumps ?
try to do test run for the FMs using SE37 and see what is the output for your input.
Do you have PSA for the load ? It may also have been deleted. You get this message when there is no PSA available.
hope it helps
Thanks
Soumya

Error when call RFC Function module in R/3

Dear All,
We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
we are facing the error "Error while lookup Exception during processing the payload. Error when calling an adapter by using the communication channel CC_PPPI_MES_RFC_Rcvr (Party: , Service: WCD_320, Object ID: 16563889b449328eac76caa6a3bc592e) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'."
This is the first time we are doing this configuration.
Could you please let me know what woulbe the reason.

read the original message
We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
I am talking about the above Receiver RFC channel which you guys are using to call R/3 from XI. That where you need to change the commit parameter

How can I call the function module of the ECC when I save the campaign?

HI Experts!
I want to call function module of the ECC when I click the save button in the campaign view,A badi or userexit is needed,but I don't find, can you tell me which badi or userexit is used to implement?

Thanks a lot.
I have tried,but it can't do.
who can tell me which badi and detailed implementation step?
waiting on line.

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

Time Constraint Error when calling a Function module from Webdynpro ABAP

Any help will be greatly appreciated - Thanks RM
Time Constraint Error
Information on where terminated
    Termination occurred in the ABAP program "SAPUP50R" - in
     "CHECK_TIME_CONSTRAINT_S1".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 1069
    of the (Include) program "UP50RU01".
Error occurred during batch input processing
Source Code Extract
      l_is_inconsistent = 'X'.
    ENDIF.
Check if there are inverted time periods.
    IF l_prelp_line-begda > l_prelp_line-endda.
      l_is_inconsistent = 'X'.
    ENDIF.
Check if there are overlaps or gaps.
    IF NOT l_prelp_before IS INITIAL.
      l_date_difference = l_prelp_line-begda - l_prelp_before-endda.
      IF l_date_difference <> 1.
        l_is_inconsistent = 'X'.
      ENDIF.
    ENDIF.
    l_prelp_before = l_prelp_line.
ENDLOOP.
IF l_prelp_before-endda <> '99991231'.
    l_is_inconsistent = 'X'.
ENDIF.
IF l_is_inconsistent = 'X'.
    IF p_access_type = 'R'.
490 Datenbankschiefstand Personalnummer & Infotyp &
      MESSAGE x490 WITH l_prelp_before-pernr l_prelp_before-infty.
    ELSE.
491 Unzulässige Daten Personalnummer & Infotyp &
Line 1069 Error occcurs >>>> MESSAGE x491 WITH l_prelp_before-pernr l_prelp_before-infty.
    ENDIF.
ENDIF.
ENDFORM.                    " CHECK_TIME_CONSTRAINT_S1     "XYVN0352581
*&      Form clear_no_adapter_needed              new     "XREN844998
      text
FORM clear_no_adapter_needed .
CLEAR no_adapter_needed.
ENDFORM.                    " clear_no_adapter_needed
*&      Form set_no_adapter_needed              new     "XREN844998
      text
FORM set_no_adapter_needed .
no_adapter_needed = 'X'.
ENDFORM.                    " clear_no_adapter_needed

Hi,
Well, are you trying to do a batch input on infotype 0000? If yes you need to check that the proposed values respects the time constraint, meaning no gap, no overlaps and no inversions. Also fields SUBTY, OBJPS, SPRPS and SEQNR must remain initial when processing IT0000...
Kr,
Manu.

Time Constraint Error when calling a Function Module

Any help will be greatly appreciated - Thanks RM
Time Constraint Error
Information on where terminated
Termination occurred in the ABAP program "SAPUP50R" - in
"CHECK_TIME_CONSTRAINT_S1".
The main program was "MP000000 ".
In the source code you have the termination point in line 1069
of the (Include) program "UP50RU01".
Error occurred during batch input processing
Source Code Extract
l_is_inconsistent = 'X'.
ENDIF.
Check if there are inverted time periods.
IF l_prelp_line-begda > l_prelp_line-endda.
l_is_inconsistent = 'X'.
ENDIF.
Check if there are overlaps or gaps.
IF NOT l_prelp_before IS INITIAL.
l_date_difference = l_prelp_line-begda - l_prelp_before-endda.
IF l_date_difference 1.
l_is_inconsistent = 'X'.
ENDIF.
ENDIF.
l_prelp_before = l_prelp_line.
ENDLOOP.
IF l_prelp_before-endda '99991231'.
l_is_inconsistent = 'X'.
ENDIF.
IF l_is_inconsistent = 'X'.
IF p_access_type = 'R'.
490 Datenbankschiefstand Personalnummer & Infotyp &
MESSAGE x490 WITH l_prelp_before-pernr l_prelp_before-infty.
ELSE.
491 Unzulässige Daten Personalnummer & Infotyp &
Line 1069 Error occcurs >>>> MESSAGE x491 WITH l_prelp_before-pernr l_prelp_before-infty.
ENDIF.
ENDIF.
ENDFORM. " CHECK_TIME_CONSTRAINT_S1 "XYVN0352581
*& Form clear_no_adapter_needed new "XREN844998
text
FORM clear_no_adapter_needed .
CLEAR no_adapter_needed.
ENDFORM. " clear_no_adapter_needed
*& Form set_no_adapter_needed new "XREN844998
text
FORM set_no_adapter_needed .
no_adapter_needed = 'X'.
ENDFORM. " clear_no_adapter_needed

Hi,
Well, are you trying to do a batch input on infotype 0000? If yes you need to check that the proposed values respects the time constraint, meaning no gap, no overlaps and no inversions. Also fields SUBTY, OBJPS, SPRPS and SEQNR must remain initial when processing IT0000...
Kr,
Manu.

TRFC type conflict when calling the function module

Similar Messages

Maybe you are looking for