Error with the FIELD CAT function module.

Hi folks,
This was the error message i had got from the FIELDCAT function module.
An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_READ_SRC_LINE_TOO_LONG', was
     not caught in
    procedure "K_KKB_FIELDCAT_MERGE" "(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:
    There was an attempt to read program "/A1SSPC/ITP_SCH_REP" from the database.
    The READ REPORT statement allows you to copy a program text into an
    internal table. The occupied line length in the program text must not
    exceed the width of the internal table.
    The internal table "\FUNCTION=K_KKB_FIELDCAT_MERGE\DATA=???" is 72 characters
     wide. The program line is
    204 characters wide.
Reg,
Hariharan

You can do this
TYPE-POOLS:slis.
DATA: it_vabp TYPE STANDARD TABLE OF vbap WITH HEADER LINE.
DATA: it_fieldcat TYPE slis_t_fieldcat_alv.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
EXPORTING
   i_program_name               = sy-repid
   i_internal_tabname           = 'IT_VBAP'
   i_inclname                   = sy-repid
  CHANGING
    ct_fieldcat                  = it_fieldcat
* EXCEPTIONS
*   INCONSISTENT_INTERFACE       = 1
*   PROGRAM_ERROR                = 2

Similar Messages

  • Error in the SAP standard function module 'RSDRI_INFOPROV_READ'.

    Hello Experts,
    We upgraded from 3.5 to 7,0 support pack 17 .
    After upgrade we are getting error
      with return code 11 'Others´'.
    While debugging the standard function module we found that the standard method s_r_infoprov->read is being executed with the return code = 8 (inherited_error).
    Any suggestions?
    Regards,
    Vivek

    Not sure if the parameters provided were correct,you may wish to do a sanity check
    Input Parameters:
    1. I_INFOPROV - This will hold the Name of the Info Cube from where we need the pull the data.
    2. I_T_SFC - This parameter is in the format of Internal Table which holds the Character Info Objects we need to pull from the Source Cube.
    3. I_T_SFK - This parameter is also in the format of Internal Table which holds the Key Figure Info Objects which we need to pull from the Source Cube.
    4. I_T_RANGE - This is also in the format of Internal Table which holds the Selection criteria for which we need to pull from the Source Cube u2013 For example the Company Code u2013 001 and Fiscal Year Period u2013 001/2006.
    5. I_T_REQUID u2013 Selection of cube data based on Request Id.
    6. I_SAVE_IN_TABLE u2013 In case you need to save the data in DB table
    7. I_REFERENCE_DATE u2013 This holds the current date.
    8. I_AUTHORITY_CHECK u2013 This will hold the value u2018Ru2019, which is meant for READ.
    9. I_DEBUG u2013 This is for Debugging mode and holds the default value u2018Yu2019.
    Output Parameters:
    1. E_T_DATA u2013 This Output Parameter is of internal table format, in which we can mention the output fields (For all the fields mentioned in the Input Parameter, this output parameter will hold the values).
    2. E_END_OF_DATA u2013 Once the FM is executed successfully, this output parameter will hold the value u2018Xu2019, means extraction completed successfully.
    Hope it Helps
    Chetan
    @CP..

  • Error with data transfer in functional module

    Hi all,
    I need to upload file to the employee through BDS. (oaor transcation).  i am using functional module
    function zin_bds_dms_upload.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(P_CLASS) TYPE  BDN_CON-CLASSNAME
    *"     VALUE(P_OBJCT) TYPE  BDN_CON-OBJKEY
    *"     VALUE(P_DESCR) TYPE  BDN_CON-DESCRIPT
    *"     REFERENCE(P_PATH) TYPE  SAPB-SAPFILES
      data: begin of i_bds_conn occurs 10, " ITAB for the actual
             bdn_tab_i type  num08,
            client type mandt,
            classname type      seoclsname,
            classtype     type bds_clstyp,
            objkey  type  bds_typeid,
            log_system    type swo_typeid,
            loio_id   type char42,
            doc_ver_no    type num08,
            doc_var_id    type num08,
            doc_var_tg    type bds_var_tg,
            descript    type sdok_descr,
            langu   type spras,
            comp_id   type bds_compid,
            mimetype  type  bds_mimetp,
            crea_user   type sdok_crusr,
            crea_time   type sdok_crtst,
            chng_user   type sdok_chusr,
            chng_time   type sdok_chtst,
            contrep   type bds_conrep,
            docuclass   type sdok_prv_m,
            doc_type    type sdok_prv_s,
            expirytime    type sdok_prv_m,
            bds_docid   type sdok_prv_l,
            loio_id_to    type sdok_loid,
            rela_id     type      bds_relaid,
            state   type sdok_phsta,
            bds_status    type bds_state,
            stor_tab  type saearstat,
            bdn_tab_d     type bar_keep,
            note_type     type bds_state,
            objecttext type toasp-objecttext,
            objecttext2 type toasd-objecttext,
            objecttext3 type toasr-objecttext,
            ntext type tojtt-ntext,
    end of i_bds_conn.
      data: begin of bds_doctype_list occurs 10,
      mandt type mandt,
      classname type bapibds01-classname,
      contrep type bapibds01-contrep,
      docuclass type bapibds01-doc_class,
      docuclass_text type toasd-objecttext,
      doc_type type bapibds01-doc_type,
      doc_type_text type toasp-objecttext,
      appl_type type toadd-appl_type,
      appl_type_text(50) type c,
      standard type toadv-standard,
      check_box type toadv-standard,
      end of bds_doctype_list.
      data: file_extension type toadd-doc_type, " file-extension
      i_files type bapifiles occurs 1 with header line,
      i_signature type bapisignat occurs 1 with header line,
      logical_system type bds_conn00-log_system.
      data: classname_select type bdn_con-classname,
      classtype_select type bdn_con-classtype,
      objkey_select type bdn_con-objkey,
      mask(20) type c,
      answer type c,
      mimetype type toadd-mimetype,
      i_toadd type toadd,
      file_path type sapb-sapfiles,
      filename_all type sapb-sapfiles,
      file_path_memory(250) type c, " path für SAP memory
      file_path_length type i, " length of the file_path
      file_name type sapb-sapfiles.
      classname_select = p_class.
      classtype_select = 'BO'.
      objkey_select = p_objct.
      filename_all = p_path.
      get parameter id 'OAP' field file_path.
      if sy-subrc <> 0. " no file_path found.
        file_path = space.
      endif.
      concatenate ',.' '' ',.' '' '.' into mask.
    -- split filename -- *
      perform split_path(oaall) using filename_all file_path file_name.
    -- set new file_path to SAP memory -- *
      file_path_length = strlen( file_path ).
      if file_path <> space and file_path_length < 250.
        file_path_memory = file_path.
        set parameter id 'OAP' field file_path_memory.
      else.
        file_path_memory = space.
        set parameter id 'OAP' field file_path_memory.
      endif.
    -- check documentclass -- *
      perform get_file_extension using file_name
      file_extension.
    -- check file extension -- *
      if file_extension = space.
    -> if no docuclass is found from the document
    -> default docuclass from the doctype!
        file_extension = bds_doctype_list-docuclass.
      endif.
    -- get the mimetype of the docuclass -- *
      perform mimetype_get(oaall) using file_extension
      changing i_toadd.
      move i_toadd-mimetype to mimetype.
    -- fill file and signature structure -- *
      clear: i_files, i_signature.
      refresh : i_files, i_signature.
      i_files-doc_count = 1.
      i_files-directory = file_path.
      i_files-filename = file_name.
      i_files-mimetype = mimetype.
      append i_files.
      i_signature-doc_count = 1.
      i_signature-prop_name = 'BDS_DOCUMENTCLASS'.
      i_signature-prop_value = file_extension.
      append i_signature.
      i_signature-prop_name = 'BDS_CONTREP'.
      if bds_doctype_list-contrep = space.
        i_signature-prop_value = ' '.                           "#EC NOTEXT
      else.
        i_signature-prop_value = bds_doctype_list-contrep.
      endif.
      append i_signature.
      i_signature-prop_name = 'BDS_DOCUMENTTYPE'.
      i_signature-prop_value = bds_doctype_list-doc_type.
      append i_signature.
      i_signature-prop_name = 'DESCRIPTION'.
      i_signature-prop_value = p_descr.
      append i_signature.
      i_signature-prop_name = 'LANGUAGE'.
      i_signature-prop_value = sy-langu.
      append i_signature.
    -- create new document via KPro -- *
      call function 'BDS_BUSINESSDOCUMENT_CREATEF'
        exporting
          logical_system = logical_system
          classname      = classname_select
          classtype      = classtype_select
          client         = sy-mandt
          object_key     = objkey_select
        tables
          files          = i_files
          signature      = i_signature
        exceptions
          internal_error = 1
          others         = 2.
    endfunction.
    *& Form GET_FILE_EXTENSION
    try to get the extension of the uploaded file
    form get_file_extension using file_name file_extension.
    -- data declaration ------------------------------------------------ *
      data: length type i,
      single_c type c.
      data: begin of bds_doctype_list occurs 10,
      mandt type mandt,
      classname type bapibds01-classname,
      contrep type bapibds01-contrep,
      docuclass type bapibds01-doc_class,
      docuclass_text type toasd-objecttext,
      doc_type type bapibds01-doc_type,
      doc_type_text type toasp-objecttext,
      appl_type type toadd-appl_type,
      appl_type_text(50) type c,
      standard type toadv-standard,
      check_box type toadv-standard,
      end of bds_doctype_list.
      clear: single_c.
      length = strlen( file_name ).
      if length > 0.
        while length > 0.
          single_c = file_name+length(1).
          if single_c co '.'.
            length = length + 1.
            exit.
          else.
            length = length - 1.
          endif.
        endwhile.
        if length > 0.
          file_extension = file_name+length.
        else.
          file_extension = space.
        endif.
      else.
        file_extension = space.
      endif.
      if file_extension <> space.
        set locale language sy-langu.
        translate file_extension to upper case.              "#EC TRANSLANG
        set locale language space.
      endif.
    endform.                    "get_file_extension
    example  : class = PREL
    object = pernr_no
    desc =  'leav application'
    p_path = file_path
    I used this in abap program then it is uploading fine but when used in the web dynpro file is not uploading. On debugging it is showing error in function module SDOK_PHIOS_CHECKIN
    error key 5 ie error in transfer.
    So please suggest how to upload in web dynpro abap.
    Edited by: Bhavya belagal on Dec 22, 2010 11:55 AM
    Edited by: Bhavya belagal on Dec 22, 2010 12:09 PM

    Hallo Bhavya,
    Please do not post like this as it is not readable . Mostly when you describe it in a simple manner you would get more response.
    See this thread for answers from Thomas Jung [Re: Approach content repository other way then URL approach|Re: Approach content repository other way then URL approach]
    Wiki [http://wiki.sdn.sap.com/wiki/display/WDABAP/File%2bUpload%2busing%2bcl_fitv_gos%2bclass|http://wiki.sdn.sap.com/wiki/display/WDABAP/File%2bUpload%2busing%2bcl_fitv_gos%2bclass]
    Edited by: Baskaran Senthivel on Dec 22, 2010 2:42 PM

  • Error in the creation of function module

    hi,
            pls help me i am getting the error "Only tables with simple line structure are   allowed in RFC" pls give me solution to solve this problem.

    Hi Mukka,
    You tables parameters contains a structure which contains nested structure within it. You have to remove that structure from it and have to include or append it so that you can bring that parameter.
    Thanks,
    Samantak.
    <b>Rewards points for useful answers.</b>

  • Error with quantity field:Datasource Creation Using Function Module method

    Problem with DATASOURCE Creation using Function Module method :
    I have created a datasource ZSTANDARD_COST_PRICE using Function Module method . The datasource creation is successfull when I remove the quantity field from the Z table . If I dont remove the quantity field from my Z table it gives an error as "Units Field WAERS for field STPRS of datasource ZSTANDARD_COST_PRICE is hidden". I am not able to remove this error . Please someone guide.
    Let me know if my explanation is not clear enough.
    Thanks in advance,
    Neha.
    Z table definition is as below :
    MATNR MATNR CHAR 18 0 Material Number
    BWKEY BWKEY CHAR 4 0 Valuation area
    LFGJA LFGJA NUMC 4 0 Fiscal Year of Current Period
    STPRS STPRS CURR 11 2 Standard Price   " Here the currency field is WAERS and table T001
    PEINH PEINH DEC 5 0 Price Unit
    VJSTP VJSTP CURR 11 2 Standard price in previous year
    VJPEI VJPEI DEC 5 0 Price unit of previous year.
    Edited by: Neha Rathi on Jan 30, 2009 3:03 PM

    Hi,
    You should add it as one of the main fields as you have added other fields and not as the currency fields...that is..it should be part of the data source and you should be able to see it in RSO2...
    Also if added as i said then it will come as new field in the data source...you can either let it be there...or hide it..
    also if you want to populate it then you will have to write the code for this fields as well.
    Thanks
    Ajeet

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

  • Errors with the global conversion rule for the field 0SOURSYSTEM.

    Hello Gurus,
        We are implementing CRM Activities. I enhanced the data source and when I add new info objects to 0SAL_DS01 DSO and trying to activate I'm getting there errors. Can some one please help me out in this problem?
    Error in global conversion rule for InfoObject 0SOURSYSTEM
    Message no. RSAR263
    Diagnosis
    Errors with the global conversion rule for the field 0SOURSYSTEM.
    System Response
    The function module delivers the following error message:
    Field "" is unknown. It is neither in one of t
    Procedure
    Check the definition of the global conversion rule for an InfoObject
    What does this error mean? We are using BI 7.
    Thanks
    RKR

    I have around 9 source systems, do I have to maintain data for all of them for 0SOURCESYSTEM?
    I set data for CRM system and then tried to activate.. but still I'm getting same error.
    I;m getting this warning too...
    InfoObject 0FISCVARNT needs to be in key for DataStore object C_0SAL_D
    Message no. RSDODSO123
    Diagnosis
    Characteristic 0FISCVARNT is included in the data part of ODS object C_0SAL_D.
    System Response
    The fiscal year variant cannot be used in the update rules for calculating business hour characteristics.
    Does this matter???
    Thanks
    RKR
    Message was edited by:
            RKR M

  • Communication error with the LOCAL_EXEC Function BAPI_PTMGREXTATTABS_CHECK

    Hello,
    We use timesheet (CATS) in a separate SAP system from the SAP system in which HR resides.
    I found out how the loosely coupled scenario with CATS works with a SAP HR system. We transfer the workschedule and absence data with report RPTIMEOVERVIEW_REPLICATE to the SAP system in which CATS is used. This data is then available in the PTIMEOV1 table to perform time checks in CATS. The distribution model for ALE takes care of the fact that the data is posted into table PTIMEOV1. With BD97 I set up that the BAPI: PTMGREXTATTABS.CHECK has RFCdestination for synchronous calls  = LOCAL_EXEC.
    When I want to record on an attendance code without clock times then the above works fine. The SAP system in which CATS resides looks into table PTIMEOV1. So far so good.
    However, when I want to record hours WITH clock times then I cannot save the data. The error message HRTIM00CATS667 shows up:
    "Communication error with the LOCAL_EXEC Function BAPI_PTMGREXTATTABS_CHECK is no t available  system"
    Diagnosis
    An error has occured during communication with the HR System. The HR data in the time sheet cannot be validated.
    From the error message description it seems that it wants to check the SAP HR system instead of looking for the check in the SAP system in which CATS resides.....
    When I change the value from LOCAL_EXEC to the system in which HR resides then the error disappears, but then it really checks into the SAP HR system (synchronous check with that SAP HR system) and that is not what the customer wants. The check should be local on the PTIMEOV1 table (in case the SAP HR system is down).
    I did not find any OSS notes on the topic....or other info on SDN.
    Can anyone help me out concerning this starnge error message, at least for me?
    Thanks very much in advance,
    Kind regards,
    Mirko

    "A point to add"
    I just noticed that following message is being continously receiving in the database alert_log:
    Sat Oct 9 16:04:52 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:05:32 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:06:30 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:07:10 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:09:35 2010
    Incremental checkpoint up to RBA [0x1d.1f9928.0], current log tail at RBA [0x1d.1f9a79.0]
    Sat Oct 9 16:11:52 2010
    WARNING: inbound connection timed out (ORA-3136)
    Sat Oct 9 16:29:40 2010
    Incremental checkpoint up to RBA [0x1d.1f9b87.0], current log tail at RBA [0x1d.1f9bf4.0]
    ~
    Please help.

  • Field catalog does not agree with the fields of the functional area

    G'day everyone,
    I am using a generic extractor via infoset to extract data from R/3 source system.
    Using RSA3, I have obtained an error message and no further details.
    ****ERROR MESSAGE
    "Field catalog does not agree with the fields of the functional area
    Message no. RSUQ134
    ****ERROR MESSAGE
    I have checked and adjusted my infoset in SQ02 and they seems fine but still obtain the same error.
    In BW, replicated the datasource and activate the transfer rules but still obtain the same error.
    Anyone knows how to get more details for this type of error? Or how to fix this problem?
    Regards
    Wayne

    I think I have just solved it.
    Transaction RS02 delete and recreate after checking the structure in BW and Source system are the same.
    Cheers

  • Errors occurred during call of function module BUPR_EMPLO_DELETE

    when distributing employee data from (HCM) to (CRM) there is an error that appears in relation with the settings for the Business Parner:
    "Errors occurred during call of function module BUPR_EMPLO_DELETE
    Message no. R11335
    Diagnosis
    The business partner BAPIs were called up incorrectly. The indicator IV_X_SAVE was given differing settings when the modules were called.
    Within a LUW, the indicator must be consistently set or not set.
    System Response
    The indicator IV_X_SAVE should be set or not set once off. Up to COMMIT WORK the content of the field may not be changed, as problems will otherwise occur with the internal memory, thus leading to runtime errors."
    This prevents CRM to be updated with the changes. Kindly help me on the same.

    Hi Sai,
    This is too late to reply this post, but to let everyone know about the issue I am posting here.
    Start new UI session and put breakpoint at BUPR_EMPLO_DELETE and check parameter IV_X_SAVE everytime, till you get the error message. The parameter IV_X_SAVE should be same/consistent (either ' ' or 'X') in whole Logical Unit of Work. It should not change in between.
    I faced the same kind of problem and found that standard was passing IV_X_SAVE = ' ' and in our custom code we were passing IV_X_SAVE = 'X'. I changed it to IV_X_SAVE = ' ' and my problem got resolved.
    You can try the same. Please post the alternate solution if you find it.
    Best Regards,
    Rahul Koshti

  • How to write the exceptions in function module

    dear all,
         how to write the exceptions in function modules with example.
    thanq
    jyothi

    Hi,
    Raising Exceptions
    There are two ABAP statements for raising exceptions. They can only be used in function modules:
    RAISE except.
    und
    MESSAGE.....RAISING except.
    The effect of these statements depends on whether the calling program handles the exception or not. The calling program handles an exception If the name of the except exception or OTHERS is specified after the EXCEPTION option of the CALL FUNCTION statement.
    If the calling program does not handle the exception
    · The RAISEstatement terminates the program and switches to debugging mode.
    · The MESSAGE..... RAISING statement displays the specified message. Processing is continued in relation to the message type.
    If the calling program handles the exception, both statements return control to the program. No values are transferred. The MESSAGE..... RAISING statement does not display a message. Instead, it fills the system fields sy-msgid, sy-msgty, sy-msgno , and SY-MSGV1 to SY-MSGV4.
    Source Code of READ_SPFLI_INTO_TABLE
    The entire source code of READ_SPFLI_INTO_TABLE looks like this:
    FUNCTION read_spfli_into_table.
    ""Local Interface:
    *" IMPORTING
    *" VALUE(ID) LIKE SPFLI-CARRID DEFAULT 'LH '
    *" EXPORTING
    *" VALUE(ITAB) TYPE SPFLI_TAB
    *" EXCEPTIONS
    *" NOT_FOUND
    SELECT * FROM spfli INTO TABLE itab WHERE carrid = id.
    IF sy-subrc NE 0.
    MESSAGE e007(at) RAISING not_found.
    ENDIF.
    ENDFUNCTION.
    The function module reads all of the data from the database table SPFLI where the key field CARRID is equal to the import parameter ID and places the entries that it finds into the internal table spfli_tab. If it cannot find any entries, the exception NOT_FOUND is triggered with MESSAGE ... RAISING. Otherwise, the table is passed to the caller as an exporting parameter.
    Calling READ_SPFLI_INTO_TABLE
    The following program calls the function module READ_SPFLI_INTO_TABLE:
    REPORT demo_mod_tech_fb_read_spfli.
    PARAMETERS carrier TYPE s_carr_id.
    DATA: jtab TYPE spfli_tab,
    wa LIKE LINE OF jtab.
    CALL FUNCTION 'READ_SPFLI_INTO_TABLE'
    EXPORTING
    id = carrier
    IMPORTING
    itab = jtab
    EXCEPTIONS
    not_found = 1
    OTHERS = 2.
    CASE sy-subrc.
    WHEN 1.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno.
    WHEN 2.
    MESSAGE e702(at).
    ENDCASE.
    LOOP AT jtab INTO wa.
    WRITE: / wa-carrid, wa-connid, wa-cityfrom, wa-cityto.
    ENDLOOP.
    The actual parameters carrier and jtab have the same data types as their corresponding interface parameters in the function module. The exception NOT_FOUND is handled in the program. It displays the same message that the function module would have displayed had it handled the error.
    Or
    just have to decide what exceptions u want and under what conditions.
    then declarethese exeptions under the exceptions tab.
    in the source code of ur function module.
    if
    like this u can code .
    now when u call the function module in tme mainprogram.
    if some error occurs and u have declared a exception for this then it will set sy-subrc = value u give inthe call of this fm.
    in the fm u can program these sy-subrc values and trigger the code for ur exception.
    Please reward if useful
    Regards,
    Ravi
    Edited by: Ravikanth Alapati on Mar 27, 2008 9:36 AM

  • URGENT : Error: Please create data processing function module

    Hi
    I am getting the folloiwng error
    "Please create data processing function module" in table maintainence.
    It is working fine in dev environment but not in QA and production.
    Pleae help.
    Regards
    Kalpesh

    Hi Kalpesh,
       I see it is something to do with the naming convention used in the quality and production system. These must have been setup differently compared to ur development system. So check with different naming conventions.
    Reward points if helpful.
    Cheers
    Shafiq

  • FF_5 - Import Bank Statement, Err: Formatting error in the field COBL-KOSTL

    Hi
    When importing the bank statement I'm getting the error
    Error: (00 298) Formatting error in the field COBL-KOSTL ; see next message
    Why is it doing this? In OKB9 I have the GL Account and the cost center assigned. It is the ne GL that is giving this problem, in the classic GL I do not have this problem.
    Thanks in advance

    Hi
    No, it is not that. For some reason in the new GL it does not seem to determine the cost centers and profit centers as usual.
    For exampl to allocate the Profit Center for Balance Sheet Account I used to use 3KEH in the classic gl but in the New gl we must use FAGL3KEH.
    Now with cost center i'm having the same problem, does not determine the cost center when importing the bank statement.
    Can someone help me.
    Thanks in advance
    Edited by: Louis De Gouveia on Mar 3, 2009 7:07 AM

  • How to raise the exception in function module

    Dear abaper's.
                   I am creating a Function module .In that in' EXCEPTION' Tab i am giving
    3 exception .1.NO_DATA_FOUND 2.NO_PRINTER_FOUND 3.SMARTFORM_INTERFACE_NOT_FOUND.
    In my coding if this condtion matches i want to raise this exception.how can i do this in my coding .can any one suggest me..
    advance thanks,
    Warm regards,
    Veera

    Hi,
    if that condition is not satisfied,and u didn't handle that exception while calling function module then in the runtime error u will get the text as the description of the exception in function module definition.
    rgds,
    bharat.

  • Formal error: Invalid calling sequence for function modules

    Hi All,
    I have developed a function module for FQEVENT 620 Payment: Transfer Line Items for Clearing.
    The clearing works fine.
    After clearing the open items i need to post an FI-CA Document(BAPI : BAPI_CTRACDOCUMENT_CREATE) for each open item(cleared item)
    I have used the bapi : BAPI_CTRACDOCUMENT_CREATE in the same function module that i have developed for FQEVENT 620 Payment: Transfer Line Items for Clearing.Here i am getting an error "Formal error: Invalid calling sequence for function modules".
    So please let me know where i can use this bapi to post fi-ca document.Is there a BAdi or Enhancement Spot where i can use this BAPI or tell me what should i do to overcome this error.
    Regards
    Venkat

    Venkat:
    While I am confused about your business process - creating an open item when clearing one seems strange.  Look into event 0020 which is called after documents are posted - it may present the opportunity to post process additional documents.
    regards,
    bill.

Maybe you are looking for

  • Lost downloads

    Hi, My mother accidently put the downloads folder from the dock into trash! I can find the folder in her hard drive but when I drag it to put it back into the Dock the computer seems to want to put it into the project gallery which for some reason is

  • Adding a new song with a different computer..?

    Ok. I'm on vacation in Costa Rica right now, and I'm using my aunt's computer. My iPod already has music on it, which I put into it on my computer from Texas. A while ago, I downloaded a song and I would really like to put it on my iPod...so I downlo

  • How to increase the length of a columnin existing publication item

    We need to urgently increase the length of three columns in one of the tables that is sent offline as a publication item. I have searched everywhere to see if there is a procedure to see this. I only found process to add/drop columns but not modify t

  • How to call PL-SQL script/stored procedure from BPEL?

    Assume I want to call a PL-SQL stored procedure from BPEL. How can I do this? Is there a simple "Hello world" example for this? Peter

  • Solstice x.400 9.0---kernel panic starting osimta daemon

    Help! After installing this sw stack: Solaris8 Disksuite 4.2 and simple mirrored filesystems Solstice x.25 9.1 HP NNM Solstice x.400 9.0 and after registering the licenses the system crashes at boot. Any idea about solution? Thanks in advance anyway