Remote function module is not compilable, normal function is not

Hi,
i have a function module with processing type "normal function", which is compilable and working well. I'm using the type definition ABAP_COMPNAME.
If i change the function module to "remote-enabled", i'm getting a compiler error that ABAP_COMPNAME is unknown.
Can someone explain why this is happening? For what reason ABAP_COMPNAME is no longer available when i'm chnaging the FM to remote enabled?
PS Please dont give any hints how to change my function module, that is NOT the question. I just want to understand the mechanism behind.

It is clearly mentioned in SAP Help that we cannot use types from type-pool
in RFC function modules.
Associated Type of an Interface Parameter
ABAP associated type for an interface parameter. The associated type must be a
global Dictionary  type or exist in a type pool. In the latter case, the type pool must
be declared in the function group.
Note that you cannot use types from type pools for RFC-enabled function modules.
When assigning a type using the LIKE typ method, you cannot use types from
type pools either.
Additionally you can use the internal ABAP types C, I, N, X, P, D, T, F, and the
TABLE type - to an extent in generic form.
You can find further information about this in the Function Builder manual and in the
ABAP online documentation under the keyword "Types".

Similar Messages

  • Function module used for ENQUEUE_EIQMEL & DEQUEUE_EIQMEL function

    Hi All,
    It should be highly appreciable if any one could please help.
    I need the name of the function module used for ENQUEUE_EIQMEL & DEQUEUE_EIQMEL function.
    waiting for help.
    Thanks
    Shaw

    Hi,
    The names 'ENQUEUE_EIQMEL' and 'DEQUEUE_EIQMEL ' you have mentioned are itself the function modules. Which other FM's you need i didnt understand.
    These are FM to ahndle lock objects 'QMEL'.
    please reframe your question in case of further issues.
    Regards,
    Mansi.

  • Remote Enabled function module of SAP working - debug mode but not run mode

    Hi,
    When a remote function module is called from Java a message should get thrown from the function module which the FM is throwing but Java is not able to fetch the error. This problem is coming in execution mode but if we are in debugging mode and go to the function module  remotely the error is getting triggered.
    Please suggest the solution to the problem.
    Thanks,
    Abhishek

    Hello
    try something like this
    try {
       JCO.Client.execute(myFunction)
    } catch (JCO.AbapException ex) {
       System.out.println ("ABAP Exception: " + ex.getKey() + " " + ex.getMessage());
    the problem is, that JCo ABAP Exceptions are subclasses of java.lang.RuntimeException so the Java Compiler doesn't force you to catch them
    regards franz
    reward points if useful

  • Running Function Module in Background with Update Task is not working

    Hello Friends,
    I have a "Z" Report Program where I am running this Report in Background using JOB_OPEN, JOB_SUBMIT, JOB_CLOSE. I am calling this in BADI.
    In this Report I am calling another Function Module PRICES_POST which is a standard Function Module and in this FM there is another FM 'CKML_UPDATE_MATERIAL_PRICE IN UPDATE TASK'. Now when I am running the BADI these values are not being updated.
    Friends I would like to know whether can we run Function Modules which are  included with UPDATE TASK as Background Job program?
    Kindly help me in providing your valuable suggestions in proceeding further.
    Thanks and Regards
    Pradeep Goli

    Usually the sequence of CALLs in your report should look like
      CALL FUNCTION 'CM_F_INITIALIZE'
        EXPORTING
          msg_on_screen = c_x.
      CALL FUNCTION 'CKMS_BUFFER_REFRESH_COMPLETE'.
      CALL FUNCTION 'PRICES_CHANGE'
        EXPORTING
          actual_bdatj = f_matpr-pp-bdatj
          actual_poper = f_matpr-pp-poper
          bukrs        = p_bukrs
          budat        = p_date
          xblnr        = p_xblnr
        TABLES
          t_matpr      = t_matpr.
      READ TABLE t_matpr WITH KEY pp-xerror = ' '
                                TRANSPORTING NO FIELDS.
      IF sy-subrc <> 0.
        MESSAGE i046(ckprch).
      ELSE.
        CALL FUNCTION 'PRICES_POST'
          EXPORTING
            i_bktxt    = p_bktxt
            bukrs      = p_bukrs
            lis_update = 'X'
          TABLES
            t_matpr    = t_matpr.
      ENDIF.
      COMMIT WORK.
    If you forget the COMMIT-WORK each and every FM called in UPDATE TASK will not be triggered.
    Regards,
    Raymond

  • Data Services XI3.1 function module files for SAP R/3 is not working

    Hi guys,
    Thank you for the quick response so far. I am very grateful to you all. 
    I got an issue and will try to explain as detail as I could and 
    hope ur guys won't mind. :P
    I pass the functions module to SAP tech guy to install to SAP using CTS 
    method, and using 900086.R63 file type because my chinese client is 
    running SAP on unicode environment.
    My DS installed on my laptop client; job server plus db2 is on HP 
    unix. SAP is on another HP Unix server. The function module I used is 
    supplied from Data Services XI3.1.
    Anyway, the installation is successfully done with GUI wizard windows of 
    SAP Workbench instead of tp command line method.
    1)However, I checked the ZAW0 function group, I opened and can't see any functions
    listed under it, although the table structures ZACTA, ZTAB2048 and other items
    were created.
    2)So I tried to create SAP Datastore, Transport Target, etc and tried to 
    extract file. It failed and log said "can't open file --- 
    /db2/temp/curcode.txt". I checked and SAP working directory /db2/temp didn't have 
    curcode.txt, because the result file supposed to be extracted and stored there. 
    The SAP tech guy checked SAP and cant find generated ABAP program of 
    ZCURCD is running anyway, although my local CURCD ABAP program is 
    created.
    3)Is it the 900086.R63 not complete? Is my function installation correct? I could view data
    on datastore, but just cant run job to extract. Another non-unidcode 900200.S08 group
    has larger file sizes. Should I try to install also this 900200.S08 files? Will it corrupt SAP
    and cause system errors?
    4)After that, I had tried to install the functions manually into ZAW0 
    one by one using cut and paste, however after that, I cant view the data view anymore with 
    error. Besides, I tried to run Check on the functions and they all returned 
    syntax errors, so I cant Activate any of them with SAP. Maybe dependency is missing??
    Then, I deleted the manually installed functions and can view data again, but just cant extract 
    data by job.
    5)Another side issue is all these SAP datastore creation and viewing is  
    through DI 11.5 old installation. The new Data Services X3.1 unable to 
    create datastore with database error, although the function module 
    installed is came from Data Services. Does anyone know the issue?
    Thank you very much to read it patiently. :P

    Hi,
    Thank you for the informative link. It did help a lot in solving the problem.
    (1) to (4) --- The Sap tech guy didnt install the function programs correctly, and he redo the transport again using CTS. Now I can see all the functions inside the function group ZAW0. While for the problem of cannot generate extracted file to SAP working directory for downloading, it is due to unix directory access permission setting. And also have to include the ftp username into SAPSYS user group as the help link suggested.
    (5) For this problem, I reinstalled again the DS with all required components like Server Manager. The network technical guy helped me with the first installation, and the installation was not complete. So now the issue is solved, I can create R/3 Datastore with DS.

  • How to check for a function module with its description and functionality

    Hi all,
    How to check for a function module,with its description and its functionality,in detail how can I know the purpose of a particular function module,how to search for a function module which suits my requirement .

    Hi,
    You can search a FM of your requirement by putting in the Key words and searching for a FM. Like * KEYWORD * and then pressing F4.
    Say for example you need to search something regarding converstion.
    Search for * CONVERT * and press F4.
    If there is something specfic like converting date to something you can give
    DATE * CONVERT *
    OR
    CONVERT * DATE *  and press F4.
    Once you narrow down your search you will have a Function module documentation inside the Function module. Please note that all the FMs willl not have documentation.
    Regards,
    Pramod

  • How to find the existing function module is used in another function module

    Hi all,
    I created a function module and the same one is called from another function module.
    When I tried to find where the  first function module is used  using  Where-used List , I am getting the message "function module not found in selected areas" .
    Please  guide me what is other method to find whether the function module is used in another one.
    Thanks,
    Vengal Rao.

    hi,
    Go to UTILITIES-> Update Navigation index.
    or go to fucntion group and Generate the Funtion group once.
    it will detect all fucntion modules under that function group.
    regards,
    Rama

  • Function module to give all partner functions for given customer

    Can anyone tell me function module name which gives all partner functions for a customer. For ex if we give customer number and sales area then it should give the list of all partner functions of this customer.
    I know 'CUSTOMER_PARTNERFS_GET' function module. But I want other than this.

    Hi,
    U can join VBAK and VBPA table and get the parrtners of the customer..
    Regards,
    Nagaraj

  • Function Module to retrive conversion exit function module names based on conversion routine

    Hi All,
    Can you people help me out in finding a function module, which takes conversion routine name as input and gives all the conversion exit function modules as output.
    Thanks and Regards,
    Shivaraj Naik.

    Curious, I looked for the way SAP do the job in SE11, and they also use the CONCATENATE option...
    From Include LSD11F01 Form OBJ_GOTO
    *       Objektspezifische Navigationsziele
    *      --> GOTOID   Kennung für Navigationsziele
    *      --> DDNAME   Dictonary-Name
    form obj_goto using  gotoid type gotoid
                         ddname.
      case gotoid.
        when 'CNVE'.   "Konvertierungsexit zu Domäne
          data: wb_request type ref to cl_wb_request.
          data: fb_name like tfdir-funcname
                            value 'CONVERSION_EXIT_'.
          concatenate fb_name ddname '*' into fb_name.
          condense fb_name.
    * Request für Infosystem erzeugen
          class cl_wb_infosystem definition load.
          call method cl_wb_infosystem=>create_request
            exporting
              p_object_type        = 'FF'
              p_object_name        = fb_name
              p_operation          = swbm_c_op_search
              p_suppress_selection = 'X'
              p_show_as_popup      = 'X'
            importing
              p_wb_request         = wb_request
            exceptions
              action_cancelled     = 1
              execute_in_batch     = 2
              error_occured        = 3.
    Regards,
    Raymond

  • Remote enabled function modules IN R/3

    hi,
    i posted this question before but i didnt get a convincing answer to move forward
    when data is sent to bw from r/3 there should be some remote enabled function modules which are  getting fired.
    so people told me to find fm for each data source in 'ROOSOURCE'  table.
    and to debug to get the function module IN RSA3.
    i got those function module but these r 'NORMAL FUNCTION MODULE'  but not
    'REMOTE ENABLED FUNCTION MODULES'
    IF REMOTE ENABLED FM'S ARE NOT GETTING TRIGGERED THEN HOW IS DATA GOING TO BW
    PLEASE SUGGEST ME I AM WAITING FOR LONG TIME FOR A GOOD ANSWER.

    OK,
    this is a big project.... You want to simulate a BW system.... I think don't think it is not possible but R/3 is a pair exchanging a lot of information and a lot of settings have to be done.... this seems to me very complex....
    This will depend on what kind of datasource you want to extract....
    - Master data: I would directly go the you SAP database and extract the info form the tables directly (we are actually doing that)
    - LO datasources would be a bit more complex since you'll have to initialize your datasource from a BW system.... Or figure out how this is working, meaning reverse engineering of the whole stuff! You could even think about using the exits for the business events, e.g. when an article doc is created, write the data in a flat file and/or write it directly to the DB of your DW....
    Also I would setup a BW system anyway; it is so easy then to manage all this data... You could then stick to load the data to the PSA and extract it very easily to your external DW. Even BW provide much more extraction capabilities once the data is stored there....
    They're a lot of solutions like always... the challenge is to choose the best one.
    hope this helps...
    Olivier.

  • Reg: Calling Function Module

    Hi to all,
    I have created a Function module, Which working fine and giving results which i expected and also i called that function module in programme in SE38, and giving correct results. BUT when i used in Transformation it giving ERROR. Routine not able to call that function module.It giving error as EXCEPTION IN SUBSTEP:RULES and PROCESS TERMINATED. In monitor screen besied this error message, There is a ikon, on cliking that ikon, it taking me to Statement CALL FUNCTION 'Function Module name'. Cursor is not going inside the Function module.
    It is Normal Function Module.
    Can anybody help in this Regard.
    Regards
    Mrk Reddy

    Hi,
    Were you able to solve this issue? I have exactly the same problem at the moment.
    Your feedback would be much appreciated.
    Regards,
    Edo

  • How to make a normal Function Module remote able function module

    Hi guys,
    i am a beginner in abap programming. I have made a programm in Se80 which shows all the nodes of the active hierarchies (5 stk.)
    in a ALV grid. Therefore i am getting the active hierarchies from table "rshiedir" and use the normal function module "RSSH_HIERARCHY_READ" to display the nodes of the hierarchie. The problem is the hierarchies do have a different techical name in the systems (development-acceptance-productive) but the descriptive nbame is the same in all systems. Because of the difference of the technical names I can use this programm in just one system. But the hierarchy content should be comparable and be displayed in all three systems. Therefore i would like to create a remoteable function module which covers the normal one. Can i do this and how can i create a remoteable function module and use it? 
    If not do you know any remotable functgion module which gives back all the nodes from an active hierarchy in table "RShiedir".
    Thanks and kind regards,
    Murat

    Hello,
    Simple, create a wrapper RFC (similar to 'RSSH_HIERARCHY_READ' ) & call the normal FM 'RSSH_HIERARCHY_READ' inside the wrapper.
    Something like this:
    FUNCTION z_rssh_hierarchy_read.
    *"*"Global Interface:
    *"  IMPORTING
    *"     VALUE(I_RSHIEDIRKEY) TYPE  RSHI_S_RSHIEDIRKEY OPTIONAL
    *"     VALUE(I_RSHIEDIRLOG) TYPE  RSHI_S_RSHIEDIRLOG OPTIONAL
    *"     VALUE(I_DATE) TYPE  RSHI_DATE DEFAULT SY-DATUM
    *"  EXPORTING
    *"     REFERENCE(E_RSHIEDIR) TYPE  RSHI_S_HIEDIR
    *"     REFERENCE(E_T_RSNODES) TYPE  RSHI_T_HIENODE
    *"     REFERENCE(E_TH_RSINTERVAL) TYPE  RSHI_TH_INTERVAL
    *"     REFERENCE(E_DUPLICATE_LEAFS) TYPE  RS_BOOL
    *"     REFERENCE(E_T_RSNODES_LNK) TYPE  RSHI_T_HIENODE
    *"  EXCEPTIONS
    *"      INVALID_HIERARCHY
    *"      NAME_ERROR
    *"      IOBJ_NOT_FOUND
    " Don't forget to add TYPE-POOLS rshi to the FuGr. TOP include
      CALL FUNCTION 'RSSH_HIERARCHY_READ'
        EXPORTING
          i_rshiedirkey     = i_rshiedirkey
          i_rshiedirlog     = i_rshiedirlog
          i_date            = i_date
        IMPORTING
          e_rshiedir        = e_rshiedir
          e_t_rsnodes       = e_t_rsnodes
          e_th_rsinterval   = e_th_rsinterval
          e_duplicate_leafs = e_duplicate_leafs
          e_t_rsnodes_lnk   = e_t_rsnodes_lnk
        EXCEPTIONS
          invalid_hierarchy = 1
          name_error        = 2
          iobj_not_found    = 3
          OTHERS            = 4.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Here Z_RSSH_HIERARCHY_READ is the wrapper RFC. Hope you get the point.
    BR,
    Suhas

  • Regarding the Remote Function Module

    hi,
            Can any body can provide the brief information regarding the Remote Function Module.
    1)How to create the remote function module
    2)how it differ from the normal function module
    3)any special features about this.
    Thanks in advance

    Hi
    RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
    and you will be passing an Import parameter DESTINATION to it.
    Other code and usage will be similar to any fun module;
    Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
    Refer this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm
    check out the following link it might help you
    http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf
    Function Modules;
    Check this matter.
    Function Modules are Global ABAP programs created by SAP for reusable purpose.they have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error occurs.
    You can create them from TCode SE37.
    Go through the following doc:
    Function modules are cross-program, reusable procedures that are organized into function groups, and whose functions are implemented between the statements FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the Function Builder.
    Function Module Interfaces
    The parameter interface of a function module is defined in the Function Builder. It includes the definition of interface parameters and the specification of exceptions that can be triggered by a function module. The Function Builder automatically generates comment lines below the FUNCTION statement in the source code of the function module, which represent the interface of the function module with the following syntax:
    Syntax
    ... [IMPORTING parameters]
    [EXPORTING parameters]
    [CHANGING parameters]
    [TABLES table_parameters]
    [{RAISING|EXCEPTIONS} exc1 exc2 ...]
    The syntax and semantics of IMPORTING, EXPORTING, CHANGING, RAISING, and EXCEPTIONS mainly correspond to the definition of method interfaces with [CLASS-]METHODS. The additional option of defining table parameters using TABLES is obsolete.
    Interface parameters
    The interface parameters are defined on the relevant tab pages in the Function Builder.
    IMPORTING parameters are input parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input parameter. The content of the actual parameter is passed to the input parameter when the call is made. The content of an input parameter for which 'pass by reference' is defined cannot be changed in the function module.
    EXPORTING parameters are output parameters. When the function module is called, a suitable actual parameter can be specified for every output parameter. The content of an output parameter that is defined for 'pass by value' is transferred to the actual parameter if the function module is completed without errors. An output parameter that is defined for pass by reference is not initialized when the function module is called.
    CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter.
    TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.
    Exceptions
    The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.
    The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.
    The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.
    Note
    For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.
    RFC is a technology which is used to access a functions (Modules) from
    the remote systems.
    If a function module is set as remote enabled which can be access from
    the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.
    A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".
    But Normal function modules can not accessd from the remote system.
    Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)
    Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.
    CALLING A FUNCTION MODULE:
    1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"
    --> Write the Corresponding FM name --> Hit Enter
    2)The appropriate import ,export Parameters will be displayed in ur editor
    3)Pass the Values Here.
    Also check these links.
    http://www.geocities.com/victorav15/sapr3/abapfun.html
    Check this link:
    http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
    Check this link:
    http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
    See the following links:
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • G_G_IDOC_REC_ZZINCOT function module not found in ECC 5.0

    i am getting the dump.
    the fuction module is not presend in ECC 5.0
    Runtime Errors         CALL_FUNCTION_NOT_FOUND                                                     
    Exceptn                CX_SY_DYN_CALL_ILLEGAL_FUNC                                                 
    Date and Time          04/05/2007 07:13:25                                                         
    ShrtText                                                                               
    Function module "G_G_IDOC_REC_ZZINCOT" not found.                                             
    What happened?                                                                               
    The function module "G_G_IDOC_REC_ZZINCOT" was called, but cannot be                          
        found in the Function Library.                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLGUIF" had to be terminated because one of the                   
        statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                         
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                      
        and make a note of the actions and input that caused the                                      
        error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer                      
         termination messages, especially those beyond their normal deletion                          
        date.                                                                               
    is especially useful if you want to keep a particular message.                                
    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_FUNC',                
         was neither                                                                               
    caught nor passed along using a RAISING clause, in the procedure                              
         "IDOC_INPUT_GLROLL" "(FUNCTION)"                                                             
    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 program "SAPLGUIF" contains a CALL FUNCTION statement. The name                           
        of the function module to be called is "G_G_IDOC_REC_ZZINCOT".                                                                               
    No function module exists with the name "G_G_IDOC_REC_ZZINCOT".                               
        All function modules are stored in the Function Library (SE37).                                                                               
    Possible reasons:                                                                               
    a) Wrong name specified. Particular attention should be paid                                  
           to upper/lower case and underscores ("_")                                                  
        b) Transport error                                                                               
    c) If an enqueue/dequeue module has been used, the lock object                                
           may not have been activated (ABAP Dictionary)                                              
           may not have been activated (ABAP Dictionary).                                             
    How to correct the error                                                                               
    Check the last transports to the R/3 System.                                                  
        Is the program "SAPLGUIF" currently being changed?                                            
        If an enqueue/dequeue module is involved, is the activation                                   
        of the lock object missing in the ABAP/4 Dictionary?                                                                               
    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_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC                                        
        "SAPLGUIF" or "LGUIFU05"                                                                      
        "IDOC_INPUT_GLROLL"                                                                               
    Function modules with names similar to "G_G_IDOC_REC_ZZINCOT":                                                                               
    G_G_IDOC_REC_COFIT                                                                               
    G_G_IDOC_REC_FILCT                                                                               
    G_G_IDOC_REC_ECMCT                                                                               
    G_G_IDOC_REC_GLPCT                                                                               
    G_G_IDOC_REC_GLT0                                                                               
    G_G_IDOC_REC_SECURE                                                                               
    G_POSTING_ZZINCOT                                                                               
    G_G_IDOC_SEND_COFIT                                                                               
    G_G_IDOC_SEND_ECMCT                                                                               
    G_G_IDOC_SEND_SECURE                                                                               
    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                           
         "IDOC_INPUT_GLROLL"                                                                               
    "(FUNCTION)", or declared in the procedure's RAISING clause.                                  
        To prevent the exception, note the following:                                                 
    System environment                                                                               
    SAP Release.............. "640"                                                                               
    Application server....... "d48ix100"                                                          
        Network address.......... "151.162.153.62"                                                    
        Operating system......... "AIX"                                                               
        Release.................. "5.3"                                                               
        Hardware type............ "00C65EFD4C00"                                                      
        Character length......... 8 Bits                                                              
        Pointer length........... 64 Bits                                                             
        Work process number...... 2                                                                   
        Short dump setting....... "full"                                                                               
    Database server.......... "d48ix100"                                                          
        Database type............ "ORACLE"                                                            
        Database name............ "D48"                                                               
        Database owner........... "SAPR3"                                                                               
    Character set............ "en_US.ISO8859-1"                                                                               
    SAP kernel............... "640"                                                               
        Created on............... "Nov 5 2006 20:46:58"                                               
        Created in............... "AIX 1 5 00538A4A4C00"                                              
        Database version......... "OCI_920 "                                                                               
    Patch level.............. "156"                                                               
        Patch text............... " "                                                                               
    Supported environment....                                                                     
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE                        
         10.2.0.."                                                                               
    SAP database version..... "640"                                                               
        Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory usage.............                                                                     
        Roll..................... 16128                                                               
        EM....................... 8379856                                                             
        Heap..................... 0                                                                   
        Page..................... 16384                                                               
        MM Used.................. 2530176                                                             
        MM Free.................. 1657232                                                             
        SAP Release.............. "640"                                                                               
    User and Transaction                                                                               
    Client.............. 010                                                                      
        User................ "OS0730"                                                                 
        Language key........ "E"                                                                      
        Transaction......... "YICUPLD "                                                               
        Program............. "SAPLGUIF"                                                               
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        The termination occurred in the ABAP program "SAPLGUIF" in "IDOC_INPUT_GLROLL".               
        The main program was "Y21091IRECON ".                                                                               
    The termination occurred in line 65 of the source code of the (Include)                       
         program "LGUIFU05"                                                                               
    of the source code of program "LGUIFU05" (when calling the editor 650).                       
        Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"                 
         occurred in the                                                                               
    procedure "IDOC_INPUT_GLROLL" "(FUNCTION)" but was not handled locally, not                   
         declared in the                                                                               
    RAISING clause of the procedure.                                                              
        The procedure is in the program "SAPLGUIF ". Its source code starts in line 5                 
        of the (Include) program "LGUIF$05 ".                                                         
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    35                                                                               
    36 *Prüfen, ob Customizing richtig eingestellt ist                                             
       37     CHECK EXIT IS INITIAL.                                                                  
       38     PERFORM CHECK_CUSTOMIZING USING IDOC_NUMBER.                                            
       39                                                                               
    40 *Für Einzelposten neue Belegnummern vergeben                                                
       41     CHECK EXIT IS INITIAL.                                                                  
       42     PERFORM NEW_DOCUMENT_NUMBER USING IDOC_NUMBER                                           
       43                                       IDOC_CONTRL-MESTYP.                                   
       44                                                                               
    45 *Füllen der Segmentdaten                                                                    
       46     CHECK EXIT IS INITIAL.                                                                  
       47     CLEAR IDOC_SEGMENT. REFRESH IDOC_SEGMENT.                                               
       48                                                                               
    49     LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_NUMBER.                                          
       50       IDOC_SEGMENT = IDOC_DATA.                                                             
       51       APPEND IDOC_SEGMENT.                                                                  
       52     ENDLOOP.                                                                               
    53                                                                               
    54 *Name des zu rufenden Funktionsbausteines ermitteln                                         
       55     ROL_FUNCNAME = 'G_G_IDOC_REC_$'.                                                        
       56     PERFORM BUILD_ROL_FUNCNAME USING IDOC_NUMBER ROL_FUNCNAME.                              
       57                                                                               
    58 *Funktionsbaustein zum Empfangen des IDOC's aufrufen                                        
       59 *Wenn Sender 4.0 System -> Nimm' TAB30, sonst altes TAB                                     
       60     IF NOT E1GLTTF-TAB30 IS INITIAL.                                                        
       61       L_TAB30 = E1GLTTF-TAB30.                                                              
       62     ELSE.                                                                               
    63       L_TAB30 = E1GLTTF-TAB.                                                                
       64     ENDIF.                                                                               
    >>>>>     CALL FUNCTION ROL_FUNCNAME                                                              
       66          EXPORTING                                                                          
       67               MESTYP             = IDOC_CONTRL-MESTYP                                       
       68               DOCNUM             = IDOC_NUMBER                                              
       69               TAB                = L_TAB30                                                  
       70          TABLES                                                                               
    71               IDOC_SEGMENT       = IDOC_SEGMENT                                             
       72               IDOC_STATUS        = IDOC_STATUS                                              
       73               RETURN_VARIABLES   = RETURN_VARIABLES.                                        
       74                                                                               
    75   ENDLOOP.                                                                               
    76                                                                               
    77 *Keine IDOC's empfangen                                                                     
       78   IF SY-SUBRC NE 0.                                                                         
       79     RAISE WF_ERROR_PROCESS.                                                                 
       80   ELSE.                                                                               
    81 *Prüfen, ob Fehler bei der Verarbeitung der IDOCs aufgetreten sind                          
       82     LOOP AT IDOC_STATUS WHERE MSGTY = 'A'                                                   
       83                            OR MSGTY = 'E'.                                                  
       84       EXIT.                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 0                                                                               
    SY-TABIX 2                                                                               
    SY-DBCNT 1                                                                               
    SY-FDPOS 0                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY                                                                           &

    I think that the FM is a customized one. Correct me if I am wrong. It is quite possible that certain FM's might have been missed out while the new system is built. Here I am assuming that the you are doing an upgrade.
    If whatever, I've mentioned above is correct, you can copy the FM and its other components from the old system into the new one, to rectify the error

  • Remote enabling a function module

    Hi all,
    I need to use function module WFMC_MESSAGE_SINGLE to allow printing with PDA. However it is not remote enabled.
    How can I make it remote-enabled? What are the possibilities?
    Thanks

    copy the  function module WFMC_MESSAGE_SINGLE  to a ZWFMC_MESSAGE_SINGLE  function module and keep the same function group and click copy icon.
    Now in the attributes of the new function module select the  Processing Type "Remote_Enabled Module"
    Save and activate.
    Reward Points if useful.

