Short dump while executing info package in 3.5 data flow?

Hi,
i am getting short dump while executing info package while executing info package. it was working perfectly 2 days back suddenly it is giving this problem. it is a full load for info object text data and i have only 600 records. when i tried with " only info package" it is working perfectly n bringing the data into PSA. But when i use "PSA and the into data target" it is giving short dump.
i replicated Data source and also i activated transfer rules, update rules still it is not working. When i check with another info objects it is working perfectly fine. i dont know what is wrong with only particular info object.
Please find attached short dump.
Thanks

Hi,
When you load transaction data I think there is a deadlock.
Check in the process overview (transaction SM50) the waiting processes are in program SAPLSENA .
The program SAPLSENA is the lock handler tool.
Also check if  ACR is running on this target while your load is happening.
Check in SM12 if there are any lock entries for the Infoobject to which you are loading data and on RSICCONT table .
Try reloading after deleting the locks manually.
Regards.

Similar Messages

  • SHORT DUMP WHILE EXECUTING DTP.

    Hi Gurus,
    I have got a short dump while executing DTP the Error is as Follows.
    Runtime Error: MESSAGE_TYPE_X.
    Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
    2.There is a error in the application program
    And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
    But i have no much time and i have to someway or the other execute the DTP and load the data.
    Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
    Regards
    Amar.

    Hi Amar,
    If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
    Thanks..
    Shambhu

  • Short Dump while executing New Hire (action type) in PA40

    Hi All,
    i am getting short dump while executing PA40 for new hire action type can anyone look into this and guide as i am new to HCM.
    Category               ABAP Programming Error                                                      
    Runtime Errors         SYNTAX_ERROR                                                                
    ABAP Program           /1PAPAXX/HDR_21000A                                                         
    Application Component  Not Assigned                                                                
    Date and Time          21.08.2014 14:07:03                                                         
    Short text                                                                                       
        Syntax error in program "/1PAPAXX/HDR_21000A ".                                              
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
        The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in                     
        include "/1PAPAXX/HDR_21000AO01 " in                                                        
        line 52:                                                                                     
        ""LV_LENGTH" has already been declared"                                                      
        The include has been created and last changed by:                                            
        Created by: "HCM04 "                                                                         
        Last changed by: "HCM03 "                                                                    
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                                 
        Please eliminate the error by performing a syntax check                                      
        (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".                        
        You can also perform the syntax check from the ABAP Editor.                                  
        If the problem persists, proceed as follows:                                                 
        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                                                                                   
        The following syntax error was found in the program /1PAPAXX/HDR_21000A :                    
        ""LV_LENGTH" has already been declared"                                                      
    How to correct the error                                                                         
        Probably the only way to eliminate the error is to correct the program.                      
        If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                      
        1. The description of the current problem (short dump)                                       
           To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                              
        2. Corresponding system log                                                                  
           Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                              
        3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                       
        4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                          
    System environment                                                                               
        SAP Release..... 731                                                                         
        SAP Basis Level. 0007                                                                        
        Application server... "dc-ds-erp"                                                            
        Network address...... "172.16.23.111"                                                        
        Operating system..... "Linux"                                                                
        Release.............. "3.0.13-0.27-default"                                                  
        Hardware type........ "x86_64"                                                               
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 1                                                                      
        Shortdump setting.... "full"                                                                 
        Database server... "dc-ds-erp"                                                               
        Database type..... "ORACLE"                                                                  
        Database name..... "ECD"                                                                     
        Database user ID.. "SAPSR3"                                                                  
        Terminal.......... "NLC-HP"                                                                  
        Char.set.... "C"                                                                             
        SAP kernel....... 720                                                                        
        created (date)... "Sep 14 2013 06:16:24"                                                     
        create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"                            
        Database version. "OCI_112, 11.2.0.3.0, V1, default"                                         
        Patch level. 500                                                                             
        Patch text.. " "                                                                             
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
        SAP database version. 720                                                                    
        Operating system..... "Linux 2.6, Linux 3"                                                   
        Memory consumption                                                                           
        Roll.... 0                                                                                   
        EM...... 37708200                                                                            
        Heap.... 0                                                                                   
        Page.... 106496                                                                              
        MM Used. 4666776                                                                             
        MM Free. 3709976                                                                             
    User and Transaction                                                                             
        Client.............. 210                                                                     
        User................ "HCM03"                                                                 
        Language key........ "E"                                                                     
        Transaction......... "PA40 "                                                                 
        Transaction ID...... "53EF470299AB5D67E1000000AC10176F"                                      
        EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"                                  
        EPP Connection ID....... 00000000000000000000000000000000                                    
        EPP Caller Counter...... 0                                                                   
        Program............. "SAPFP50M"                                                              
        Screen.............. "MP000000 1000"                                                         
        Screen Line......... 3                                                                       
        Debugger Active..... "none"                                                                  
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "SAPFP50M" - in                                     
        "GET_HEADER_WITH_TCLAS".                                                                    
        The main program was "MP000000 ".                                                            
        In the source code you have the termination point in line 146                                
        of the (Include) program "FP50MDHD".                                                         
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
      116
      CALL FUNCTION 'HR_HEADER_GET'                                                            
      117
          EXPORTING                                                                            
      118
               DHDID                    = FHD_HID                                              
      119
               BEGDA                    = BEGDA                                                
      120
               TCLAS                    = TCLAS                                                
      121
    * Es wird nur einer der folgenden 3 Parameter benutzt.                                     
      122
    * Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                 
      123
    * Der erste der nicht initial ist wird ausgewertet.                                        
      124
    *           MOLGA                   =                                                      
      125
               P0001                    = P0001                                                
      126
               PERNR                    = PSPAR-PERNR                                          
      127
          IMPORTING                                                                            
      128
               PROG                     = HEADER_PROG                                          
      129
               DNUM                     = HEADER_DYNNR                                         
      130
           EXCEPTIONS                                                                          
      131
                HEADER_DEACTIVATED          = 1                                                
      132
                HEADER_UNKNOWN              = 2                                                
      133
                HEADER_GENERATE_DEACTIVATED = 3                                                
      134
                HEADER_GENERATE_FAILED      = 4                                                
      135
                INTERNAL_ERROR              = 5                                                
      136
                OTHERS                      = 6.                                               
      137
      138
      IF NOT SY-SUBRC IS INITIAL.                                                              
      139
    * Bei Problemen gibt's eben ein leeres Dynpro.                                             
      140
        HEADER_PROG = 'SAPMP50A'.                                                              
      141
        HEADER_DYNNR = '0090'.                                                                 
      142
      ELSE.  " NOT sy-subrc IS INITIAL.                                   "                    
      143
    * Dann setzen wir jetzt auch noch das Datum fest.                                          
      144
        PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                         
      145
    * Und schalten auf Uebergabe der PERNR mit globalen Variablen.                             
    >>>>>
        PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                       
      147
      ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                    
      148
    * Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                         

    Hi,
    Error Log: Syntax error
    ""LV_LENGTH" has already been declared"
    please check LV_LENGTH variable declaration.
    It may be declared more once!

  • System Throws short dump while executing data source 2LIS_11_VASCL in RSA3.

    Hello Experts,
    I got short dump while executing data source 2LIS_11_VASCL in RSA3.
    The details are as follow.
    When importing object "MC11VA0SCL_TAB", the structure did not match the
    structure of the target object. The error occurred in component
    no. 567.
    This may be due to one of the following reasons:
    - the structure is actually different (the next field has, for
      example, a different data type) or
    - the same sequence of components were exported and imported,
      but the fields were from other include units.
    I have checked source and target fields and those are of same length and data type.
    Could you please give some points why this short dump occurs.
    Thanks
    Konda Reddy

    Hi,
    This error is not between BI and R/3.  It is within R/3.  You may have setup data and then modified the datasource.
    Delete setup data, generate your datasource again.  Setup data and try again.
    If you are on a live system with data setup after a downtime and you do not want to delete it, then bring your datasource to the original state when you setup data and pull data.
    Cheers....

  • Short dump while executing few queries , which has got created on Infoset.

    Hi,
    We went to BI7.0 upgrade from BW3.x now.
    We are getting short dump short dump while executing few queries and work book, which has got created on Infoset.
    When i was executing work book where i was geting popup message saying that "Erro ZSD_XST_F00121 is invalid".When i click that message it went to dump.
    I was getting this error while executing query on infoset.
    We are currently SP Stack 13(Patch level 15).
    I found some note 1067918 as per the shortdum,where it is saying that you need to apply SP Stack14(patch level16).
    Please some one who had earlier this kind of issue.
    I appreciate your answer.

    Dear Krish,
    Yes, It is the patch problem.
    We too faced the same issue on Infosets.
    Apply SP 15.
    Regards,
    Ram.

  • Short Dump while executing ALV Grid.

    Hi All,
    I m getting a short dump while trying to execute an ALV.
    The dump exception is of type
    CX_SY_DYN_CALL_ILLEGAL_TYPE class.
    The message displayed is :  " Call to form 'GI_FIELDCAT' is incorrect .The actual parameter in PERFORM is different data type than requested for form GI_FIELDCAT "  .
    The part of programe included is as follows:
      FORM build_fieldcat .
        PERFORM gi_fieldcat USING 'MBLNR' text-014 '1' '20'.
        PERFORM gi_fieldcat USING 'ZEILE' text-005 '2' '4'.
        PERFORM gi_fieldcat USING 'MATNR' text-006 '3' '18'.
        PERFORM gi_fieldcat USING 'MAKTX' text-028 '4' '40'.
        PERFORM gi_fieldcat USING 'MATKL' text-029 '5' '40'.
        PERFORM gi_fieldcat USING 'BUDAT' text-027 '6' '10'.
        PERFORM gi_fieldcat USING 'MENGE' text-026 '7' '9'.
        PERFORM gi_fieldcat USING 'DMBTR' text-025 '8' '13'.
        PERFORM gi_fieldcat USING 'WAERS' text-011 '9' '5'.
        PERFORM gi_fieldcat USING 'RSNUM' text-012 '10' '10'.
        PERFORM gi_fieldcat USING 'PSPHI' text-013 '11' '10'.
    ENDFORM.                    " build_fieldcat
    FORM gi_fieldcat  USING    fieldname TYPE slis_fieldcat_alv-fieldname
                               colmname  TYPE slis_fieldcat_alv-seltext_m
                               colmpos   TYPE slis_fieldcat_alv-col_pos
                               outputlen TYPE slis_fieldcat_alv-outputlen.
      wa_fieldcat-fieldname   = fieldname.
      wa_fieldcat-seltext_m   = colmname.
      wa_fieldcat-col_pos     = colmpos.
      wa_fieldcat-outputlen   = outputlen.
    wa_fieldcat-
      APPEND wa_fieldcat TO it_fieldcat.
      CLEAR  wa_fieldcat.
    ENDFORM.                    " gi_fieldcat
    Can ayone gimmi a solution for the same.

    Hi,
    Try to change ur code like the below.
    Attached: sample code
    Building field catalog
      PERFORM modify_catlog USING:
      'GT_OUTPUT' 'AUART'  text-t02  '1',
      'GT_OUTPUT' 'KUNNR'  text-t03  '2',
      'GT_OUTPUT' 'NAME'   text-t04  '3',
      'GT_OUTPUT' 'KWMENG' text-t05  '4',
      'GT_OUTPUT' 'VRKME'  text-t06  '5',
      'GT_OUTPUT' 'LFIMG'  text-t07  '6',
      'GT_OUTPUT' 'GEWEI'  text-t08  '7',
      'GT_OUTPUT' 'VOLUM'  text-t09  '8',
      'GT_OUTPUT' 'VOLEH'  text-t10  '9',
      'GT_OUTPUT' 'BRGEW'  text-t11 '10',
      'GT_OUTPUT' 'UOMGW'  text-t12 '11',
      'GT_OUTPUT' 'VARCE'  text-t13 '12',
      'GT_OUTPUT' 'UOMVR'  text-t14 '13'.
    FORM modify_catlog USING    pa_tabname TYPE string
                                pa_field   TYPE string
                                pa_text    TYPE string
                                pa_pos     TYPE string.
      CLEAR gs_fieldcatalog.
    *Modifying field catalog
      gs_fieldcatalog-col_pos = pa_pos.
      gs_fieldcatalog-fieldname = pa_field.
      gs_fieldcatalog-tabname = pa_tabname.
      gs_fieldcatalog-seltext_m = pa_text.
      APPEND gs_fieldcatalog TO gt_fieldcatalog.
      CLEAR gs_fieldcatalog.
    l_repid = sy-repid.
    To call function to display ALV output
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
           EXPORTING
                i_callback_program = l_repid
                it_fieldcat        = gt_fieldcatalog
                     TABLES
                t_outtab           = gt_output
           EXCEPTIONS
                program_error      = 1
                OTHERS             = 2.
      IF sy-subrc <> 0.
        MESSAGE e000 WITH text-t16.
      ENDIF.
    Reward if helpful.
    Regards,
    Ramya

  • Short dump while executing job SM:EXEC SERVICES for EWA alert generation

    Hello All,
    I'm getting short dump error while executing job SM:EXEC SERVICES for EWA alert generation.I'm using EHP1@SP22 of Sol Man.
    Please find the logs
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "RDSVASCABAP_TRANS__________073
    " in include "RDSVASIABAP_TRANS__________073 " in
    line 1782:
    "Field "STATEMENT_SUMMARY001019" is unknown. It is neither in one of th"
    "e specified tables nor defined by a "DATA" statement. "DATA" statement"
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    If anyone came across such kind of dump, please reply asap, due to this, i could not generate EWA report for R/3 system 6.04.
    Thanks,
    Anand.

    >
    Anand Tigadikar wrote:
    > Thx Paul, but i already did checked this note and its not solving my issue
    Dear Anand,
    Did you perform a complete service definition replacement for SDCC/SDCCN as described in the note?
    These are manual steps you need to perform on the system and are not code corrections.
    I would suggest you perform it, if you have not, and check the SDCCN logs to review the process ran cleanly.
    Note: Please make sure SDCC_OSS is functioning and a connection to SAP can be made before
    deleting the service definitions.
    If you have already replaced the service defintions on the Solution Manager system, then no point doing it again. However checking a note and applying it are not the same thing. So I am uncertain if you replaced the service definitions or not. The dump you are getting in SM:EXEC SERVICES suggests its due to a problem with the service definitons. The recommendation is to replace them according to the process described in SAP Note 727998. If you have not done so please do so.
    If you have successfully replaced the service definitions are you still getting the same dump, or has it possibly changed?
    Regards,
    Paul

  • Urgent : short dump while executing prog

    Dear Gurus,
                      While executing a program i am getting following errors :
    Runtime Errors         PXA_NO_FREE_SPACE
    Date and Time          27.01.2008 15:17:34
    Short dump has not been completely stored (too big).
    Error analysis
        Unable to load a program of 763904 bytes.
        The PXA ('program execution area') was too small to hold all
        currently active programs for all users.
        At present, the size of the PXA is set at 144708 Kbytes.
        The largest contiguous and unlocked memory chunk has 621568 bytes.
    Please do the needful at earliest, coz its very urgent.
    Looking forward to your earliest response.
    Thanks & Regards,
    Gulrez Alam

    Hi Alam,
                  Contact your Basis team guys ASAP as there seems to be nothing wrong with the prog ....
    There is some memory management issue.
    Regards,
    Raghav

  • Short Dump while executing costing run or production orders

    Hi Guys,
    While executing the costing run or production orders saving, we are getting short dump.  it is the debugging is showing its fingers at A035 which is related to maintenance of overhead rates.
    We have maintained the overhead rates correctly. There is no issue.
    This could be some thing related to OSS notes as well.
    Just wanted to know if it has got something to do with OSS notes or something else.
    Please throw some light in this regard
    Thanks in advance

    Hi,
    In what program there is a dump? I mean, what is the log saying?
    Regards,
    Eli

  • Short dump while executing the DTP

    Dear Experts,
    While executing the DTP the system is generated short dump and it is Quality server not in Development system.
    The error details are in method Calculate_keyfigure_ds and the data is loaded for IS retails from POSDM.
    The error details:
    "The MOVE-CORRESPONDING statement can only be used on operands with a
    structured type.
    In the case at hand, this condition is not fulfilled: Operand "<L_STRUC>" has
    the type "C"."
    Regards,
    Amit

    Hi Amit ,
    Move corresponding statements can be used for structures only and from the error message it seems that there is datatype mismatch.
    Check for the errors ion link :
    http://help.sap.com/abapdocu/en/ABAPMOVE-CORRESPONDING.htm
    Hope it helps ,
    Regards,
    Supriya

  • Short dump while executing APD

    Hi Experts,
                      We have a requirement to populate key and text values for 23 charecterstics in to a flat file. For this we have created a APD with query as source, This query will bring key values. And text values are populated using APD routine which will look up respective text tables and all the result data is downloaded in to a flat file.
    When testing this APD i have come across a short dump, as all the charecterstics are placed in rows. Then i have applied static filters in the query for some of charecterstics and executed the APD. It worked. But if try to execute APD with no filters in the query it gives me short dump. Request you to suggest strategy which will avoid the short dump and improve the performance, where i can display all the 23 charecterstics key and text values.
    Thanks in advance.

    Hi Javed
    Here are couple of things what you can try
    - You can apply filters in the APD and split the data into small chunks and later collate the data into one final file, this can be done by decisions in APD
    - There is a difference how you have created your query and applied the filters/restrictions,In case of 7x queries none of the filters should be in Default tabs and all of them should be in Filters tab only
    - From my previous experiences I have seen that at times you add a dummy "Filter" type be applied in APD to avoid such issues, so give this a try as well
    Thanks
    Abhishek Shanbhogue

  • Short dump while executing report group.

    Hi,
    We are upgrading to ECC6.0 from 4.6C
    Now while testing the report group i got short dump.
    This is due to to the 'Exception condition "LOAD_PROBLEMS" raised.'
    Error analysis
        A RAISE statement in the program "SAPLSLDB" raised the exception
        condition "LOAD_PROBLEMS".
        Since the exception was not intercepted by a superior
        program, processing was terminated.
        Short description of exception condition:
        For detailed documentation of the exception condition, use
        Transaction SE37 (Function Library). You can take the called
        function module from the display of active calls.
    Function module 'SELOPTS_AND_PARAMS' in this that statement was there.
    Can some one help me out. what i have to do further.
    Thanks in advance.
    Regards,
    Deepak.

    Hi Hemanth,
    Actually what I analysed is what ever the exception raised due to this sy-subrc that exception i think the superior program is not receiving. I think due to this it is going for short dump.
    Let me know if you have any idea further.
    Thanks,
    Deepak.
    Message was edited by:
            Deepak Kudaravalli

  • SEM-BCS Short Dump while executing Manual Posting Task

    Hi SEM-BCS Colleagues,
    I am having a peculiar problem with relation to the settings for Manual Postings. I have three scenarios for which I have defined manual document types and tasks 1) Standardizing Entry (Data Collection) 2) Manual Document in IU for adjustment 3) COI Group level manual postings. I am just creating and not changing any settings for document field properties also. I have configured monthly consolidation frequency and period category and I am posting document type 1 in Local Currency and 2 and 3 in Group Currency since they are after currency translation.
    Have any of you faced similar problem and help me please?

    Hello,
    I am also getting short dump during data collection in BCS.
    we recently upgraded the system to SP20. Is it anyway related to upgrade.
    I also checked the MYSELF as a source system, but not found one.
    Could you please let me know how you have solved this issue.
    short dump:
    Runtime Errors         PERFORM_TOO_MANY_PARAMETERS
    Exception              CX_SY_DYN_CALL_PARAM_NOT_FOUND
    Date and Time          04.12.2009 05:21:11
    Short text
         Too many parameters specified with PERFORM.
    What happened?
         In a subroutine call, there were more parameters than in the
         routine definition.
         Error in the ABAP Application Program
         The current ABAP program "SAPLRSDRI" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
          not caught in
         procedure "RSDRI_CUBE_WRITE_PACKAGE_RFC" "(FUNCTION)", nor was it propagated by
          a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         A PERFORM was used to call the routine "CUBE_WRITE_PACKAGE" of the program
          "GPD1S8520HM8UV0U2XBDVPADF03".
         This routine contains 7 formal parameters, but the current call
         contains 10 actual parameters.

  • Short dump while executing Ztransaction

    Hi,
      I am doing module pool programming by desinging the screens, handling events and running it thru a Z-trnasaction.
      My first query is how do I debug a module pool prg.. so as to understand that the error/short dump is because of my code or due to some other reason ...
      My second query is that I am getting a short dump with "DIAG_RFC_EXCEPTION" ... I do have access to SM59 ... do I need to check for some other RFC propeties ??... Is this error related to Basis guys??? & the line where it is dumping is as follows :-
    Einzelbildverarbeitung Transaktionsvarianten/Batch-Input/CATT
       call function 'SYSTEM_SCREEN_INPUT'
            exporting
                 modul = p_repid.
    endform.                               " %_CTL_INPUT
    Thank You,
    SB

    Hi SB,
    One way to debug module pool(Pop-up) is like this :
          Many times we would like to start debugging from a Pop-up screen, but the editor doesn't allow us to do that.
    *Instead, we have to start debugging all the way from main screen.
    *Enclosed is a 3 line script would allow us to make our edits in a Pop-up.
    *Create a file with following code and save it as 'debugger.txt' in your local drive and drag and drop it (from Windows explorer) on to the Pop-up box and the debug mode will be on.
    FILE CONTENTSMany times we would like to start debugging from a Pop-up screen, but the editor doesn't allow us to do that. Instead, we have to start debugging all the way from main screen. Enclosed is a 3 line script would allow us to make our edits in a Pop-up. Create a file with following code and save it as 'debugger.txt' in your local drive and drag and drop it (from Windows explorer) on to the Pop-up box and the debug mode will be on!
    <b>Code: (File Contents)</b>
    [FUNCTION]
    Command=/H
    Title=Debugger
    Type=SystemCommand
    Hope this will help you to find out the error while debugging the pop up .
    Cheers
    Sunny

  • Short Dump while executing function module "IDOC_INPUT"

    Dear Friends,
    We are trying to execute the function module "IODC_INPUT" and getting a short dump.
    Basically the scnario is that we are trying to change an IDOC through transaction WE19 and then we execute the same by pressing tab "STANDARD INBOUND".
    But as soon as we press this button we get the short dump. whereas if I process the IDOC by pressing tab "Inbound Function Module" , there is no error and we are able to process the idoc successfully.
    Request you to please guide why this problem is there and what is the resolution for the same.
    Regards,
    Lalit Kabra

    Hi Nazeer,
    Thanks a lot for quick response.
    We are getting the dump with error ""Type "IDOC_DATA_CRYPTION" is unknown"". We just pressed the button STANDARD INBOUND and it gave us the error.
    Even when I execute this FM stand alone then just after pressing F8, it gives me Dump instead of the selction screen of the Function module.
    I tried running this FM on my IDES system and there I can see the selction screen and there is no dump.
    To me it seems that I need to do some settings so that this fm can be executed sucessfully.
    Request you to please help and guide me.
    Regards,
    Lalit Kabra

