LOAD_PROGRAM_NOT_FOUND RSSTAT10

Dears,
after we upgrade our system to netweaver 7.0, we receive the following dumps in the systme:
LOAD_PROGRAM_NOT_FOUND
Program "RSSTAT10" not found
Since neighter the marketplace or SDN seem to have a solution, can someone help me out on this one ?
kind regards
Davy

Hi Davey,
RSSTAT10 does not exist in version 7. It was decomissioned after 640
A lot of the statistics collection has changed in version 7 significantly.... Have a look at note 1006116 and the related notes at the bottom of the note.
In SE38 look for SWNC* programs that may suit as replacements

Similar Messages

  • Dump while running a query-LOAD_PROGRAM_NOT_FOUND

    Hi,
    I got following dump when executing a query.
    How do we fix it.?
    Runtime Errors         LOAD_PROGRAM_NOT_FOUND
    Date and Time          01/09/2008 09:54:11
    Short text
         Program "AQZZZ_SD_CUST===Z_SD_CUST_QRY= " not found.
    What happened?
         There are several possibilities:
         Error in the ABAP Application Program
         The current ABAP program "????????????????????????????????????????" had to be
          terminated because it has
         come across a statement that unfortunately cannot be executed.
         or
         Error in the SAP kernel.
         The current ABAP "????????????????????????????????????????" program had to be
          terminated because the
         ABAP processor detected an internal system error.

    if you start that query for a second time, does the problem persist?
    anyway, go to tx. SQ01 -> Query -> Generate coding and the program will be reloaded.

  • Report in Transaction CJE0 - LOAD_PROGRAM_NOT_FOUND

    Hi ABAP Gurus,
    After double clicking a project report in Transaction CJE0, Dump LOAD_PROGRAM_NOT_FOUND occurs.  Can you kindly provide advise on how to check this?  Thank you.
    Best regards.
    Brando

    This is the error: program "GP3U00IL5OJAWE41MAMXUFGYEXR" does not exist in the library.
    I debugged this and the above program is being submitted in FM RKD_REPORT_START_ONLINE.  However, the program does not exist.  Hence, the dump occured.
    Do you happen to know how to verify if it is the correct program to be called? and how to add/generate the program if it;s the correct one? 
    Thank you

  • Runtime error LOAD_PROGRAM_NOT_FOUND for ARE document.

    Hi All,
    when I am creating or posting ARE document thru tcode J1IA101 & J1IA301 ,I am clicking on Printing check box & when I am going to save it .It is giving me error printing parameter is not set &
    after pressing enter it is giving runtime error, which is as follows:
    Runtime Errors         LOAD_PROGRAM_NOT_FOUND
    Exception              CX_SY_PROGRAM_NOT_FOUND
    What happened?
        There are several possibilities:
        Error in the ABAP Application Program
        The current ABAP program "SAPLJ1IEX" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        or
        Error in the SAP kernel.
        The current ABAP "SAPLJ1IEX" program had to be terminated because the
        ABAP processor detected an internal system error.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
         caught in
        procedure "J_1IEX_PRINT_ARE" "(FUNCTION)", nor was it propagated by a RAISIN
         clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        On account of a branch in the program
        (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
        or a transaction call, another ABAP/4 program
        is to be loaded, namely " ".
        However, program " " does not exist in the library.
        Possible reasons:
        a) Wrong program name specified in an external PERFORM or
           SUBMIT or, when defining a new transaction, a new
           dialog module or a new function module.
        b) Transport error
    Thanks,
    C Singh,

    hi all,
    please change the access sequence from J1ID to J1IB and include program for printing ARE-3 in program 2 of access sequence J1IB.
    regards,
    C Singh.

  • LOAD_PROGRAM_NOT_FOUND

    Hi, In My XI system I get every hour message below (DDIC user , 000 Client)
    I search sap notes but did not find proper note.
    Is there anyone to help me?
    Thanks
    Runtime Error          <b>LOAD_PROGRAM_NOT_FOUND</b>
    Date and Time          06.12.2007 09:00:35
    |ShrtText                                                                               
    |    Program <b>"SWNCCOLL"</b> not found.                                                                
    |<b>What happened?</b>                                                                               
    |    There are several possible reasons for the error:                                            
    |                                                                               
    |    Error in ABAP application program.                                                           
    |                                                                               
    |    The current ABAP program "RSCOLL00" had to be terminated because one of the                  
    |    statements could not be executed.                                                            
    |                                                                               
    |    This is probably due to an error in the ABAP program.                                        
    |    or                                                                               
    |    The current ABAP program had to be terminated because the                                    
    |    ABAP processor detected an internal system error.                                            
    |    The current ABAP program "RSCOLL00" had to be terminated because the ABAP                    
    |    processor discovered an invalid system state.                                                
    |<b>What can you do?</b>                                                                               
    |    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.                               
    |<b>Error analysis</b>                                                                               
    |    On account of a branch in the program                                                        
    |    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)                                             
    |    or a transaction call, another ABAP/4 program                                                
    |    is to be loaded, namely "SWNCCOLL".                                                          
    |                                                                               
    |    However, program "SWNCCOLL" does not exist in the library.                                   
    |                                                                               
    |    Possible reasons:                                                                            
    |    a) Wrong program name specified in an external PERFORM or                                    
    |       SUBMIT or, when defining a new transaction, a new                                         
    |       dialog module or a new function module.                                                   
    |    b) Transport error                                                                           
    |    b) Transport error                                                                           
    |How to correct the error                                                                         
    |    Check the last transports to the R/3 System.                                                 
    |                                                                               
    |    Are changes currently being made to the program "RSCOLL00"?                                  
    |                                                                               
    |    Has the correct program been entered in table TSTC for Transaction " "?                      
    |    -                                                                               
    |                                                                               
    |                                                                               
    |    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:                                                           
    |                                                                               
    |    -
    |    "LOAD_PROGRAM_NOT_FOUND" C                                                                   
    |    "RSCOLL00" or "RSCOLL00"                                                                     
    |    "LOOP_AT_SYSTEMS_AND_REPORTS"                                                                
    |    -
    |    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.                                              
    |System environment                                                                               
    |    SAP Release.............. "640"                                                              
    |                                                                               
    |    Application server....... "brckxiprd"                                                        
    |    Network address.......... "10.4.5.133"                                                       
    |    Operating system......... "Windows NT"                                                       
    |    Release.................. "5.2"                                                              
    |    Hardware type............ "4x Intel 801586"                                                  
    |    Character length......... 16 Bits                                                            
    |    Pointer length........... 32 Bits                                                            
    |    Work process number...... 34                                                                 
    |    Short dump setting....... "full"                                                             
    |                                                                               
    |    Database server.......... "BRCKXIAPP"                                                        
    |    Database type............ "ORACLE"                                                           
    |    Database name............ "BXP"                                                              
    |    Database owner........... "SAPBXP"                                                           
    |                                                                               
    |    Character set............ "C"                                                                
    |                                                                               
    |    SAP kernel............... "640"                                                              
    |    Created on............... "Jul 4 2005 23:49:14"                                              
    |    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"                     
    |    Database version......... "OCI_920_SHARE "                                                   
    |                                                                               
    |    Patch level.............. "80"                                                               
    |    Patch text............... " "                                                                
    |                                                                               
    |    Supported environment....                                                                    
    |    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE                        
    |     10.1.0.."                                                                               
    |    SAP database version..... "640"                                                              
    |    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"                   
    |                                                                               
    |    Memory usage.............                                                                    
    |    Roll..................... 8176                                                               
    |    EM....................... 5226160                                                            
    |    Heap..................... 0                                                                  
    |    Page..................... 24576                                                              
    |    MM Used.................. 957264                                                             
    |    MM Free.................. 86568                                                              
    |    SAP Release.............. "640"                                                              
    |                                                                               
    |User and Transaction                                                                             
    |    Client.............. 000                                                                     
    |    User................ "DDIC"                                                                  
    |    Language key........ "E"                                                                     
    |    Transaction......... " "                                                                     
    |    Program............. "RSCOLL00"                                                              
    |    Screen.............. "SAPMSSY0 1000"                                                         
    |    Screen line......... 6                                                                       
    |Information on where terminated                                                                  
    |    The termination occurred in the ABAP program "RSCOLL00" in                                   
    |     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                              
    |    The main program was "RSCOLL00 ".                                                            
    |                                                                               
    |    The termination occurred in line 534 of the source code of the (Include)                     
    |     program "RSCOLL00"                                                                          
    |    of the source code of program "RSCOLL00" (when calling the editor 5340).                     
    |    The program "RSCOLL00" was started as a background job.                                      
    |                                                                               
    |    Job name........ "SAP_COLLECTOR_FOR_PERFMONITOR"                                             
    |    Job initiator... "DDIC"                                                                      
    |    Job number...... 08003401                                                                    
    |Source Code Extract                                                                               
    |Line |SourceCde                                                                               
    |  504|    LOOP AT itcoll.        " start of loop 2: reports                                      
    |  505|      skip_flg = 'X'.      " disable execution of report                                   
    |  506|      CASE itcoll-sytyp.                                                                   
    |  507|        WHEN 'S'.                                                                          
    |  508|          IF sys_tabl-system_mark = 'X'.                                                   
    |  509|            CLEAR skip_flg.  " enable execution of report                                  
    |  510|          ENDIF.                                                                           
    |  511|        WHEN 'A'.                                                                          
    |  512|          IF sys_tabl-appsrv_mark = 'X'.                                                   
    |  513|            CLEAR skip_flg.  " enable execution of report                                  
    |  514|          ENDIF.                                                                           
    |  515|        WHEN 'H'.                                                                          
    |  516|          IF sys_tabl-host_mark = 'X'.                                                     
    |  517|            CLEAR skip_flg.  " enable execution of report                                  
    |  518|          ENDIF.                                                                           
    |  519|        WHEN '%'.                  "Explicitly                                             
    |  520|          IF sys_tabl-name = itcoll-altsy OR sys_tabl-host = itcoll-altsy.                 
    |  521|            CLEAR skip_flg.                                                                
    |  522|          ENDIF.                                                                           
    |  523|      ENDCASE.                                                                             
    524
    |  525|*     Execute this report?                                                                 
    |  526|      IF skip_flg IS INITIAL.                                                              
    |  527|*       Yes, execute report ITCOLL-RNAME.                                                  
    |  528|*       All 'S' reports are executed locally; don't perform a RFC (itcoll-sytyp = 'S').    
    |  529|*       'A' and 'H' reports for the local application server are also                      
    |  530|*       executed by SUBMIT (sys_tabl-system_mark = 'X').                                   
    |  531|        IF itcoll-sytyp = 'S' or sys_tabl-system_mark = 'X'.                               
    |  532|          DO itcoll-renum TIMES.                                                           
    |  533|            SUBMIT (itcoll-rname) AND RETURN.                                              
    |>>>>>|            rinfo-host    = sy-host.                                                       
    |  535|            rinfo-rname   = itcoll-rname.                                                  
    |  536|            rinfo-rpara   = space.                                                         
    |  537|            rinfo-datum   = sy-datum.                                                      
    |  538|            rinfo-uzeit   = sy-uzeit.                                                      
    |  539|            rinfo-ltext   = space.                                                         
    |  540|*           write log entry                                                                
    |  541|            PERFORM proto_fill USING sys_tabl-name                                         
    |  542|                                     sys_tabl-host                                         
    |  543|                                     itcoll-rname                                          
    |  544|                                     sys_tabl-error.                                       
    |  545|          ENDDO.                                                                           
    |  546|        ELSE.                                                                               
    |  547|*         'A' and 'H' reports may have to be executed remotely.                            
    |  548|          DO itcoll-renum TIMES.      " start of loop 3: trials                            
    |  549|            sys_tabl-error = 0.                                                            
    |  550|            CLEAR mess.                                                                    
    |  551|            MODIFY sys_tabl.                                                               
    |  552|            CALL FUNCTION 'RSCOLL10' DESTINATION sys_tabl-name                             
    |  553|              EXPORTING                                                                    

    please visit
    How to handle form call error?
    Calling RPTQTA00 from a Z program
    Passing selection-options to standard PROG

  • Is there any alternative program for RSSTAT10 in ECC6.0 system

    Dear ABAPers,
    Issue scenario:
    We are trying to create a report program in the ECC system to provide the details of the server workload. This report is a copy of the program RSSTAT10 which is working fine in other systems(3.1,4.7). The report works fine in those systems. But when we try to copy the same on ECC,we get a dump " CALL_FUNCTION_CONFLICT_TYPE ".
    The Reason for the dump :
    1.The reason is the mismatch of the field length in the import export parameters of the FM.
    2.There are a few includes and FModules that do not exist in the ECC system, but are available in the other systems. For eg. RSSTAT10 is not available.
    Our question is :
    Since RSSTAT10 is unavailable in the ECC is there an alternate program that can be used in order to generate the report that provides the details of the server workload in the ECC system?
    Regards,
    Prathap

    Check
    Program:- RSSTAT15 in ECC 6.0
    Edited by: Bala Krishna on Aug 14, 2008 12:44 PM

  • SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed  with abap dump LOAD_PROGRAM_NOT_FOUND

    Dear Experts,
    Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed  with abap dump LOAD_PROGRAM_NOT_FOUND.
    As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
    Finished Job log
    Job started
    Step 001 started (program RSCOLL00, variant , user ID Bharath)
    Clean_Plan:Cleanup of DB13 Plannings
    Clean_Plan:started by RSDBPREV                       on server
    Clean_Plan:Cleaning up jobs of system DEV
    Clean_Plan:finished
    Job finished
    Failed Job Log
    Job started
    Step 001 started (program RSCOLL00, variant , user ID Bharath)
    Internal session terminated with a runtime error (see ST22).
    Kindly suggest on this..
    Thanks,
    Bharath.

    Dear Divyanshu,
    Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
    |Short text                                                                                        |
    |    Program "RSORA811" not found.                                                                 |
    |What happened?                                                                                    |
    |    There are several possibilities:                                                              |
    |                                                                                                  |
    |    Error in the ABAP Application Program                                                         |
    |                                                                                                  |
    |    The current ABAP program "RSCOLL00" had to be terminated because it has                       |
    |    come across a statement that unfortunately cannot be executed.                                |
    |    or                                                                                            |
    |    Error in the SAP kernel.                                                                      |
    |                                                                                                  |
    |    The current ABAP "RSCOLL00" program had to be terminated because the                          |
    |    ABAP processor detected an internal system error.                                             |
    |What can you do?                                                                                  |
    |    Note down which actions and inputs caused the error.                                          |
    |                                                                                                  |
    |                                                                                                  |
    |    To process the problem further, contact you SAP system                                        |
    |    administrator.                                                                                |
    |                                                                                                  |
    |    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
    |    at and manage termination messages, and you can also                                          |
    |    keep them for a long time.                                                                    |
    |Error analysis                                                                                    |
    |    On account of a branch in the program                                                         |
    |    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)                                              |
    |    or a transaction call, another ABAP/4 program                                                 |
    |    is to be loaded, namely "RSORA811".                                                           |
    |                                                                                                  |
    |    However, program "RSORA811" does not exist in the library.                                    |
    |                                                                                                  |
    |    Possible reasons:                                                                             |
    |    a) Wrong program name specified in an external PERFORM or                                     |
    |       SUBMIT or, when defining a new transaction, a new                                          |
    |       dialog module or a new function module.                                                    |
    |    b) Transport error                                                                            |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "RSCOLL00" - in                                      |
    |     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                               |
    |    The main program was "RSCOLL00 ".                                                             |
    |                                                                                                  |
    |    In the source code you have the termination point in line 535                                 |
    |    of the (Include) program "RSCOLL00".                                                          |
    |    The program "RSCOLL00" was started as a background job.                                       |
    |    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
    |    Job Initiator.. " bharath"                                                                       |
    |    Job Number..... 18243400
    Kindly check and suggest..
    Thanks,
    Bharath.

  • PBA7 runtime error LOAD_PROGRAM_NOT_FOUND

    i am trying transfer applicant to employee by using PBA7 but when transfer infotype 0021 family there's error load program not found and with dump :
    ABAP runtime errors    LOAD_PROGRAM_NOT_FOUND
           Occurred on     21.04.2014 at 11:52:27
    Program "MP031800 " not found.
    What happened?
    There are various possibilities:
    program library.
    The current ABAP/4 program "????????????????????????????????????????" had to be
    terminated because
    one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 program.
    or
    Error in the SAP Basis system
    ABAP/4 processor detected an internal system error.
    The current ABAP program "????????????????????????????????????????" had to be
    terminated because the ABAP
    processor discovered an invalid system state.
    MP031800 is SAP standard program for indonesian family infotype, should i create MP031800 module pool ?
    what should i do ?

    Dear Dio Dic
    I suspect that the error might be from the Basis system as it shows in the dump too
    Error in the SAP Basis system
    Kindly check this Note & links: 993499
    LOAD_PROGRAM_NOT_FOUND
    load program not found
    Hope this serves u in some sort of solution.
    Cheers
    Pradyp

  • Runtime Errors -  LOAD_PROGRAM_NOT_FOUND

    Hi ,
    we have scheduled delta job for the DO once in a day. After  deleted this job, everyday getting dump 'LOAD_PROGRAM_NOT_FOUND' in st22 ,Short Text:
    getting dump LOAD_PROGRAM_NOT_FOUND in st22.
    Information on where terminated
        Termination occurred in the ABAP program "RSBTCRTE" - in "START-OF-SELECTION".
        The main program was "RSBTCRTE ".
        In the source code you have the termination point in line 492
        of the (Include) program "RSBTCRTE".
        The program "RSBTCRTE" was started as a background job.
        Job Name....... "Sliding Window-Date"
        Job Initiator.. "PRODR4"
        Job Number..... "0000542F".
    What could be reason?
    Regards,
    Kanagaraj.

    Hi Kanagaraj,
    Basically, when you are deleting the job, you should delete the job in tcode SM37 with the status 'Released'. The job with status Released is responsible for spawning new job based on the frequency. Unless this is deleted, new will be created based on the defined frequency.
    I guess in your case, this job is not deleted in SM37 and thats the reason new job is getting creted everyday and trying to execute a report which is also deleted.
    If you are using sdoe_bg_job_monitor tcode to schedule/delete a job, you should not have this issue.
    Regards,
    Vinodh

  • Dump 'LOAD_PROGRAM_NOT_FOUND' while using QM02 and ZXqm02

    Dear All,
    We are facing dump LOAD_PROGRAM_NOT_FOUND at the time of QM02 and One Z transaction ZXQM02.
    Could you please tell me what should be the reason or what should be the remedy?
    Regards,
    AMAR

    There can be various reasons for this error :
    1. You have change dthe standard program for QM02
    2. Due to wrong customizing
    3. Check the dump and ther eyou can find the root cause of this error e.g the Z txn uses a program which is generated during runtime and this program is not available .
    Edited by: Sandeep Kumar on Sep 24, 2010 1:34 PM

  • Numerious LOAD_PROGRAM_NOT_FOUND dumps

    Hello Gurus,
    I'm getting like 30 short dumps on production daily:
    LOAD_PROGRAM_NOT_FOUND
    Program "GP3T9VZ87YU75ZSS0SO621KH46Q" not found.
    On account of a branch in the program (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)or a transaction call, another ABAP/4 program is to be loaded, namely "GP3T9VZ87YU75ZSS0SO621KH46Q". However, program "GP3T9VZ87YU75ZSS0SO621KH46Q" does not exist in the library. Possible reasons:
    a) Wrong program name specified in an external PERFORM or SUBMIT or, when defining a new transaction, a new dialog module or a new function module.
    |
    b) Transport error
    SAP kernel....... 700
    Patch level. 75
    Transaction......... "START_REPORT "
    Program............. "SAPLKYP4"Screen.............. "SAPLSRT2 0100"Screen line......... 7
    Here is the trace:
    A ABAP Program ZTDC_INT_OB_LOAD_TENDER_NAST
    A Source ZTDC_INT_OB_LOAD_TENDER_NAST
    Line 63.
    A Error Code LOAD_PROGRAM_NOT_FOUND.
    A Module $Id: //bas/700_REL/src/krn/runt/absubmit.c#3 $ SAP.
    A Function ab_submit Line 260.
    A ** RABAX: level LEV_RX_STDERR completed.
    A ** RABAX: level LEV_RX_RFC_ERROR entered.
    A ** RABAX: level LEV_RX_RFC_ERROR completed.
    A ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A ** RABAX: level LEV_RX_IMC_ERROR entered.
    A ** RABAX: level LEV_RX_IMC_ERROR completed.
    A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    A ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A ** RABAX: level LEV_RX_END entered.
    A ** RABAX: level LEV_RX_END completed.
    A ** RABAX: end no http/smtp
    A ** RABAX: end RX_BTCHLOG|RX_VBLOG
    A Program ZMHRSNAST00 not found..
    A
    M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c
    13155]
    M PfAddStatDura: overflow (4294613573<4294790703,1183), take max uint for STAT_COMMIT
    B
    B Thu May 15 08:16:53 2008
    B Disconnected from connection con_da={+DBO+0030,8000780,1}
    I questioned everyone, noone performed any upgrades or transports to the system... . Could you please translate this gibberish into the plain English....

    The error appears to be in ZTDC_INT_OB_LOAD_TENDER_NAST, which is a user program.  I suggest you talk to the developer who created this program.
    Looks like some sloppy prgramming to me.
    You should be able to trace through the program to find the real culprit

  • ABAP dump LOAD_PROGRAM_NOT_FOUND in S_ALR_* transactions

    Hi,
    I am trying to execute S_ALR_87011792 and S_ALR_87012249 and getting LOAD_PROGRAM_NOT_FOUND abap dumps in tdms receiver client in dev system. We are on ECC6.
    Here is the dump details:
    Short text
        Program "GP4A1HFKFHN7RW6BOFW65F3ZTQ9" not found.
    What happened?
        There are several possibilities:
        Error in the ABAP Application Program
        The current ABAP program "SAPLKYP4" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        or
        Error in the SAP kernel.
        The current ABAP "SAPLKYP4" program had to be terminated because the
        ABAP processor detected an internal system error.
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    Error analysis
        On account of a branch in the program
        (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
        or a transaction call, another ABAP/4 program
        is to be loaded, namely "GP4A1HFKFHN7RW6BOFW65F3ZTQ9".
        However, program "GP4A1HFKFHN7RW6BOFW65F3ZTQ9" does not exist in the library.
    Short text
        Program "GP4A1HFKFHN7RW6BOFW65F3ZTQ9" not found.
    What happened?
        There are several possibilities:
        Error in the ABAP Application Program
        The current ABAP program "SAPLKYP4" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        or
        Error in the SAP kernel.
        The current ABAP "SAPLKYP4" program had to be terminated because the
        ABAP processor detected an internal system error.
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    Error analysis
        On account of a branch in the program
        (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
        or a transaction call, another ABAP/4 program
        is to be loaded, namely "GP4A1HFKFHN7RW6BOFW65F3ZTQ9".
        However, program "GP4A1HFKFHN7RW6BOFW65F3ZTQ9" does not exist in the library.

    Hello,
    Please check the SAP notes 84023 and 361491 and regenerate the reports. It solves this error in 99% percent of the cases.
    If you need, please import the report from client 000 in the IMG.                 
    The path to follow is:                                                                               
    Financial Accounting -> General Ledger Accounting                  
      -> Information System -> Drilldown Reports (G/L Accounts)          
      -> Report -> Import Report from Client 000                         
    Regards,
    Renan

  • LOAD_PROGRAM_NOT_FOUND Short dump in R/3

    Hi frnds,
    I am facing some short dump problem while loading the data from R/3 BW, its a master data.
    The short dumps are LOAD_PROGRAM_NOT_FOUND and RAISE_EXCEPTION in R/3.
    Not able to find the exact problem and please suggest some OSS Notes.
    Thanks
    Hari

    hi Hari,
    check if helps oss note 899405-Master data extrctn: LOAD_PROGRAM_NOT_FOUND in source system
    Symptom
    You are loading master data in delta mode from an SAP source system. The DataSource uses generic extraction in the process.
    The request is displayed in the monitor as being incorrect. The status indicates that the extraction process has probably terminated with a runtime error.
    In the source system, you find the runtime error LOAD_PROGRAM_NOT_FOUND with the exception CX_SY_PROGRAM_NOT_FOUND. The point of termination is in the function module RSA3_GEN_GET_DATA.
    The short dump occurs only if there is no data available for the delta.
    Other terms
    OLTP, extractor, data extraction, DataSource, service API, SAPI, dump, SAPLRSA3, LRSA3U03, RSAPTM2, EXTRACTOR_FETCH, EXTRACTOR_INIT, NO_MORE_DATA
    Reason and Prerequisites
    This is caused by a program error.
    When you implemented Note 853001, calls for function modules were relocated to subroutines. This changed the query for the exception NO_MORE_DATA in such a way that it is not caught when the extractor is initialized.  The extraction process then tries to start the program, but the program has not been generated because data is missing. The system issues the short dump.
    Solution
    After you have implemented the correction specified below, you must reactivate the transfer rules for the affected DataSource. It is only by doing this that the correction is also implemented in the generated program for the extraction process.
    To correct the problem, you need to have Support Package 07 in the relevant source system Service API 7.00. The attached composite note informs you of the software components that contain Service API 7.0 and specifies the corresponding Support Packages for these components.
    As an alternative, you can also implement the advance correction from the attachment.
    You must implement the correction in the BW system only if it is affected in its role as a source system for itself (myself connection) or for another BW system.
    Note: Service API is an internal component. It is not delivered separately, but as part of other software components: PI, CRM, PI_BASIS and a number of others. For this reason, a composite note has been created which tells you in which Support Packages of the above-mentioned software components the SAP correction note is contained. However, the composite note is not released until the release date of the corresponding SAPI Support Package. Different SAPI versions are delivered for Basis Releases 3.1I, 4.0B, 4.6D, 6.20 and 6.40. The version for 4.0B is also valid for R/3 Releases 4.6B and 4.6C.

  • LOAD_PROGRAM_NOT_FOUND raise in CL_SHM_AREA- _ATTACH_READ

    I recently re-organized my code and deleted a now unused function group called SAPLZENTITLEMENT_SERVICE. All the functionality is now performed by a new function group.
    Since then I get dumps when trying to attach to the shared memory area, which was previously used by the deleted function group and which is now used by the new function group.
    LOAD_PROGRAM_NOT_FOUND Program "SAPLZENTITLEMENT_SERVICE " not found.
        The current ABAP program "CL_SHM_AREA===================CP" had to be
         terminated because one of the
        statements could not be executed.
    Call stack:
    14 METHOD       CL_SHM_AREA===================CP    CL_SHM_AREA===================CM00B     2
        CL_SHM_AREA=>_ATTACH_READ
    13 METHOD       ZCL_ES_AREA===================CP    ZCL_ES_AREA===================CM004    33
        ZCL_ES_AREA=>ATTACH_FOR_READ
    12 METHOD       ZCL_ES_SHARED_MEMORY==========CP    ZCL_ES_SHARED_MEMORY==========CM001    53
        ZCL_ES_SHARED_MEMORY=>ATTACH
    11 METHOD       ZCL_ES_CQS====================CP    ZCL_ES_CQS====================CM004     7
        ZCL_ES_CQS=>SET_CONFIGURATION
    10 FUNCTION     SAPLZES_CONTRACT_ENTITLEMENT        LZES_CONTRACT_ENTITLEMENTU01           51
        ZES_CONTRACT_ENTITLEMENT
      9 FUNCTION     SAPLZES_SERVICE_INTERFACE           LZES_SERVICE_INTERFACEU01              34
        ZES_CONTRACT_ENT_ES10
      8 FORM         SAPLZES_SERVICE_INTERFACE           LZES_SERVICE_INTERFACEV01              15
        ZES_CONTRACT_ENT_ES10
      7 METHOD       CL_HTTP_EXT_SOAPHANDLER_RFC===CP    SOAPINCS_DOCUMENT                    1175
        CSOAPSERVERDOCUMENT=>CALL_FUNCTION
      6 METHOD       CL_HTTP_EXT_SOAPHANDLER_RFC===CP    SOAPINCS_REQPROC                      342
        CSOAPREQUESTPLUGINRFC=>ISOAPREQUESTPLUGIN~PROCESS_PAYLOAD
      5 METHOD       CL_HTTP_EXT_SOAPHANDLER_RFC===CP    SOAPINCS_REQPROC                      256
        CSOAPREQUESTPROCESSOR=>PROCESS_REQUEST
      4 METHOD       CL_HTTP_EXT_SOAPHANDLER_RFC===CP    CL_HTTP_EXT_SOAPHANDLER_RFC===CM001    87
        CL_HTTP_EXT_SOAPHANDLER_RFC=>IF_HTTP_EXTENSION~HANDLE_REQUEST
      3 METHOD       CL_HTTP_SERVER================CP    CL_HTTP_SERVER================CM017   346
        CL_HTTP_SERVER=>EXECUTE_REQUEST_FROM_MEMORY
      2 FUNCTION     SAPLHTTP_RUNTIME                    LHTTP_RUNTIMEU02                      886
        HTTP_DISPATCH_REQUEST
      1 MODULE (PBO) SAPMHTTP                            SAPMHTTP                               13
        %_HTTP_START
    More interesting is that I get those dumps every time, when we call into SAP from the ES Java side, but I could not reproduce the dumps when calling the functions in SAP directly.
    Also it doesn't make a difference whether I connect via JCo or via SOAP.
    Do you have any ideas to this issue?
    I parsed already SAP notes and could not find any hint ....
    So any help would be highly appreciated!
    Best regards,
    Birgit

    Try Activatig the complete function group function by function. There seems to be probelm in your syntax.
    if not resolves goto se38 and paste 'CL_SHM_AREA===================CP'
    and do a syntax check.
    This happens with Webdynpros of BSPs sometimes too.
    A

  • Load_program_not_found in zprogram

    HI,
    CREATED A ZPROGRAM WORKING  IN THE TESTING SERVER, TRANSPORTED TO PRODUCTION SERVER,
    SUCCESSFULY, BUT GIVING DUMP ERROR WITH THE MESSAGE "LOAD_PROGRAM_NOT_FOUND"
    IN THE PRODUCTION SERVER. PLEASE LET ME KNOW  WHAT HAS TOBE DONE.
    REGDS
    TRESSAA
    Moderator message: please search for available information/documentation on this specific error message, do not post in all upper case in these forums.
    Edited by: Thomas Zloch on Oct 30, 2010 9:35 PM

    There are several NOTES for similar kind of issues.. those should help..

Maybe you are looking for