Maybe you are looking for

  • Double Quotes in MaxL Strings

    I am trying to pass in a calc script string from a Perl script to a MaxL script. The calc script needs double quotes around some of the member names (yes, I know I can create aliases with underscores to work around this, but I can't believe this isn'

  • IPod Shuffle not recognised in any way

    My 2GB iPod Shuffle began blinking green-orange-orange which, I gather, means that I have to reinstall the firmware. First when I plugged it in, iTunes told me that an iPod was recognised but not identified properly. I tried the iPod Reset Utility bu

  • How to embed assets (GUIs) from different files, which are sharing common assets (BGs, Buttons)?

    I'm working in a bigger game project with a lot of Popups and GUIs. We use [Embed ...] in the code, to be able to implement the user interfaces. At the moment we have all GUIs in only one FLA, as they are sharing a lot of assets. The problem is, when

  • Sql code for authorizing senior staff after data was inserted in the table

    Dear sirs/madams, Sub: I am using oracle9i/forms6i/reports6i and developing software for rural bank, I need sql/procedure/function code for authorizing senior staff after data was inserted in to the table by the junior staff. Thanks in advance for yo

  • Navigate to Web Page always opens a new window

    Hi, I am using action link "Navigate to Web Page" for column interaction. The source report is in a dashboard page and by clicking on this column should navigate to another dashboard page carrying some parameters. It works fine but everytime it opens