Login Module not found by ClassLoader

I tried to add my own LoginModule to the login modules stack, but i get the following exception from the classloader when it is supposed to be used:
Exception com.sap.engine.services.security.exceptions.BaseSecurityException: Cannot load a login module.
Then i get an info about the Class Loader, but it seems that my archive is not there.
i followed the steps from the document "JAAS Login Modules
For SAP WebAS JAVA 6.40", but i am not sure how/where to define the jar-archive.
What exactly has to be described under the config property "Security Provider->Properties->LoginModuleClassLoaders" ?
Any help would be very kind!
Marius

Hi,
I see that this is an old post but I just had the same problem and maybe it helps someone else who is facing the same problem too.
I also found the error in the trace file stating that my custom login module class could not be loaded and I realized that my JAR-File was not contained in the SDA file as it should after Creating the archive although I added a reference in the provider.xml file.
Everything was just as described under help.sap.com.
My custom class is in a package called de.test.... so I browsed to the general Tab of the provider.xml and changed the provider from sap.com to de.test
After exporting again the JAR was finally contained in the sda and after deployment to the j2ee and restart of the engine the class could finally be loaded!
Note that when changing the vendor to de.test the name of the library also changes to de.test~MyLoginModuleClass or whatever the Class is called. This name has to be registered in the Config Toll (Global Server Config > services > security > LoginModuleClassLoaders)
y
You can check for the exact name of your deployed library in the Visual Admin by choosing Server > Libraries > YourLibraryDisplayName or Server > Services > Class Loader Viewer > Libraries)
Hope this helps
Cheers
Marcel

