Dump while executing class method whose exporting parameter  of type table

hi,
i am getting dump after executing a method in which i want to export an internal table which will hold all the states name along with its code on the basis of the country name which is my importing parameter.
for the above i am using importing parameter named as country of type too5u-land1 and the exporting parameter named as itab of type table and below is my code for the requirement.
method PROCESS.
  select BLAND BEZEI from T005U
         INTO TABLE ITAB WHERE
         LAND1 = COUNTRY.
endmethod.

Hi,
  Please check the below code
parameters country type land1.
*Refer the class which we are using like below
data: a type ref to ZCL_TX_SERVICE_01.
data itab type ycountry.
*ycountry is a table type defined in dictionary with fields BLAND and BEZEI
data wa like line of itab.
*If we are using instance method we need  to create the instance like below
create object a.
*In the method process define exporting parameter itab as type ycountry which is a table type already defined
CALL METHOD a->PROCESS
  EXPORTING
    COUNTRY = country
  IMPORTING
    ITAB    = itab.
loop at itab into wa.
write:/ wa-bland.
endloop.
Regards
Dande

Similar Messages

  • Exporting parameter of type table in Method of a Class

    Hi Experts,
    I want to pass an internal table from my method in ABAP class to a workflow.
    For thi spurpose i have cretaed a parameter of type table in the method.
    My problem is that i am not able to bind this to a workflow/task  container.
    I can see all the other parameters of the method in thw workflow while binding except for the parameter of type table ( i.e internal table ).
    Any idea ?
    Thanks,
    Radhika.

    Assuming that you are trying to export the internal table from class method to task conatiner.
    I have cretaed a Structure 'zemails' in se11
    Already you have created a Structure in the SE11 , why don't you just create one Table Type of ZEMAILS in SE11. Once you hvae created in DDIC then in the class signature declare the ltmails of type the tabale type that you create. and then in the task conatiner also try to declare the container element with the same name and same table type.
    In the class method declare the lt_mails as Exporting. save and actiavte. And one more thing if that element is not present in the Task conatiner then as soon as you try to open in the change mode and click on the binding button of the task it will prompt you asking whether you want to trnasfer the mssing elements if you clcik Yes then the same element which you have declared in the class will created with the same type. but make sure in the task conatiner you delcare the lt_mails as IMport export element.

  • Dump while executing the report in the background!!!

    Hi Experts,
    I have created one report which is calling the "HRASR_TEST_PROCESS" (HR form process) thru BDC.
    Its running fine while executing via SE38 (foreground) but getting dump while executing from the background with same variant.
    The dump is follows,
    Short Text
    Exception condition "CNTL_ERROR" raised.
    ERROR ANALYSIS
    A RAISE statement in the program "CL_GUI_CUSTOM_CONTAINER=======CP" raised the exception condition "CNTL_ERROR". Since the exception was not intercepted by a superior program, processing was terminated.
    Line        Source Code
    32         WHEN 1.
       33           RAISE CNTL_SYSTEM_ERROR.
       34         WHEN 2.
       35           RAISE CNTL_ERROR.
       36         WHEN 3.
       37           class cl_gui_cfw definition load.
       38           message id 'DC' type 'W' number cl_gui_cfw=>reason_no_init
       39             raising create_error.
       40         WHEN 4.
       41           RAISE LIFETIME_ERROR.
       42         WHEN 5.
       43           RAISE LIFETIME_DYNPRO_DYNPRO_LINK.
       44         WHEN OTHERS.
       45           RAISE CNTL_ERROR.
       46       ENDCASE.
       47     
       48       m_container_type = CONTAINER_TYPE_CUSTOM.
       49     
       50       CALL METHOD SET_VISIBLE
       51           EXPORTING
       52               VISIBLE = '1'
       53           EXCEPTIONS
       54               CNTL_SYSTEM_ERROR = 1
       55               CNTL_ERROR = 2.
       56     
       57       CASE SY-SUBRC.
       58         WHEN 0.
       59         WHEN 1.
       60           RAISE CNTL_SYSTEM_ERROR.
       61         WHEN 2.
    >>>>>           RAISE CNTL_ERROR.
       63         WHEN OTHERS.
       64           RAISE CNTL_ERROR.
       65       ENDCASE.
       66     
       67       m_name = container_name.
       68       call method set_window_property
       69            exporting property_id = property_name
       70                      value       = m_name
       71                      keep_cache  = 'X'
       72            exceptions others = 1.
       73       if sy-subrc ne 0.
       74         clear m_name.
       75         raise cntl_error.
       76       endif.
       77     
       78       CALL METHOD ME->REGISTER_CACHED_W_PROPERTY
       79         EXPORTING
       80           PROPERTY_ID             = property_height
       81         EXCEPTIONS
    Kindly let me know, what is the problem and how can i solve it.
    Thanks in advance.
    Regards,
    Harish

    Hello Zhou,
    indeed, as you mention the ALV grid, there are some workarounds in the system, but there is no global solution. For example, the function module REUSE_ALV_GRID_DISPLAY detects internally whether it is called in background mode, and in this case it forwards the call to REUSE_ALV_LIST_DISPLAY which is runnable in background mode, since it creates an ABAP list.
    But normally, when using objects of the control framework in your program, you are restricted to dialog mode.
    Kind regards,
    Rüdiger

  • Dump while Executing Hrast_dT (Design time of HCM Process and Forms)

    Hi All,
    I am getting Syntax Error Dump while Executing Hrast_dT tcode (Design time of HCM Process and Forms) and here with i have mentioned the source code also ist contained in standard class.
    *METHOD constructor.
      DATA:
        badi_context          TYPE REF TO lcl_badi_context.
      CALL METHOD super->constructor
        EXPORTING
          form_scenario         = form_scenario
          form_scenario_service = form_scenario_service.
      DATA:
        t5asrfscnsrv_wa TYPE t5asrfscnsrv.
      SELECT SINGLE * FROM t5asrfscnsrv INTO t5asrfscnsrv_wa WHERE form_scen_srv EQ form_scenari
      ASSERT sy-subrc EQ 0.
      ASSERT t5asrfscnsrv_wa-service_type = 'GENSRV'.
      fill_table_metadata( ).*
    i followed this link also..its not working for me..
    [Re: Assertion_Failed dump when accessing Design Time for Processes & Forms EP3]
    Regards,
    Parthi

    Hello Parthasarathi,
    Please, try to implement the note 1075650.

  • 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!

  • Dump While Executing ME21N, ME22N and ME23N

    Hi,
    Am getting the below Short Dump while executing ME21N, ME22N and ME23N.
    Runtime Errors         SYNTAX_ERROR
    Date and Time          08.07.2009 15:41:00
    |Short text                                                                               
    Syntax error in program "ME_PROCESS_PO_CUST============CP ".
    |What happened?                                                                               
    |    Error in the ABAP Application Program                                                                               
    |                                                                               
    |    The current ABAP program "CL_EX_ME_PROCESS_PO_CUST======CP" had to be                     
    |     terminated because it has                                                                               
    |    come across a statement that unfortunately cannot be executed.                                                  
    |                                                                               
    |    The following syntax error occurred in program                                                                             
    |     "ME_PROCESS_PO_CUST============CP " in include                                                                 
    |     "ME_PROCESS_PO_CUST============CM000 " in                                                                      
    |    line 14:                                                                               
    |    "The specified type cannot be converted into the target variables."                         
    |    " "                                                                               
    |    " "                                                                               
    |    " "                                                                               
    |                                                                               
    |    The include has been created and last changed by:                                           
    |    Created by: "SILABAP "                                                                      
    |    Last changed by: "SILABAP "                                                                 
    |    Error in the ABAP Application Program                                                        
    |                                                                               
    |    The current ABAP program "CL_EX_ME_PROCESS_PO_CUST======CP" had to be                     
    |     terminated because it has                                                                   
    |    come across a statement that unfortunately cannot be executed.                               
    |Error analysis                                                                               
    |    The following syntax error was found in the program                                          
    |     ME_PROCESS_PO_CUST============CP :                                                          
    |    "The specified type cannot be converted into the target variables."                          
    |    " "                                                                               
    |    " "                                                                               
    |    " "                                                                               
    |Trigger Location of Runtime Error                                                                
    |    Program                                 CL_EX_ME_PROCESS_PO_CUST======CP                     
    |    Include                                 CL_EX_ME_PROCESS_PO_CUST======CM001                  
    |    Row                                     1                                                    
    |    Module type                             (METHOD)                                             
    Module Name                             IF_EX_ME_PROCESS_PO_CUST~INITIALIZE
    |Source Code Extract                                                                               
    |Line |SourceCde                                                                               
    |>>>>>|method IF_EX_ME_PROCESS_PO_CUST~INITIALIZE.                                                
    |    2|  CLASS CL_EXIT_MASTER DEFINITION LOAD.                                                    
    3
    |    4|  DATA l_badi TYPE REF TO ME_PROCESS_PO_CUST.                                              
    5
    6
    7
    8
    9
    |   10|  TRY.                                                                               
    11
    |   12|    GET BADI l_badi                                                                        
    |   13|     CONTEXT me.                                                                           
    14
    |   15|    CALL BADI l_badi->INITIALIZE                                                           
    |   16|.                                                                               
    17
    18
    19
    |   20|    CATCH CX_BADI_NOT_IMPLEMENTED CX_BADI_INITIAL_REFERENCE.                               
    Please let me know is there any OSS note to resolve the Issue.
    Thanks,
    Subas

    Hi,
    when I try to do the same in my system SAP gives me an information message as follows:-
    Changes to transported Business Add-In definitions are incompatible
    Message no. ENHANCEMENT236
    Diagnosis
    This business add-in definition has already been transported. Subsequent changes could invalidate existing business add-in implementations.
    System Response
    The runtime behaviour is no longer predictable. Syntax errors or short dumps may occur.
    Procedure
    If possible, do not make these changes. Alternatively, create a new business add-in definition incorporating the changes and use it, along with the existing definition.
    It clearly indicates that the BADI definition should not be changed if active implementations already exists.
    I am really now not sure how to solve your issue.
    Try deactiviting the standard BADI implementation.
    Then again add the filter and then remove it.
    And then try activating the BADI implementation once again.
    Regards,
    Ankur Parab

  • Dump while executing FM based Gen extractor

    Hi,
    I am getting a dump while executing the FM based extractor in RSA3.
    below is the dumps error analysis-
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
         not caught in
        procedure "RSA3_GET_DATA_SIMPLE" "(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:
        The program "SAPLRSA3" contains the CALL FUNCTION statement.
        The name of the function module to be called is "ZZRSAX_BIW_GET_DATA_SIMPLE".
        but "ZZRSAX_BIW_GET_DATA_SIMPLE" cannot be found in its function group.
        Possible reasons:
        a) The function module "ZZRSAX_BIW_GET_DATA_SIMPLE" has not been activated.
         Therefore,
           it cannot be found at runtime.
        b) The Function Library contains an incorrect entry for
         "ZZRSAX_BIW_GET_DATA_SIMPLE".
        c) The function module contains no code, even FUNCTION ... ENDFUNCTION
           is missing.
    Pls tell me if u need the FM code or anything else...
    Thanks in advance,
    sandy,

    And this is the FM...which was written
    Pls tell me if i am missing anything?
    Example: DataSource for table SFLIGHT
      TABLES: vbak, vbap.
    Auxiliary Selection criteria structure
      DATA: L_S_SELECT TYPE SRSC_S_SELECT.
    Maximum number of lines for DB table
      STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
    counter
              S_COUNTER_DATAPAKID LIKE SY-TABIX,
    cursor
              S_CURSOR TYPE CURSOR.
    Select ranges
      RANGES: L_R_VBELN  FOR VBAK-VBELN,
              L_R_AUDAT  FOR VBAK-AUDAT,
              L_R_POSNR FOR VBAP-POSNR.
    Initialization mode (first call by SAPI) or data transfer mode
    (following calls) ?
      IF I_INITFLAG = SBIWA_C_FLAG_ON.
    Initialization: check input parameters
                    buffer input parameters
                    prepare data selection
    Check DataSource validity
        CASE I_DSOURCE.
          WHEN 'ZSALES_DS'.
          WHEN OTHERS.
            IF 1 = 2. MESSAGE E009(R3). ENDIF.
    this is a typical log call. Please write every error message like this
            LOG_WRITE 'E'                  "message type
                      'R3'                 "message class
                      '009'                "message number
                      I_DSOURCE   "message variable 1
                      ' '.                 "message variable 2
            RAISE ERROR_PASSED_TO_MESS_HANDLER.
        ENDCASE.
        APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
    Fill parameter buffer for data extraction calls
        S_S_IF-REQUNR    = I_REQUNR.
        S_S_IF-DSOURCE = I_DSOURCE.
        S_S_IF-MAXSIZE   = I_MAXSIZE.
    Fill field list table for an optimized select statement
    (in case that there is no 1:1 relation between InfoSource fields
    and database table fields this may be far from beeing trivial)
        APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
      ELSE.                 "Initialization mode or data extraction ?
    Data transfer: First Call      OPEN CURSOR + FETCH
                   Following Calls FETCH only
    First data package -> OPEN CURSOR
        IF S_COUNTER_DATAPAKID = 0.
    Fill range tables BW will only pass down simple selection criteria
    of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
          LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'VBELN'.
            MOVE-CORRESPONDING L_S_SELECT TO L_R_vbeln.
            APPEND L_R_vbeln.
          ENDLOOP.
          LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'POSNR'.
            MOVE-CORRESPONDING L_S_SELECT TO L_R_posnr.
            APPEND L_R_posnr.
          ENDLOOP.
    Determine number of database records to be read per FETCH statement
    from input parameter I_MAXSIZE. If there is a one to one relation
    between DataSource table lines and database entries, this is trivial.
    In other cases, it may be impossible and some estimated value has to
    be determined.
          OPEN CURSOR WITH HOLD S_CURSOR FOR
          SELECT vbakvbeln vbakaudat vbakaugru vbakkunnr vbakvkbur vbakawahr
                 vbakkvgr1 vbapvbeln vbapposnr vbapmatnr vbapkwmeng vbapvrkme
                 vbapnetwr vbapwaerk
                 FROM vbak INNER JOIN vbap ON vbakvbeln = vbapvbeln
                 WHERE vbak~vbeln IN L_R_VBELN AND
                       vbap~posnr IN L_R_posnr.
        ENDIF.                             "First data package ?
    Fetch records into interface table.
      named E_T_'Name of extract structure'.
        FETCH NEXT CURSOR S_CURSOR
                   APPENDING CORRESPONDING FIELDS
                   OF TABLE E_T_DATA
                   PACKAGE SIZE S_S_IF-MAXSIZE.
        IF SY-SUBRC <> 0.
          CLOSE CURSOR S_CURSOR.
          RAISE NO_MORE_DATA.
        ENDIF.
        S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
      ENDIF.              "Initialization mode or data extraction ?
    ENDFUNCTION.

  • 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....

  • Dump while executing SAP Script

    Hello,
    My program is throwing a dump while executing this script. Request you all to please help me in removing this.
    /E   MAIN_DATA
    /:    BOX FRAME 10 TW
    PA To,  ,,Invoice No. & Date,,  &JVBRK-VBELN&  &JVBRK-FKDAT&
    PA M/s  &JKNA1-NAME1(35)&,,Your P.O. No.,,  &JVBAK-BSTNK&
    /*           &JKNA1-NAME2(35)&,,Truck No.,,  &JLIKP-TRAID&
    PA         &JKNA1-NAME2(35)&,,Truck No.,,  &WRK_VEHNO&
    PA         &JKNA1-ORT01(20)&,,LR No.& Date,,  &WRK_LRNO&   &JJ_1IEXCDTL-EXDAT& 
    /*           &JKNA1-REGIO(20)&,,Net Qty.in kgs.,,  &JLIPS-NTGEW(10.3L)&
    PA         &JKNA1-REGIO(20)&,,Net Qty.in kgs.,,  &W_NETWT(12.3L)& KG
    PA         ,,Material,,  &JVBRP-ARKTX(30)&
    My Report has the following code:
    FORM write_to_layout_set.
      PERFORM write_layout_set USING 'MAIN' 'SET' 'BODY' 'MAIN'.
      PERFORM write_layout_set USING '' 'SET' 'BODY' 'LOGO'.
      PERFORM write_layout_set USING '' 'SET' 'BODY' 'HEADER2'.
      PERFORM write_layout_set USING 'HEADER' 'SET' 'BODY' 'TEST2'.
      PERFORM write_layout_set USING 'FOOTER' 'SET' 'BODY' 'FOOTER2'.
      PERFORM write_layout_set USING '' 'SET' 'BODY' 'SIGN'.
    ENDFORM.                               " WRITE_TO_LAYOUT_SET
    FORM write_layout_set USING wrk_element
                                wrk_function
                                wrk_type
                                wrk_window.
      CALL FUNCTION 'WRITE_FORM'
         EXPORTING
               element       =  wrk_element
               function      =  wrk_function
               type          =  wrk_type
              window         =  wrk_window
       IMPORTING
            PENDING_LINES =
           EXCEPTIONS
                element       = 1
                function      = 2
                type          = 3
                unopened      = 4
                unstarted     = 5
                window        = 6
                OTHERS        = 7.
    +
      IF sy-subrc NE 0.
        PERFORM protocol_update.
      ENDIF.
    +
    ENDFORM.                               " WRITE_LAYOUT_SET

    As per my first reply you have to change the perform
    PERFORM write_layout_set USING 'MAIN' 'SET' 'BODY' 'MAIN'.
    to
    PERFORM write_layout_set USING 'MAIN_DATA' 'SET' 'BODY' 'MAIN'.
    and now check and one more thing whether this main_data element is in main window or not just check.
    if it does not work then just change &W_NETWT(12.3L)&  to
    &W_NETWT& and check

  • ABAP dump while executing transaction *PC00_M99_CIPE*

    Hi,
    Getting ABAP dump while executing transaction PC00_M99_CIPE  ,hence cannot do payroll posting .
        Information on where terminated
        Termination occurred in the ABAP program "CL_HRFPM_CD_CLOSING_HANDLER===CP" -
         in "GET_FM_POS_CHECK_DATA".
        The main program was "RPCIPE00 ".
        In the source code you have the termination point in line 13
        of the (Include) program "CL_HRFPM_CD_CLOSING_HANDLER===CM00E".
    We have recently upgraded our patch level.
    SAP_OCS(SPAM/SAINT)          SAPKD70026            SAPKD70033
    SAP_ABA                                SAPKA70012            SAPKA70018
    SAP_BASIS                              SAPKB70012           SAPKB70018
    PI_BASIS                                 SAPKIPYJ7B            SAPKIPYJ7I
    SAP_BW                                  SAPKW70012           SAPKW70020
    SAP_AP                                   SAPKNA7008           SAPKNA7015
    SAP_APPL                                SAPKH60009           SAPKH60015
    SAP_HR                                  SAPKE60028            SAPKE60039
    EA-HR                                     SAPKGPHD07          SAPKGPHD26
    Kindly guide me.
    Regards,
    Rachel

    thanks for the quick response.
    By applying  note 1137655,problem got resoved.
    FORM CHECK_CMTNT_UPDATE_CLOSED
    Delta001
    Context Block
    FORM check_cmtnt_update_closed
               USING
                  u_key_date TYPE begda
               CHANGING
                  c_flg_cmtnt_closed.
    Delete Block
      DATA ls_encumb_iv TYPE t77hrfpm_encumb.
      DATA l_gsval TYPE t77s0-gsval.
      DATA ls_fm_pos_key TYPE hrfpm_fm_doc_pos-key_pos.
      DATA lx TYPE REF TO cx_hrfpm.
      STATICS so_closing_handler TYPE REF TO cl_hrfpm_cd_closing_handler.
      CLEAR c_flg_cmtnt_closed .
    *--- old switch from note??? active?
    *--- if so: use the old logic
      cl_hr_t77s0=>read_gsval(
        EXPORTING
          grpid       = 'HRFPM'
          semid       = 'CHKAC'
        IMPORTING
          returnvalue = l_gsval ).
      TRY.
          IF NOT l_gsval IS INITIAL .
            TRY.
                c_flg_cmtnt_closed = 'X'.
    Insert Block
      DATA: ls_encumb_iv TYPE t77hrfpm_encumb.
      STATICS:
          s_gsval TYPE t77s0-gsval,
          s_gsval_read TYPE flag.
      IF s_gsval_read IS INITIAL .
        SELECT SINGLE gsval
           FROM t77s0
          INTO s_gsval
          WHERE grpid = 'HRFPM'
            AND semid = 'CHKAC' .
        s_gsval_read = 'X'.
      ENDIF.
      CLEAR c_flg_cmtnt_closed .
      TRY.
          c_flg_cmtnt_closed = 'X'.
    Delta002
    Context Block
        CATCH
            cx_hrfpm_db_operation
            cx_hrfpm_ad_customizing .
    Delete Block
            ENDTRY.
          ELSE.
    *--- using closed period functionality of PBC
            IF so_closing_handler IS INITIAL .
              CREATE OBJECT so_closing_handler.
            ENDIF.
            IF so_closing_handler->consumption_in_closed_period(
                       i_key_date = u_key_date
                       is_fm_pos_key = ls_fm_pos_key )
                 IS INITIAL.
              c_flg_cmtnt_closed = 'X'.
            ENDIF.
          ENDIF.
        CATCH cx_hrfpm INTO lx.
        lx->raise_sy_message( ).
      ENDTRY.
    ENDFORM.                    "check_cmtnt_update_closed
    Insert Block
      ENDTRY.
    ENDFORM.                    "check_cmtnt_update_closed

  • 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 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.

  • Dump while Executing the Report HINUINFU

    Dear All
            I am getting Dump while executing the T.Code - HRPBSIN_IN_INFU (HINUINFU). As per my Configuration it should update the IT0267 and the IT0582. While debugging the We found out that its updating the IT0267 internally. But while reaching to IT0582 its reflecting on the feature 40CEA and the T549D.
    here we are having the Telephone Reimbursement for this i copied the Tax code SEXM to ZTEL and assigned to my wage type
    I also maintaied this Subtype to the feature 40CEA.
    Checked also the IT0582 and its subtype time constraint.
    Still the the DUMP persisisting. Please provide the solutions if any of you come across with the same situation.
    Thanks & Regards
    Srikanth Reddy

    Hi
         Issue has been resoved internally. Return value to feature set as HINUOSD0 to MOLGA. hence closing the thread
    Regards
    Srikanth Reddy

  • Getting a dump while executing the standard report BUSCHDOC

    Hi,
    I am getting a dump while executing the standard report BUSCHDOC.
    I am specifying the following values:-
    Application Object : BUPA
    Business partner:<some business partner>
    Changed on: <some date>
    Changed by:<some userid>
    Below are the dump details
    Short text
        CREATE DATA: The specified type "BUSSRCH_401BUPAT" is no valid data type.
    Any suggestions to avoid the dump are welcome.
    Thanks,
    Ravindra

    Hi Ravindra,
    Can you execute report BUP_BUSSRCHGF_REPAIR and try again ?
    Also, go to transaction BUS10, click the button Geneate Selection. On next screen, give Application object = BUPA, Max no. of tables per view = 1.
    Regards,
    Rishu.

  • 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.

Maybe you are looking for

  • Exchange did notPush. MobileMe do Push

    Hello, I have set an account with MobileMe (home Email) and the Email are pushed into my Iphone I have set exchange on my Iphone (work email) but email are not pushed? I have to sync manually Any clue? Exchange will never push or is this a settings i

  • Long-running transactions and the performance penalty

    If I change the orch or scope Transaction Type to "Long Running" and do not create any other transaction scopes inside, I'm getting this warning: warning X4018: Performance Warning: marking service '***' as a longrunning transaction is not necessary

  • Message regarding Metadata for this photo has been changed

    We recently transferred from PC to Mac. We now get, over each image, an icon that when you hover over it the message says,  "The metadata for this photo has been changed by both Lightroom and another application. Should Lightroom import settings from

  • Yosemite won't boot past login.

    I installed Yosemite a few days ago. The first day it ran fine, but the second day my computer started running extremely slowly, freezing up completely after shorter and shorter timeframes, and shutting down randomly without warning. As of last night

  • No tools menu!

    Hi there, just got a brand new Nokia N79 and I can't find the tools menu!  When I push the menu button (left of green phone), it brings up a 'stack' of cards view with Internet, Contacts, Music, Photos, TV & Video, Games, Maps but know tools option.