Maybe you are looking for

  • HP 5520 all in one printer: Problem installing software

    Nightmare trying to install software - have tried from CD and from web. Installation error Call to DriverPackageInstall returned error 1627 for package 'C\Program Files\HP\HP Photosmart 5520 series\Driver Store\Pipeline\hpvp109.inf' Any advice would

  • I can open a certain link in Internet Explorer and see all the information but when I open it in Firefox I get the HTML. Is there a setting I need to change in Firefox?

    I created HTML for a document and wanted to use it as HELP. When I open the index in Internet Explorer it takes me to the various topics and I can see everything I need to see in a nice format. HOWEVER, when I try to open it in Mozilla I get html cod

  • ZPOHISTORY

    HI, We are using ZPOHISTORY Report,in that results,Some of the data is missing.Like, for reversal documents its not showing the exact amount of documents and these reversal documents should have Negative sign,so that total value should match.But for

  • FM to Update infotype-0006 without ZIP Code

    Hi All, I am trying to create new entry in info type - 0006 (address) without using state and zip code.. I have tried with FM 'HR_INFOTYPE_OPERATION' . Using this I am able to save address without state but it is still giving zip code error is mandat

  • Weird scripts in corrupted RH9 project

    Hi! I'm having trouble with a small 75-topic project in RH9. I just upgraded it from RH7 last month. The application runs on XP, service pack 3. The project file is located on a desktop and has a short access path (c:\RH9Projects\). I have in all 4 s