Similar Messages

  • Custom login module - Not invoked...

    Hi All
    I have developed a custom login module and the necessary configuration steps in VA are performed. However, the custom login module is not called...
    1. Developed a Java DC as a Child DC in a Library DC.
    2. Added all the relevant jars needed as Used DC and Public Parts as required. Also updated the provider.xml with relevant references.
    3. Build and Deployed. (No errors found here..)
    4. In VA - Created a new Login Module.... updated the property LoginModuleClassLoaders to library:xyz where xyz is the name of the folder for deployed sda as found in cluster\j2ee\serverx\bin\ext...next updated the config tool for the same.... next modified the sap.com/irj*irj authentication as:
    Basic - Requisite
    CustomModule - Optional.
    Then performed server restart. Yet, login module not called. Any ideas as to where I am going wrong..?? (In my login module, just trying to retrieve the user name and change their attributes like lastname etc... )
    Thanks
    Deepak

    Issue solved....
    Had forgot to add the module to the ticket stack...

  • Why i get servlet exception/login servlet not found exception  with .ear ?

    I am able to deploy my war and after that generating the ear from that. both works fine in local system.
    But when i run (Jboss as service[Java Service Wrapper]) it takes war without any problem.But with ear file i am getting servlet not found exception.I can't understand where this problem is coming from.
    Even if i take my JSPWIki ear which is running well in production server, this also gives same error.
    One more thing, the files, what i am running well in local system i.e. war and ear working fine. (can't test in production server so testing in same kind of testing server) there also getting login servlet not found exception. Even in same location other files which are deployed are working fine.out of 4 at least one is working fine.
    I don't undersatnd where this whole problem is .
    Please guiide me where sholud i concentrate to solve this problem.
    thnaks
    Vijendra

    I took the source code including the dll files already added to the project from here:
    spazzarama/Direct3DHook
    The solution include two projects the one name Capture is class library type and the dll that make the exception is in this project.
    I tried now to use the program Dependency Walker on this dll file and it found error/s:
    This is the log:
    Error: At least one required implicit or forwarded dependency was not found.
    Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
    Error: Modules with different CPU types were found.
    Warning: At least one delay-load dependency module was not found.
    Screenshot:
    It happen only when using/detecting Direct3D 11 . So far only in Direct3D 11, When i use it with a game that run Direct3D 9 it's working fine.
    The question is how can i solve this dll problem ? Any site/place to download this dll from ?

  • "Module not found" in Apple Mail

    Hi all,
    Many times when I edit a new message in Apple Mail, images do not appear after I drag them to the new email. Instead, a sentence appears. My System is in Spanish language and I haven't had the chance to see it in English but it is something like "Module not found".
    This message, instead of attached images, appears randomly so it's very difficult for me to say why is this happening. It happens in some emails I receive so I have to ask them to send them over again. In some emails received with this problem, the images appear time after if I check them back again.
    I deleted and added again my email accounts, but this didn't help. I use MobileMe and Gmail.
    If someone in this forum can help me or has got a clue about this, is very frustrating as I'm a graphic designer and there are attached images in almost every email I send or receive.
    Thanks a lot!

    Hola Carola! 
    That's what I'm talking about! I work as a Graphic Designer and it's quite absurd how I can not appreciate the images my clients send me to show changes or reviews inside the email's body.. it's not just sending but reading the images the issue remains.
    You like me (as many) don´t have enought time to reset or re-install the entire operative system (where the Apple mail is packaged) to fix such a basic problem.
    Apple had closed other discussions like this one with no response.
    -La verdad no entiendo que exista este detalle tan básico para un ordenador hecho para el sector creativo-
    Estoy creando un hashtag en twitter #modulenotfound a ver si consigo algo por ahi.. Saludos desde Madrid

  • Error Function module " " not found in Smartforms

    Hi all,
    Please help me out….
    I created the form using the smartforms, check it and activated it. I can see the unique function module is assigned to the form. I wrote the ABAP program and use function module ‘SSF_FUNCTION_MODULE_NAME’and also define data types.
    when I called the function module fm_name for passing values and tables from program to smartform. This is working perfectly in development server but in production it giving error like Function module " " not found.
    Below I m pasting my code.
    *& Report  ZCASHJOURNAL                                                *
    REPORT  zcashjournal                            .
    TABLES: bseg.
    DATA: FM_NAME TYPE rs38l_fnam.
    DATA:BEGIN OF it_bseg OCCURS 0.
            INCLUDE STRUCTURE bseg.
    DATA:END OF it_bseg.
    DATA:BEGIN OF it_bseg1 OCCURS 0.
            INCLUDE STRUCTURE bseg.
    DATA:END OF it_bseg1.
    DATA: gv_amt_in_words TYPE spell,
          gv_word TYPE spell-word,
          gv_decword TYPE spell-decword.
    DATA:BEGIN OF gt_bkpf OCCURS 0.
            INCLUDE STRUCTURE bkpf.
    DATA:END OF gt_bkpf.
    DATA:bktxt TYPE bktxt.
    DATA:waers TYPE waers.
    DATA:belnr TYPE belnr_d.
    DATA:werks TYPE bukrs.
    DATA:desc  TYPE butxt.
    DATA:awkey TYPE awkey.
    DATA:docno TYPE matnr.
    DATA:cajo  TYPE awkey.
    DATA:desc1 TYPE butxt.
    DATA:dmbtr TYPE dmbtr.
    SELECTION-SCREEN BEGIN OF BLOCK b2.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT (15) FOR FIELD s_belnr.
    SELECTION-SCREEN POSITION 28 .
      PARAMETERS : s_belnr TYPE bseg-belnr .
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT (15) FOR FIELD s_werks.
        SELECTION-SCREEN POSITION 28 .
          PARAMETERS: s_werks TYPE werks.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN END OF BLOCK b2.
    SELECT * FROM bkpf
               INTO CORRESPONDING FIELDS OF TABLE gt_bkpf
              WHERE belnr LIKE s_belnr
              AND   bukrs LIKE s_werks.
    IF NOT gt_bkpf[] IS INITIAL.
      SELECT * FROM bseg
          INTO CORRESPONDING FIELDS OF TABLE it_bseg
          FOR ALL ENTRIES IN gt_bkpf
          WHERE bukrs EQ gt_bkpf-bukrs
          AND   belnr EQ gt_bkpf-belnr
          AND   shkzg EQ 'S'.
    ENDIF.
    LOOP AT gt_bkpf.
      bktxt = gt_bkpf-bktxt.
      waers = gt_bkpf-waers.
      belnr = gt_bkpf-belnr.
      werks = gt_bkpf-bukrs.
      awkey = gt_bkpf-awkey.
      docno = awkey+0(10).
      cajo = awkey+10(4).
    ENDLOOP.
    LOOP AT it_bseg.
      dmbtr = it_bseg-dmbtr.
    ENDLOOP.
    IF s_werks EQ '65'.
      desc = 'JCBML - Heavy Equipments'.
    ENDIF.
    IF cajo EQ '0001'.
      desc1 = 'PETTY CASH PLANT II'.
    ENDIF.
    CALL FUNCTION 'SPELL_AMOUNT'
      EXPORTING
        amount    = dmbtr
        currency  = waers
        filler    = space
        language  = sy-langu
      IMPORTING
        in_words  = gv_amt_in_words
      EXCEPTIONS
        not_found = 1
        too_large = 2
        OTHERS    = 3.
    IF sy-subrc EQ 0.
      MOVE : gv_amt_in_words-word TO gv_word,
             gv_amt_in_words-decword TO gv_decword.
    ENDIF.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        formname                 = 'ZCASHRECPT'
    IMPORTING
       FM_NAME                  = FM_NAME
    EXCEPTIONS
       NO_FORM                  = 1
       NO_FUNCTION_MODULE       = 2
       OTHERS                   = 3
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    *CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
            EXPORTING  formname           = 'ZCASHRECPT'
                    variant            = ' '
                    direct_call        = ' '
            IMPORTING  fm_name            = lf_fm_name
            EXCEPTIONS no_form            = 1
                       no_function_module = 2.
    *v_vbeln = S_VBELN-low.
    CALL FUNCTION FM_NAME
      EXPORTING
        bktxt            = bktxt
        waers            = waers
        belnr            = belnr
        werks            = werks
        desc             = desc
        docno            = docno
        cajo             = cajo
        desc1            = desc1
        dmbtr            = dmbtr
        gv_word          = gv_word
      TABLES
        T_ZDEB           = it_bseg
      EXCEPTIONS
        formatting_error = 1
        internal_error   = 2
        send_error       = 3
        user_canceled    = 4
        OTHERS           = 5.
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

    Hi Rakesh,
    Check two things
    1. Program tranpsorted to production without any error in request log.
    2. Smartform tranpsorted to production without any error in request log and without renaming / misspelling it.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
    formname = 'ZCASHRECPT'
    IMPORTING
    FM_NAME = FM_NAME
    EXCEPTIONS
    NO_FORM = 1
    NO_FUNCTION_MODULE = 2
    OTHERS = 3
    IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Also try to uncomment the Message id part and it will show some meaningful message.
    And to check whether actaually fucntion module is generated or not goto smartforms ->Smartform name -> Display -> Environment->Fucntion module name . if this is blank try to retransport smartform.
    Hope that helps.
    Regards
    Kapadia
    ***Assigning points is the way to say thanks in SDN.***

  • SMQ2 SYSFAIL - Function Module not found

    Hi All,
    When i am trying to push data to cdb i got sysfail - Function module not found error in the smq2. But data inserted in the cdb, the probelm we found was the data object having the dependency cause this error.
    The data was there in the cdb, but no distribution entries found.
    Please help me to resolve the same.
    Regards,
    Ramkumar

    Hi,
    Clear the queue first (delete it), then implement the NOTE 1552255 - 'Parallel load problem for partial association shadow'. Run the report mentioned in the NOTE and  do a delta generation.
    Then on doin a delta load the queues should run successfully.
    regards,
    Anil

  • Login keychain not found

    I tried to do the keychain first aid and it came up with the error of login keychain not found. I googled it and nothing was helpful. Should I take my mac in?

    At some point, you reset your keychain to default in Keychain Access. That caused your login keychain to be renamed.
    Back up all data.
    In Keychain Access, delete the login keychain from the keychain list. Choose Delete References when prompted, not Delete References & Files.
    In the Finder, select Go ▹ Go to Folder from the menu bar, copy the text on the line below into the box that opens, and press return:
    ~/Library/Keychains
    A folder will open. Rename the file "login.keychain" in that folder to something like "login-old.keychain". Rename the file "login-renamed.keychain" to "login.keychain".
    Back in Keychain Access, select File ▹ Add Keychain from the menu bar. Add back the file now named "login.keychain". If any of your needed keychain items are missing from it, also add back the file you named "login-old.keychain". I suggest you transfer any needed items from that keychain to the login keychain, then delete it. The transfers are made by drag-and-drop in Keychain Access. You'll need to enter your password for each item transferred.

  • Function modules not found....

    Hello,
    I found the following errors in my SDCCN logs, I have googled and also searched in SAP market place and even in SDN but no help. Also the EWA shows the same in Missing Function Module column.Please help in this regards.
    Thanks and Regards,
    Yoganand.V
    Errors:
    1) EWA_MAIN_BUSINESS_HOURS : no matching interface found
        function module not found
        EWA_MAIN_BUSINESS_HOURS : funcname /SDF/MAIN_BUSINESS_HOURS , module 000156
    2) READ_RFC_LIST : # of imp params in funcmod < # of imp params in mod 000152
        READ_RFC_LIST : inconsistency in # of imp params found for mod 000152
        READ_RFC_LIST : non-default imp param IF_ANONYMIZE is not passed to mod 000152
        READ_STAMP : no matching interface found
        function module not found
        READ_STAMP : funcname /BDL/READ_STAMP , module 000153

    Hi,
    EWA_MAIN_BUSINESS_HOURS
    READ_RFC_LIST
    READ_STAMP
    are three new function modules which will be supplied with the next version of ST-PI. The next version of ST-PI is currently scheduled to be released in mid December. For the moment, the only thing to do is to ignore those errors until the next ST-PI becomes available.
    best regards,
    -David.

  • I cannot get it. 10 times already to receive  new passwords today. Adove Download Assistant says  "Unable to invoke CFC - The method login was not found in component tdrc.tdrcfacade.

    I cannot get it. 10 times already to receive  new passwords today. Adove Download Assistant says  "Unable to invoke CFC - The method login was not found in component tdrc.tdrcfacade.
    What can I do? My problem was started from installing Adobe Reader. It says "Done OK" but never installed.
    Elena
    e. [email protected]

    Try using the offline installer from http://get.adobe.com/reader/enterprise/

  • Function Module not found in SRM 7.0 -CRM_ORDERADM_H_SELECT_BUF_M_DB

    Hi Masa/Muthu/Viru ,
    We  have upgraded from SRM 3.0 to SRM 7.0.
    we have copied the ZUS2000113 from Business object BUS2000113 for Contract workflow.
    In SRM 7.0 the above   Function Module not found in SRM 7.0 -CRM_ORDERADM_H_SELECT_BUF_M_DB.
    Can you telll which is the replacement of this FM
    Regards
    G.Ganesh Kumar

    Hello,
    What is the aim of FM name you gave us ?
    What is its function group ?
    With those data, it could be easier to find an existing one with same goal in SRM 7.0 release .
    Regards.
    Laurent.

  • 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

  • Sample Login Module Not working

    I have configured the sample login module shipped with identity server 6.0 for understanding the configuration of a custome login module.
    As per the instruction when i try to run the example i get an Authentication faliure i have given the following url "http://<domain-name>:58080/amserver/UI/Login?module=LoginModuleSample&org=<my org name>"
    Could anyone plz tell me y this error has occurred and if not then suggest me a way to return back to a state where i was before working with this example as now i cannot open the amconsole as well.
    plz help as fast as possible
    kirtan

    use commandline to remove and then add (again) amauth service. you should be able to log into the console again.... with your amadmin id and password
    for getting the sample auth module to work.. please read the docs carefully, it has a very clear step by step explanation on how to do it...

  • CDMC - Function Modules not Found

    Hi,
    Initially the Solution manager ST level is 23 and CDMC clearning analysis worked will with ERP satellite system.
    Later, Solution manager has upgraded with 24 and not able to actiavate the statistics and unable to perform clearning analysis.
    Below are 2 known errors(there could be more),
    Function Modules "CNV_CDMC_CC_GET_COMPS_OF_SYS" and "CNVCDMC_OBJECT_EXISTENCE_CHECK" not found.
    Did any face this similar issues ?
    Do we need to consider any component upgrade at Satellite systems  with respect these upgrades in solution manager ?
    Note: 3 of components are upgraded in solution manager which are ST , ST-A/PI and ST-SER...
    Regards,

    Hello,
    If you are on ST-PI SP03 this note is needed in all the participating systems of your CDMC project
    1509340 - Collective Note with all corrections for CDMC (ST-PI SP03)
    Also pleae review SAP Note 1348772 -  CDMC Corrections - Composite SAP NotePlease look under Solution for Support Package 03 relevant Notes:
    This will ensure that your system works without errors!
    Regards,
    Paul

  • Error "Function module  not found."

    Hi,
    I am calling RFC_GET_MATERIAL_DATA but I got this error "Function module "RFC_GET_MATERIAL_DATA" not found". What does it mean? How I can solve this error?
    Thank you in advance,
    Sunny

    Well I think it simply means that the Function Module does not exist in the system where it needs to get executed.
    First check if you are calling this FM remotely ( with a DESTINATION specification ). Then ensure that the FM exist in the DEST system (SE37).
    if you are not calling it remotely, then check if the FM exist in your local system.Just check in SE37.
    Reason it might not be available in the system is because of the version , or say product type ( R/3, CRM, EBP, BW... ).
    Thanks,
    Ram

  • Connection error to SAP InfoSets/Queries 'Function module not found'

    I have crystal reports 2011 and I would like to connect to our SAP system (ECC6.0).  I am able to connect partially but when I drill down into where I guess crystal is trying to pull a list of queries or infosets I get errors.
    For infosets i get 'Function module "/CRYSTAL/GET_FUNCAREA_CATALOG" not found.'
    For queries i get 'Function module "/CRYSTAL/GET_QUERY_CATALOG" not found.'
    What changes need to be performed to our SAP system to get these functions added?
    Thanks in advance.

    Hi Joshua,
    I did some checking so I changed my original reply. Those drivers are installed so nothing extra needed. I'm not completely sure how all of the Classic SAP data sources work but the only thing different is BW Query was removed in favor of MDX.
    Also, the Transports are in a download package and must be installed onto the BW system. I'm checking what that means and where they are located.
    The package for the BW server is located here:
    <folder where I unzipped>\DATA_UNITS\CrystalReports\Collaterals\Add-Ons\SAP\Transports
    Thanks again and sorry for the confusion...
    Don
    Edited by: Don Williams on Jul 11, 2011 10:59 AM

Maybe you are looking for