Dump - DYNPRO_NOT_FOUND

Hi,
I tried to created a "Request for Quotation" but system hangs with the following error:
Runtime Errors         DYNPRO_NOT_FOUND
Date and Time          12.11.2008 10:45:56
Short text
     Dynpro does not exist
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPMM06E" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     The system attempted to use dynpro 0301 in program "SAPLXM06".
     This dynpro does not exist.
Trigger Location of Runtime Error
     Program                                 SAPMM06E
     Include                                 MM06EO0C_CUSTSCR1_HEAD_SET_DAT
     Row                                     10
     Module type                             (MODULE PBO)
     Module Name                             CUSTSCR1_HEAD_SET_DATA
How can I correct the problem ?
Best regards
Edited by: Julius Bussche on Nov 12, 2008 11:56 AM

Hi
Answer is pure assumption
Pls check the following OSS notes
Note 430771 - ME21N: Customer enhancement MM06E005 active after SuppPack22
Note 389059 - MM06E005: Short dump 'CUSTSCR1_HEAD_SET_DATA'
Pls take opinion from Basis / SAP before implementing the note
Regards
Madhan D

Similar Messages

  • SHORT DUMP DYNPRO_NOT_FOUND, DOUBLE CLICK ON OPERATION IN NETWORK GRAPHIC

    Dear Experts,
    I am getting shor dump error as DYNPRO_NOT_FOUND in transaction IA02 while double clicking on operation in newtwork graphic.
    I found SAPNOTE 397750 for releases SAP_APPL 46 and 46C. But we are using ECC 5.0 SAP_APPL 500.
    Please give the solution how to resolve this dump error.
    Thanks & Regards,
    Tushar

    Hi,
    there is no coding correction in the note, hence please compare the setting mentioned in the note with your system, if the entry does not exist, you might have to maintain it. otherwise, i am afraid you need to submit a OSS message regarding it.
    Regards
    Jane

  • XD03/XD02 Short Dump (DYNPRO_NOT_FOUND)

    Hi Group,
    When I enter a customer in XD02 or XD03 which does not exist yet & hit enter, first I get a message 'Customer XXX has not been created' and then a short dump is produced.
    Runtime errors         DYNPRO_NOT_FOUND
    Program "SAPLSZA1" tried to use screen 0000.
    The screen does not exist.
    Have any of you faced this issue. Is it a SAP problem?
    Thanks & Regards,
    Midhun.

    hi
    good
    sometime it happens like that whenever we try to change the customer using the XD02 AND display the customer using XD03 and we dont have the proper customer number it goes to short dump because when we press the enter key internally it searchse for some ok code and there respective actions and when it does not get them it creates a short dump.
    thanks
    mrutyun^

  • Tx VD02 Dump DYNPRO_NOT_FOUND

    Hi everybody!
    I have a problem with the Tx. VD02, In my DEV environment. When I want to consult any client and i press check i receive the following dump:
    Err.tmpo.ejec.: DYNPRO_NOT_FOUND
    Runtime Errors         DYNPRO_NOT_FOUND                                                
    Date and Time          15.10.2010 12:03:49                                                                               
    Short text                                                                               
    Dynpro does not exist                                                                               
    What happened?                                                                        
         Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLSZA1" had to be terminated because it has           
         come across a statement that unfortunately cannot be executed.                                                                               
    Error analysis                                                                        
         The system attempted to use dynpro 0000 in program "SAPLSZA1".                    
         This dynpro does not exist.                                                                               
    Trigger Location of Runtime Error                                                     
         Program                                 SAPLSZA1                                  
         Module Name                             SYSTEM-EXIT                               
    I was trying to find the error and i found that it happens in the following code.
    ROCESS BEFORE OUTPUT.
    MODULE TABSTRIP_DYNTAB.
    MODULE DYNPRO_MODIFIZIEREN. " muss 1. Modul sein !!
    MODULE tabstrip_dyntab_copy. " uh
    MODULE ZAV_VORBEREITEN.
    MODULE REFDATEN_VORSCHLAGEN.
    MODULE SAVE_MCOD_FUELLEN.
    MODULE pfstatus_ermitteln.
    MODULE titel_setzen.
    *CALL SUBSCREEN ADDRESS INCLUDING 'SAPLSZA1' '0300'.*
    MODULE PUBLISH_RESTORE_SWU_OBJECT.
    MODULE OIF_GET_LOCATION_DATA SWITCH OIF_BUSINESS_LOCATION.
    CALL SUBSCREEN OIFLOCS1 INCLUDING 'SAPLOIFK' '0110'. "IS2ERP
    "SWITCH OIF_BUSINESS_LOCATION
    Per any reason, when that subscreen is called, the program sends dynpro 0000.
    When i use the same program in my QAs environment, there is no problem.
    Does anybody have any idea?, Thanks in advance.
    Ps.: Sorry about my English, I know it is not so good.

    SAP Note 931355 - BP: "DYNPRO NOT FOUND" after upgrade ->
    6.40 / 7.00
    Note Language: English Version: 7 Validity: Valid Since 06/11/2009
    This note appears to address your problem?

  • DYNPRO_NOT_FOUND dump in program MP126300

    Hello experts,
    While we are running a TCODE pp01 select Business role and choose create, we are getting a ABAP DUMP DYNPRO_NOT_FOUND.
    Error analysis: The system attempted to use dynpro 0003 in program"MP126300". This dynpro does not exist.
    we have searched the marketplace for Notes but no success.
    Even though Some business roles are assigned, when we login to the WEB UI we get a message as :
    Logon is not possible because you have not been assigned to a business role; contact your system administrator
    Our environment
    Application : CRM 7.0, Os : windows 2003, Database   : MS sql 2005.
    Thanks and Regards,
    Ranadhir

    Hello Ranadhir,
    infotype 1263 business role seems to be missing.
    In the transaction SOBJ -> Object: PDST -> Piece list are defined all inotypes that will be included in the transport request using the report RHMOVE30.
    The check can be made with the report RHSOBJCH. Please run this report you will find mixssing infotype 1263. Select and run Adjust.
    Afterwards this entry should be maintained in the transaction SOBJ an the report RHMOVE30 should collect this infotype in the transportrequest. You can check note 442334.
    Hope this will resolve your issue.
    Thanks
    Raja Pamireddy
    CRM Moderator

  • DYNPRO_NOT_FOUND in ME41

    Dear All,
    I am facing some issue in standard Transaction code ME41,  on initial screen when i enter mandatory field data and when i hit enter  its shows dump error. The short dump screenshot is attached kindly find and please do the needful.

    Hi,
    Please check the Notes
    1517584 - Short dump DYNPRO_NOT_FOUND in T-code ME21(N), ME51(N), ME41, ME31(K/L)
    Check and revert
    Regards
    Pavan

  • Runtime error DYNPRO_NOT_FOUND when creating business entity in SAP RE-FX

    Hello,
    I have a problem...
    In SAP RE-FX (Real Estate) when I try to do the most basic thing like creating a business entity (transaction REBDBE), I get a runtime error 'DYNPRO_NOT_FOUND'.
      Program                                SAPLBUSS
      Include                                  LBUSSO00
      Row                                     1.543
      Module type                          (MODULE PBO)
      Module Name                         PBO_START_SUBSCREEN
    Does anybody know how I can fix this?
    Thanks in advance!

    Hi
    look OSS Note [162119|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3136323131313926] note youe need to have market place login
    1621119 - Dump DYNPRO_NOT_FOUND in SAPLBUSS in module PBO_START_SUBSCREEN
    Regards,
    koolspy.

  • Errors in weekly data collection

    Hello,
    I am running ecc6 sp 15 on AIX 5.3 and oracle 10.2.0.2
    when i goto transaction st03 -> workload -> <instance_name> ->week dir - when i try to open one of the logs i get the following error message
    on the botton of the screen - "unknown period type (W).
    when i try to watch a daily log it is displayed without a problem.
    moreover when i push on the change user mode button (expert mode or
    service engineer options) and move to service engineer, i try to
    calculate both in background and in dialog i get the same error
    message - unknown period type (W).when i press again on the user mode
    button (expert mode or service engineer options) i get a dump -
    DYNPRO_NOT_FOUND - dynpro does not exist, the current abap progrem
    SAPWL_ST03N HAD TO BE TERMINATED.
    the saposcol is running, the background job -
    SAP_COLLECTOR_FOR_PERFMONITOR is running and working (daily data is
    collected and displayed correctly)
    each week i get an early watch alert report but with errors in data
    collection section with the following exception -
    SAPWL_WORKLOAD_GET_SUMMERY_I_W - NO_DATA_FOUND.
    please advise asap
    Regards,
    Moshe

    done - had to import note 1014116

  • Regarding applying SAP Note 1172084

    Hi all,
    I have applied SAP Note 1172084 - PKMC: Dump DYNPRO_NOT_FOUND for control cycles of type SeqJC through SNOTE  as we are receiving run time error Dynpro Not Found...Even though it didnt solve our problem..
    Read in some site that if any changes are done to the screen, we need to manually apply the note (i.e. not through SNOTE), but i didnt find any program or function module in the source code mentioned by the note...
    Could you pls. help in solving the problem..
    Thanks,
    Subbu

    > Read in some site that if any changes are done to the screen, we need to manually apply the note (i.e. not through SNOTE), but i didnt find any program or function module in the source code mentioned by the note...
    There are corrections in the note, if you scroll down to "correction instructions" for your release and you open it, there are 4 program changes displayed.
    If you can apply the note via SNOTE and the program is still dumping I'd open an OSS call.
    Markus

  • STO3N is not working

    Dear Expertise,
             In one of our newly installed test system St03n transaction resulting into the following errors.in ST03N Expertmode>detailed analysis>last minute load.
    - RFC problem No data available.
    - Unknown period type.
    and in st22 the following dump
    "DYNPRO_NOT_FOUND"
    "The current ABAP program "SAPWL_ST03N" had to be terminated because it has
    come across a statement that unfortunately cannot be executed".
    System configuration:
    windows 2003 sp1,ECC6.0,ORACLE 10.2.0.2., SAP Basis patch level 09.
    as per our client (customer) we cannot enhance the sap basis
    patch to 12 in the system.as mentioned in the sapnote 1032653.
    Please let me know that is there any other alternative resolution for this kindly help me out in resolving this issuse
    Thanks in advance ,
    venkata satya

    Hi Venkata,
    1) Error message "RFC problems: No data available"
    This issue is generally due to the difference in the time zone settings at the operating system level and at the R/3 level.Please apply the recommendations provided in the note 926290 which mentions the reason for the issue.
    SAP Note 926290 - SWNCCOLL: SAP workload NW collector collects no data
    2) When checking "Load History," a runtime error occurs
    (DYNPRO_NOT_FOUND) for program SAPWL_ST03N.
    Please review the following notes and apply if suitable with your issue
    SAP Note 967644 SAPWL_ST03N: Syntax error
    Hope this helps to resolve your issues.
    Thanks and Regards
    Tanuj Gupta
    Award points if helpful.

  • DYNPRO_NOT_FOUND  in abap program dumps in st22

    Hi All,
    We are  facing an issue in Abap dumps
    Run Time error  DYNPRO_NOT_FOUND
    Termination occurred in the ABAP program "MP058400" - in "SET_INIT_TAB".
    The main program was "MP058400 ".
    In the source code you have the termination point in line 49
    of the (Include) program "MP058420".
    I have an idea that it is releated to Screens but  its a standard Tcode PA40  and info type 584.
    Please suggest the how can i solve the dump.
    Regards
    Harsha Teja

    Hi Deepak,
    We had installed ECC 6.0 Ehp5  recently and released to HCM consultant  they are testing PA30 infotype 584.
    Regrads
    Harsha Teja

  • Runtime Error DYNPRO_NOT_FOUND after transport of customer subscreen

    Hi,
    We have created a new customer subscreen 9002 using transaction OXK1. When the subscreen was transported to the quality system, the subscreen was not generated thereby causing a dump (error DYNPRO_NOT_FOUND) in transaction FB01 which was using the subscreen.
    Are customer subscreens not regenerated automatically when they are transported?
    Thanks.
    Ekit

    HEllo,
    Sometimes error happen in this process. Please re-generate your scrren.
    goto  OXK1 Select the screen and go to the menu option Subscreen -> Generate.  
    REgards,
    REnan Correa

  • Dynpro_not_found ML81N

    the scenario: Once user exit project Z1(package is $TMP). It contains one enhancement assignment Z2. Z2 has some user's customized codes. Z2 is active and then saved in one change request and last it is sent to PRD and it can work. This sounds some strange but please temptly neglect it. Z2 is one user exit of T-code ML81N.
    To avoid some unexpected issues, I want to chagne Z1's package from $TMP to one that can be sent to PRD. So I deleted Z1 and then created project Z3. Its package is zazpc which can be sent to PRD. Then put Z2 into Z3, active Z3, then I have get the dump information when I run ML81N.
    The dump information is below. But I didn't create any screen in the user exit. I just put input some codes in the enhancement 'SRVESSR'.
    "Runtime Errors         DYNPRO_NOT_FOUND
           Occurred on     09/11/2009 at 15:57:14
    Screen does not exist
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLMLSR " had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    The program had to be terminated.
    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.
    Error analysis
    Program "SAPLXMLU" tried to use screen 0399.
    The screen does not exist.
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:"

    Hi Ganjian,
    first of all you have to find out where the screen call is issued.
    In Include LMLSRF1B, set a break-point before and after CALL CUSTOMER-FUNCTION '001' (line 50) and check if really comes from your user exit. In the dump, you can also see the Active Calls/Events section to find out more.
    As your dump says
    Program "SAPLXMLU" tried to use screen 0399.
    it might be possible that your user exit does more than you are aware of.
    Also possibly someone already used the new ENHANCEMENT FRAMEWORK to insert code at some SPOT.
    Regards,
    Clemens

  • CV04N Dump in Object Link

    Hi,
    I have developed Object Link to ML81N. This linkage is working fine.
    when i go to CV04n by entering the Document type and then click on Object link and choose the tab as service entry sheet its going for dump.
    Dump history shows that Dynpro does not exist
    "DYNPRO_NOT_FOUND" " "
    "SAPLCV100" or "LCV100O01"
    "INIT_404"
    I hv included my custome screen in SAPLCV130. i dnt hv any issue in cv01n, cv02n,cv03n.
    Plz help me to resolve this issue.
    Regards
    Janani.

    Hi Janani,
    This error is typically observed incase a object maintained for one of the document types uses a non-existing screen number.
    This behavior can be corrected by entering the right screen number or removing the object in the customizing.
    You may find more details in the wiki links below:
    http://wiki.sdn.sap.com/wiki/display/PLM/PerformanceinCV04N-Timeout+Dump
    http://wiki.sdn.sap.com/wiki/display/PLM/DYNPRO_NOT_FOUNDDumpin+CV04N
    Regards,
    Pradeepkumar Haragoldavar

  • Short Dump in XD02

    Hi,
    I need a solution for the short dump which i'm getting at the time of accessing the XD02/XD03 transaction for only one particular customer number.
    Interestingly the same customer number was useful in that transaction a week before and i was able to add that customer as my shipto in my sales order with all its addresses appearing. Now no details of that customer is appearing and when i double click on shipto field (at VA02) or given the same number at XD02/XD03 transaction, an short dump arises.
    It says this...
    Program "SAPLSZA1" tried to use screen 0000.
    The screen does not exist.                                                                               
    Source code extract                                                                               
    000010   * ABAP-System Include for all programs                                  
    000020   constants SPACE value ' ' %_predefined.                                 
    000030                                                                           
    000040   * SYST-Felder als SY-Felder ansprechbar machen.                         
    000050   tables: SYST,                                                           
    000060           sy %%internal%%.                                                
    000070   *                                                                       
    000080                                                                           
    000090   tables RSJOBINFO.                      "for SUBMIT .. VIA JOB ..        
    000100                                                                           
    000110   data: begin of common part %_SYS%%,                                     
    000120           SCREEN    type SCREEN,                                          
    000130           %_PRINT   type PRI_PARAMS,                                      
    000140           %_ARCHIVE type ARC_PARAMS,                                      
    000150         end   of common part.                                             
    000160   *                                                                       
    000170   data: %_VIASELSCR type X value '04' %_predefined.                       
    000180                                                                           
    000190   system-exit.                                                            
    000200     perform (SY-XFORM) in program (SY-XPROG).                             
    000210                                                                           
    000220   * Nach Laden des Dynpros                                                
    000230   module %_CTL_INIT output.                                               
    000240     perform %_CTL_INIT in program SAPMSSYD using SY-REPID if found.       
    >   endmodule.                                                              
    000260                                                                           
    000270   * Nach DCO                                                              
    000280   module %_CTL_OUTPUT output.                                             
    000290     perform %_CTL_OUTPUT in program SAPMSSYD using SY-REPID if found.     
    000300   endmodule.                                                              
    000310                                                                           
    000320   * Vor DCI                                                               
    000330   module %_CTL_INPUT input.                                               
    000340     perform %_CTL_INPUT in program SAPMSSYD using SY-REPID if found.      
    000350   endmodule.                                                              
    000360                                                                           
    000370   * Vor at exit-Modul (wenn vorhanden)                                    
    000380   module %_CTL_AT_EXIT input.                                             
    000390     perform %_CTL_AT_EXIT in program SAPMSSYD using SY-REPID if found.    
    000400   endmodule.                                                              
    000410                                                                           
    000420   * Erstes Modul in PAI                                                   
    000430   module %_CTL_PAI input.                                                 
    000440     perform %_CTL_PAI in program SAPMSSYD using SY-REPID if found.
    I have also got a message in the "How to correct the error" column to search for some OSS note for this issue. I tried and not able to find the exact one. The search criteria proposed for the OSS note was
    "DYNPRO_NOT_FOUND" C    
    "SAPLSZA1" or "<SYSINI>"
    "%_CTL_INIT"            
    This dump appears only for one customer number and all the other numbers are working fine at XD02/XD03. Please help me with your valuable solutions.

    Hi Ravi,
    Thanks again.
    I performed the steps suggested by you and found the following implementations were available.
    <u>For CUSTOMER_ADD_DATA Badi</u>:
    1. FM_CUSTOMER_ADD_DATA - Implementation of CUSTOMER_ADD_DATA by Public Sector
    2. ZCUSTOMER_ADD_DATA - For adding custom field in the Customer Master 
    <u>For CUSTOMER_ADD_DATA_BI Badi</u>:
    1. FM_CUSTOMER_ADD_D_BI - IS-PS: Additional Data for Customers (Batch-Input and ALE)
    <u>For CUSTOMER_ADD_DATA_CS Badi</u>:
    1. FM_CUSTOMER_ADD_D_CS - Implementation of CUSTOMER_ADD_DATA_CS by Public Sector
    2. ZCUST_ADD_DATA_CS - Adding custom field to the customer master
    Now shall i just give these names and deactivate in Se19. Sorry it might be silly but i really haven't worked on badi's. Hope deactivating it will not cause any surprising behaviour in the transaction.
    Please let me know your comments.

Maybe you are looking for