Getting run time errors while executing the copied SAP programs

Hi folks,
i want to copy an sap program.after coping i need to change some coding there.then i have to create a new transaction for that.
i am just copying the sap program RQEEAL10(transaction-QA32) to Z_RQEEAL10. it has 4 include  programs.i am copying them to z programs like
RQ00MF10 copied to z_RQ00MF10
RQALVF14 copied to z_RQALVF14
RQALVF16 copied to z_RQALVF16
RQALVTOP copied to z_RQALVTOP.
now i am executing that program Z_RQEEAL10.but i am getting run time errors as given below.
<b>runtime error---</b>
The termination occurred in the ABAP program "Z_RQEEAL10" in           
"SELECT_FIELDS_MANIP2_F16".                                           
The main program was "Z_RQEEAL10 ".                                                                               
The termination occurred in line 257 of the source code of the (Include)
program "RQALVF16"                                                    
of the source code of program "RQALVF16" (when calling the editor 2570).
--Error in ABAP statement when processing an internal table.  
--When changing or deleting one or more lines of the internal table         
"\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS" or when inserting in the table   
"\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS", 0 was used as                  
the line index. An index less than or equal to zero is not                
allowed.                                                                               
The error can occur when using the following options:                     
1. "INDEX idx" for specifying the line number in the table                
"\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS"                                 
   where you want to change, insert or delete.                            
2. "FROM idx" for specifying the start index when deleting a line         
   area from or inserting a line area into the table                      
"\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS".                                
3. "TO idx" for specifying the end index when deleting a line             
   area from or inserting a line area into the table                      
"\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS".                                                                               
When the program terminated, the table had 2 lines.                       
these r the runtime errors what i am getting.where is the problem?i have activated all interface & includes.plz advice.
Thanks & regards

Hi Madhu,
I will give you one more check point where you have to give your concentration while copying the standard programs....
Call Customer-Function (Function Exists) if any in the Program when copied will not get executed. Instead you need to call the FM Directly.
one more is also here
You are likely to have some problems with the text-elements and translation that may have been maintained for the original report.
~~Guduri

Similar Messages

  • Run-time error while executing alv grid report

    Hi everyone
    I m trying to run a alv grid report it is giving a run time error while executing the statement CALL METHOD V_ALV->SET_TOOLBAR_INTERACTIVE.
    Actually i added 2 buttons in the toolbar.after that when i execute the report i m getting errors.
    <b>Error Analysis</b>
    An exception occurred that is explained in detail below.                     
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not    
    caught in                                                                   
    procedure "TOOLBAR_MENUS_INIT" "(METHOD)", 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:                                             
    You attempted to use a 'NULL' object reference (points to 'nothing')         
    access a component (variable: "ME->M_CL_MENU_BUTTON_VARIANT").               
    An object reference must point to an object (an instance of a class)         
    before it can be used to access components.                                  
    Either the reference was never set or it was set to 'NULL' using the         
    CLEAR statement.

    Hi Dinesh,
    Seems you have not initialised ( Instantiated in OO ) the object and / or the parent container.
    Check if you have create object for both the parent as well as the alv object.
    So when you instatntiate the object of ALV you pass the object ( instantiated before hand ) in the parent container position.
    Also you would have to register the events to the object using method. Then only the buttons will finction.
    eg :
    IF G_CUSTOM_CONTAINER IS INITIAL.
        CREATE OBJECT CUSTOM_CONTAINER_1
               EXPORTING CONTAINER_NAME = CONTAINER_1.
        CREATE OBJECT GRID1
               EXPORTING I_PARENT = CUSTOM_CONTAINER_1.
        CALL METHOD ALV_GRID1->SET_TABLE_FOR_FIRST_DISPLAY
             EXPORTING I_STRUCTURE_NAME = 'VBAK
             CHANGING  IT_OUTTAB        = IT_VBAK.
    Reward points if useful.

  • ABAP Run time Error whle executing the Balance sheet report in FGI0

    Hi,
    I am getting the below ABAP Run time error while executing the Balance Sheet report in FGI0.It was working before but now it is giving the error.Kindly help me in solving this.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          06/12/2009 15:17:17
    Short text
         The current application triggered a termination with a short dump.
    What happened?
         The current application program detected a situation which really
         should not occur. Therefore, a termination with a short dump was
         triggered on purpose by the key word MESSAGE (type X).
    Error analysis
         Short text of error message:
         RAISE RKD_CONDITION_READ       (internal error)
         Long text of error message:
          Diagnosis
              The program was terminated because a situation occurred which
              should not have arisen.
          Procedure
              Analyze the situation and contact SAP.
         Technical information about the message:
         Message class....... "KH"
         Number.............. 299
         Variable 1.......... "RKD_CONDITION_READ"
         Variable 2.......... " "
         Variable 3.......... " "
         Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLKYPR
        Include                                 LKYPRU31
        Row                                     36
        Module type                             (FUNCTION)
        Module Name                             RKD_CONDITION_READ
    Thanks
    Supriya

    Hello,
    Please refer SAP
    Note 971535 - dump when deleting characteristic with hierarchy
    Regards,
    Ravi

  • Getting run time error while calling smartform

    hi,
    i am getting run time error of "maintain output device in your master data" while calling smart form.
    p_output_options-xsfcmode = 'X' .
      p_output_options-xsf = space .
      p_output_options-xdfcmode = 'X' .
      p_output_options-xdf = space .
      p_output_options-tddest = 'LP01'.
      p_output_options-tdnewid = 'X'.
      p_output_options-tddelete = SPACE.
      p_control_parameters-no_dialog = 'X' .
      p_control_parameters-getotf = 'X' .
      p_control_parameters-DEVICE = 'PRINTER'.

    Hi Neha
    Your program looks out for the default printer configured against your user (Check SU01 : Constant tab ). You dont seem to have maintained it properly as a result of which you get this message. You will have to configure your printer device to overcome this error.
    Choose menu: System -> User Profile -> Own data.
    On the Defaults tab, give LOCL code for the output device.
    You can also check the output device setting in transaction SPAD.
    Regards,
    Uday

  • Run time error while closing the CRM Order using BAPI

    Hi Experts,
    Need your invaluable suggestions here.Apologies for the lengthy mail, intention is to give clear idea of the issue.
    I am facing an issue while closing the CRM orders. According to our business process, when an issue is solved we will keep the order in resolved status only. We will not directly close the order from the CRM tool, instead we have created a custom program for the same purpose.
    For the custom program we will give input as the order number and execute it, this will close the order.
    Here close the order means assigning it to Close status as well assign the reason code.
    We have created some reason codes for closed status.
    So when the program is run the Order moves from resolved status to closed status along with reason code.
    But of late we are facing some problems with this program, it is giving run time error for some CRM orders.
    Run time error message : The ABAP/4 Open SQL array insert results in duplicate database records.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "CRM_SERVICE_OS_UPD_OST_DU" "(FUNCTION)", nor was it propagated by a RAISING clause.
    Please find my code which have used in the custom program
    Closing the resolved SOs in the system
        CALL FUNCTION 'CRM_STATUS_CHANGE_EXTERN_OW'
            EXPORTING
              objnr                     = iv_guid
              user_status          = lc_status_closed
           EXCEPTIONS
             object_not_found          = 1
             status_inconsistent       = 2
             status_not_allowed       = 3
             OTHERS                        = 4.
        IF sy-subrc <> 0.
          WRITE :  'Error at maintaining status'.
        ENDIF.
    Set reason code
    build lt_subject
        ls_subject-ref_guid = iv_guid.
        ls_subject-katalogart = 'A2'.
        ls_subject-codegruppe = 'ZR000003'.
        ls_subject-code       = 'ZR33'.                      " Reason code
        ls_subject-mode       = 'A'.
        APPEND ls_subject TO lt_subject.
    build lt_ossset
        ls_osset-ref_guid        = iv_guid.
        ls_osset-subject_profile = 'ZREASON03'.
        ls_osset-profile_type    = 'G'.
        ls_osset-subject         = lt_subject.
        APPEND ls_osset TO lt_osset.
    build lt_service_os
        ls_service_os-ref_guid  = iv_guid.
        ls_service_os-ref_kind  = 'A'.
        ls_service_os-osset     = lt_osset.
        APPEND ls_service_os TO lt_service_os.
    build lt_input_fields
        REFRESH: lt_input_fields, lt_field_names.
        CLEAR  : ls_input_fields, ls_field_names.
        ls_field_names-fieldname    = 'CODE'.
        APPEND ls_field_names TO lt_field_names.
        ls_field_names-fieldname    = 'CODEGRUPPE'.
        APPEND ls_field_names TO lt_field_names.
        ls_field_names-fieldname    = 'KATALOGART'.
        APPEND ls_field_names TO lt_field_names.
        ls_field_names-fieldname    = 'SERVICE_PROFILE'.
        APPEND ls_field_names TO lt_field_names.
        ls_input_fields-ref_guid    = iv_guid.
        ls_input_fields-ref_kind    = 'A'.
        ls_input_fields-objectname  = 'SERVICE_OS'.
        ls_input_fields-field_names = lt_field_names.
        APPEND ls_input_fields TO lt_input_fields.
         CALL FUNCTION 'CRM_ORDER_MAINTAIN'
          EXPORTING
            it_service_os     = lt_service_os
          CHANGING
            ct_input_fields   = lt_input_fields
          EXCEPTIONS
            error_occurred    = 1
            document_locked   = 2
            no_change_allowed = 3
            no_authority      = 4
            OTHERS            = 5.
        IF sy-subrc <> 0.
          WRITE :  'Error at maintaining reason'.
        ENDIF.
        CALL FUNCTION 'CRM_ORDER_SAVE'
          EXPORTING
            it_objects_to_save   = lt_header_guid
            iv_update_task_local = lv_update_task_local
          IMPORTING
            et_saved_objects     = lt_saved_objects
          EXCEPTIONS
            document_not_saved   = 1
            OTHERS               = 2.
        IF sy-subrc <> 0.
          WRITE : 'Error at saving'.
        ELSE.
          WRITE : 'Successfully Closed'.
          COMMIT WORK AND WAIT.
        ENDIF.
    Run time error is coming at COMMIT WORK AND WAIT statement.
    Please let me know any corrections are required in the above program.
    When I analyzed the run time error I have found that it trying to insert the record in CRMD_SRV_OSSET for that CRM order, but already one record is present in the table for the same CRM order number.
    For most of the CRM orders there is no entry in this table so they are closing successfully but for a few orders for which there is an entry we are getting the above run time error.
    There is nothing wrong with the orders which have an entry already in the table CRMD_SRV_OSSET, I need to close these kind of orders with out run time error.
    Kindly provide your feedback.

    Hi Dinakar,
    You posted this in APO PPDS forum. This question should go to PP forum where someone could answer it.
    Please close this thread and open a new thread in PP forum so that you could get help quickly from the relevant experts.
    Regards - Pawan

  • Run time error while executing Project Info system Reports

    Hi,
    I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
    Thank you for your cooperation.
    Regards,
    Rakesh Pradhan

    Hi,
    I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
    Thank you for your cooperation.
    Regards,
    Rakesh Pradhan

  • Run time Error while executing Project Info system Reports (CN41/CN41N)

    Hi,
    I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
    Thank you for your cooperation.
    Regards,
    Rakesh Pradhan

    Hi,
    I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
    Thank you for your cooperation.
    Regards,
    Rakesh Pradhan

  • Run time error while executing KP06

    Hello All,
    A run time error is being returned when I execute the tcode KP06. After entering all required field such as cost elements, cost center / CCgroup, then I pressed period screen / overview screen ... and it went to abap dump ...
    FYI, I have upgraded to 4.7 to ECC system.
    Regards,
    Bharath.
    Moderator message: please do more research before asking, use ST22, search for SAP notes, check your custom enhancements.
    Edited by: Thomas Zloch on Aug 22, 2011 9:58 AM

    Ok. Look at the dump in ST22 and solve your problem.

  • Run time Error while executing project infosystem reports (CN41/41N)

    Hi,
    I would like to inform while running project infosystems reports (CN41/41N / cns41 etc), it is taking long time & most of the time run time errors are coming. I observed due to more objects in projects, run time error is coming. Request you to suggest to fix the issue.
    Thank you for your cooperation.
    Regards,
    Rakesh Pradhan

    Hi Rakesh,
    The memory which can be managed by the logical database is approx.       
    100 MB. You can use the following rule of thumb to calculate the         
    allocated memory of your selection:                                                                               
    [(  sum of projectdefinitions + sum of WBS elements + sum of networks and orders ) * 1 KB  + ( sum of activities     ) * 4 KB ] *2,5 = memory consumption                                                                               
    Further objects - as relationships, capacities, ... will increase        
    the memory consumption. (see note 107605) 
    You can find out the number of objects bein used using the "Test selection scope" (CTRL+F12) button in CN41                                                                               
    Other recommendations are:                                                                               
    1) Check the profile (parameter "rdisp/PG_MAXFS") with your Basis        
       colleague and adjust upwards (Note 133909)                                                                               
    2) Select a smaller range of objects by using status schema              
       or more dynamic selections. Please review SAP Note 206264.                                                                               
    3) Please review also 107605, which gives you further information 
       concerning the selection in Project Information System.                                                                               
    Hope this helps!
    Regards
    Martina
    Message was edited by:
            Martina Modolell

  • Getting run time error when executing stanard SAP transaction

    Hi experts,
        I am trying to run the standard SAP report transaction S_ALR_87013557. but it is giving the run time error "LOAD_PROGRAM_NOT_FOUND". i also check the program name that appears in the short dump with SE38. it gives the message that no program exist.
      but when i try to run other S_ALR_ trasactions, they are running correctly.
      So can just help me in this regards.

    Check if this program GPA8PD2X83M8PML7SBUU3COEFIK exist in your system.
    if yes then see which transaction it is attached.
    if that transaction is executing properly, then functional person can tell if that's the report they are looking for.
    if no u can execute this prog from se38 & check. if that works, then you can create z transaction & attach that program.
    This will be workaround, ideally you should raise OSS ticket. SAP may release new Note .

  • Run time error while activating the Transfer Rules

    Hi,
    Error when activating Transfer rules for Infosource :
    0FI_GL_1 -
    (General ledger: Transaction figures)
    Run time error : ASSERTION FAILED
    Transfer rules traffic light is in Green. But when i am trying to activate the Transfer rules, its giving Run time error.
    Thanks,
    Kishore

    Hi,
    As mentioned in the note 939383 , either Import Support Package 08 for SAP NetWeaver 2004s BI (BI Patch08 or SAPKW70008) into your BI system or do correction instructions given in the note.
    It is always better to import the latest patches avialble in service market to avoid this type of problems.
    Also see tha note 1010672 amd check whether it is applicable to your problem.
    With rgds,
    Anil Kumar Sharma .P
    Message was edited by:
            Anil Kumar Sharma

  • Run Time error while activating the cube 0pp_c03

    Hi All,
    I encountered this error while activating the info cube 0pp_c03
      An exception occurred which is explained in detail below.
      The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
      and
      therefore caused a runtime error.
      The reason for the exception is:
      No text available for this exception
    Regards
    Rohit

    Hi,
    Please check in ST22 for any relevant short dump. the error message is not of much help in anlyzing the problem
    or
    Perform the consistency test with 'RSRV' -->All Elementary Tests --> Master Data --> 'Compare Number Range and Maximum SID for the characteristic 0REQUID'. and correct the error
    Regards,
    Marasa.

  • Run time error while executing Rule- RSTRAM- 301

    Hi
    I am getting following error whilr  trying to laod data from flatfile. This process worked well till last month but now its failing with the below error.  Looks like  one columns which is foramatted to number without decimal when loaded is changin to text format
    as you can see it says 3 cannot be interpreted as number. Not sure why any advice.
    Diagnosis                                                                               
    An error occurred while executing a transformation rule:                                                                               
    The exact error message is:                                                                               
    The argument ''3' cannot be interpreted as a number                                                                               
    The error was triggered at the following point in the program:                                                                               
    GPD3C9RN4D74RNEWHKNBERS6QCR 583                                                                               
    System Response                                                                               
    Processing the data record has been terminated.                                                                               
    Procedure                                                                               
    The following additional information is included in the higher-level
    Thanks
    Siva

    Thanks for quick reposne. However Flat file does not have '3 . In flat file I formatted as number and it shows just as 3 but somehow it is getting converted to text when loading as '3.  No sure why and how.
    Siva

  • Getting run time error when accessing the file from frontend server using F4.....?

    Category               ABAP Programming Error
    Runtime Errors         CONVT_NO_NUMBER
    Except.                CX_SY_CONVERSION_NO_NUMBER
    ABAP Program           ZMM_MIGO_GOODS_ISSUE
    Application Component  Not assigned
    Date and Time          26.05.2014 14:28:30
    Short Text
         "C:\Users\SAP\Desktop\MIGO\MIGO.xlsx" cannot be interpreted as a number
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "ZMM_MIGO_GOODS_ISSUE" had to be terminated because
          it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception has occurred which is explained in more detail below. The
         exception is assigned to class 'CX_SY_CONVERSION_NO_NUMBER' and was not caught
          in procedure
         "%_SEL_SCREEN_P_FNAME_V" "(FORM)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated this

    HI CHIRUI,
    I have changed and tried but still i a getting the same thing..
    otherwise please check this i am using some class method i am not getting short dump,but excel file is not getting uploaded.
    REPORT ZMM_MIGO_GOODS_ISSUE NO STANDARD PAGE HEADING.
    DATA : BEGIN OF IT_DATA OCCURS 0,
             ID(10),
             BLDAT(10),                             " Document Date
             BUDAT(10),                             " Posting Date
             REF_DOC_NO(16),                        " Material Slip No
             DEL_NOTE(16),                          " delivery note
             MATNR TYPE MSEG-MATNR,                 " Material Number
             ERFMG(13) TYPE C,                      " Quantity
             BWART TYPE RM07M-BWARTWA,              " Movement Type
             SOBKZ(1),                              " Special Stock
             WERKS TYPE RM07M-WERKS,                " Plant
             LGORT TYPE RM07M-LGORT,                " Storage Location
             PS_POSID TYPE PS_POSID,                " WBS Element
             COST_CENTER TYPE KOSTL,                " cost center
             ORDER TYPE AUFNR,                      " order number
             SERNR TYPE RIPW0-SERNR,                " Serial Number
            END OF IT_DATA,
            BEGIN OF IT_HEAD OCCURS 0,
              ID(10),
              BLDAT(10),                            " Document Date
              BUDAT(10),                            " Posting Date
              REF_DOC_NO(16),                       " Reference document number
              "HEADER_TXT(25),                       " Header Text
              BWART TYPE RM07M-BWARTWA,             " Movement Type
            END OF IT_HEAD,
            BEGIN OF IT_ITEM OCCURS 0,
              ID(10),
              "ID1(10),
              WERKS TYPE RM07M-WERKS,               " Plant
              LGORT TYPE RM07M-LGORT,               " Storage Location
              VAL_TYPE TYPE BWTAR_D,
              MATNR TYPE MSEG-MATNR,                " Material Number
              ERFMG(13) TYPE C,                     " Quantity
              CHARG TYPE MSEG-CHARG,                " Batch
              BWTAR TYPE BWTAR_D,
              PS_POSID TYPE PS_POSID,                 " WBS Element
              ERFME TYPE MSEG-ERFME,                  " Unit
              COST_CENTER TYPE KOSTL,                " cost center
              ORDER TYPE AUFNR,                      " order number
              CUSTOMER TYPE EKUNN,                    " Account Number of Customer
              SERNR TYPE RIPW0-SERNR,                 " Serial Number
              AMOUNT_LC TYPE BAPI_EXBWR,
              SOBKZ(1),
            END OF IT_ITEM,
              HEADER   LIKE BAPI2017_GM_HEAD_01,
              CODE     LIKE BAPI2017_GM_CODE,
              ITEMS    LIKE BAPI2017_GM_ITEM_CREATE OCCURS 0 WITH HEADER LINE,
              SERIAL   LIKE BAPI2017_GM_SERIALNUMBER OCCURS 0 WITH HEADER LINE,
              RETURN   LIKE BAPI2017_GM_HEAD_RET,
              RET      LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE,
              TESTRUN  LIKE BAPI2017_GM_GEN-TESTRUN,
              IT_TAB   TYPE FILETABLE,
              GD_SUBRC TYPE I,
              L_FILE   TYPE RLGRAP-FILENAME,
              IT_RAW   TYPE TRUXS_T_TEXT_DATA,
              COUNT(2) TYPE N,
              TEXT_C(30).
    DATA: DATA     LIKE TABLE OF IT_ITEM WITH HEADER LINE.
    DATA: IT_TEMP  LIKE TABLE OF IT_ITEM WITH HEADER LINE.
    DATA: IT_TEMP1 LIKE TABLE OF IT_ITEM WITH HEADER LINE.
    DATA: IT_ITEM1 LIKE TABLE OF IT_ITEM WITH HEADER LINE.
    SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
    PARAMETERS : P_FILE TYPE RLGRAP-FILENAME.
    *             p_test AS CHECKBOX.
    SELECTION-SCREEN: END OF BLOCK B1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
       CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
         EXPORTING
           WINDOW_TITLE = 'SELECT FILE'
         CHANGING
           FILE_TABLE   = IT_TAB
           RC           = GD_SUBRC.
       READ TABLE IT_TAB INTO P_FILE INDEX 1.
    START-OF-SELECTION.
       PERFORM GET_EXCEL_DATA.
       PERFORM GET_HEADER_ITEM.
       PERFORM UPDATE_DATA.
    *&      Form  GET_EXCEL_DATA
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM GET_EXCEL_DATA .
       CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
           INPUT  = P_FILE
         IMPORTING
           OUTPUT = L_FILE.
       CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
         EXPORTING
           I_LINE_HEADER        = 'X'
           I_TAB_RAW_DATA       = IT_RAW
           I_FILENAME           = L_FILE
         TABLES
           I_TAB_CONVERTED_DATA = IT_DATA
         EXCEPTIONS
           CONVERSION_FAILED    = 1
           OTHERS               = 2.
       IF SY-SUBRC <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
    ENDFORM. " GET_EXCEL_DATA
    *&      Form  GET_HEADER_ITEM
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM GET_HEADER_ITEM .
       DATA : FLAG(1).
       LOOP AT IT_DATA.
         CLEAR FLAG.
         IF IT_DATA-ID IS NOT INITIAL.
           AT NEW ID.
             FLAG = 'X'.
           ENDAT.
         ENDIF.
         IF FLAG = 'X'.
           MOVE-CORRESPONDING IT_DATA TO IT_HEAD.
           APPEND IT_HEAD.
         ENDIF.
         MOVE-CORRESPONDING IT_DATA TO IT_ITEM.
         APPEND IT_ITEM.
       ENDLOOP.
       DATA[] = IT_ITEM[].
       IT_TEMP[] = IT_ITEM[].
       IT_TEMP1[] = IT_ITEM[].
    ENDFORM. " GET_HEADER_ITEM
    *&      Form  UPDATE_DATA
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM UPDATE_DATA .
       DATA : COUNT1(10),
              L_QTY TYPE I,
              DAT(10).
       CONCATENATE SY-DATUM+6(2) '.' SY-DATUM+4(2) '.' SY-DATUM(4) INTO DAT.
       LOOP AT IT_HEAD.
         ON CHANGE OF IT_HEAD-ID.
           CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
             EXPORTING
               DATE_EXTERNAL       = IT_HEAD-BUDAT
               ACCEPT_INITIAL_DATE = 'X'
             IMPORTING
               DATE_INTERNAL       = HEADER-PSTNG_DATE.
           IF SY-SUBRC <> 0.
             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                     WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
           ENDIF.
           CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
             EXPORTING
               DATE_EXTERNAL       = IT_HEAD-BLDAT
               ACCEPT_INITIAL_DATE = 'X'
             IMPORTING
               DATE_INTERNAL       = HEADER-DOC_DATE.
           IF SY-SUBRC <> 0.
             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
           ENDIF.
           MOVE : '2'                TO HEADER-VER_GR_GI_SLIP,
                  'X'                TO HEADER-VER_GR_GI_SLIPX.
    *      IF r1 EQ 'X'.
           MOVE '05' TO CODE-GM_CODE.
           HEADER-REF_DOC_NO = IT_HEAD-REF_DOC_NO.
           "HEADER-HEADER_TXT = IT_HEAD-HEADER_TXT.
    *      ELSEIF r2 EQ 'X'.
    *        MOVE '04' TO code-gm_code.
    *      ELSEIF r3 EQ 'X'.
    *        MOVE '04' TO code-gm_code.
    *      ENDIF.
    *      IF p_test = 'X'.
    *        MOVE 'X' TO testrun.
    *      ENDIF.
         ENDON.
         IT_ITEM1[] = IT_ITEM[].
    *delete it_item[] where werks = '' and id = it_head-id.
         DELETE ADJACENT DUPLICATES FROM IT_ITEM COMPARING ID MATNR.
         LOOP AT IT_ITEM WHERE ID = IT_HEAD-ID.
    *      ON CHANGE OF it_item-id1.
           COUNT1 = COUNT1 + 1.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = IT_ITEM-MATNR
             IMPORTING
               OUTPUT = ITEMS-MATERIAL.
           MOVE : IT_ITEM-WERKS TO ITEMS-PLANT,
                  IT_ITEM-LGORT TO ITEMS-STGE_LOC,
    *             it_item-lgort1 TO items-move_stloc,
                  IT_ITEM-CHARG TO ITEMS-BATCH,
    *            IT_ITEM-VAL_TYPE TO ITEMS-VAL_TYPE,
                  'FRESH' TO ITEMS-VAL_TYPE,
                  IT_HEAD-BWART TO ITEMS-MOVE_TYPE,
                  IT_ITEM-SOBKZ TO ITEMS-SPEC_STOCK,
                  IT_ITEM-ERFMG TO ITEMS-ENTRY_QNT,
                  IT_ITEM-ERFMG TO ITEMS-ENTRY_QNT,
    *            it_item-erfme TO items-entry_uom,
    *            it_item-sgtxt TO items-item_text,
    *            it_item-exbwr TO items-amount_lc,
                  IT_ITEM-PS_POSID TO ITEMS-WBS_ELEM,
                  IT_ITEM-PS_POSID TO ITEMS-VAL_WBS_ELEM,
                  "IT_ITEM-CUSTOMER TO ITEMS-CUSTOMER,
                  IT_ITEM-ERFMG TO L_QTY,
                  IT_ITEM-AMOUNT_LC TO ITEMS-AMOUNT_LC,
                  IT_ITEM-COST_CENTER TO ITEMS-COSTCENTER,
                  IT_ITEM-ORDER TO ITEMS-ORDERID.
    *             items-SPEC_MVMT = 'R'.
           CALL FUNCTION 'CONVERSION_EXIT_ABPSN_INPUT'
             EXPORTING
               INPUT  = ITEMS-WBS_ELEM
             IMPORTING
               OUTPUT = ITEMS-WBS_ELEM.
           CALL FUNCTION 'CONVERSION_EXIT_ABPSN_INPUT'
             EXPORTING
               INPUT  = ITEMS-VAL_WBS_ELEM
             IMPORTING
               OUTPUT = ITEMS-VAL_WBS_ELEM.
    *      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    *        EXPORTING
    *          input  = it_item-lifnr
    *        IMPORTING
    *          output = items-vendor.
           APPEND ITEMS.
    *      ENDON.
         ENDLOOP.
         DELETE ADJACENT DUPLICATES FROM IT_TEMP COMPARING ID MATNR.
         DELETE IT_TEMP1 WHERE ID <> IT_HEAD-ID.
         DELETE IT_TEMP WHERE ID <> IT_HEAD-ID.
         DATA: MAT_ITM TYPE MBLPO,
               SERNP TYPE SERAIL.
         MAT_ITM = '0001'.
         LOOP AT IT_TEMP.
           SELECT SINGLE SERNP FROM MARC INTO SERNP WHERE MATNR = IT_TEMP-MATNR.
           IF SERNP IS NOT INITIAL.
             LOOP AT IT_TEMP1 WHERE ID = IT_TEMP-ID AND MATNR = IT_TEMP-MATNR.
    *    MOVE : it_item1-id TO serial-matdoc_itm,
    *     MOVE : mat_itm TO serial-matdoc_itm,
               SERIAL-MATDOC_ITM = MAT_ITM .
               SERIAL-SERIALNO   = IT_TEMP1-SERNR.
               APPEND SERIAL.
               CLEAR IT_ITEM1.
             ENDLOOP.
             MAT_ITM = MAT_ITM + 1.
           ENDIF.
           CLEAR IT_TEMP.
         ENDLOOP.
         CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
           EXPORTING
             GOODSMVT_HEADER       = HEADER
             GOODSMVT_CODE         = CODE
             TESTRUN               = TESTRUN
    *       GOODSMVT_REF_EWM      =
           IMPORTING
             GOODSMVT_HEADRET      = RETURN
    *       MATERIALDOCUMENT      =
    *       MATDOCUMENTYEAR       =
           TABLES
             GOODSMVT_ITEM         = ITEMS
             GOODSMVT_SERIALNUMBER = SERIAL
             RETURN                = RET
    *       GOODSMVT_SERV_PART_DATA =
    *       EXTENSIONIN           =
         CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
           EXPORTING
             WAIT = 'X'
    *   IMPORTING
    *       RETURN        =
         IF NOT RETURN IS INITIAL.
           WRITE :/ 'Material Document Number Generated: ' ,RETURN-MAT_DOC,RETURN-DOC_YEAR.
         ELSE.
           LOOP AT RET.
             WRITE : RET-TYPE,    RET-MESSAGE.
    *      log-index = sy-index.
    *      log-matnr = header-material.
    *      log-message = ret1-message.
    *      APPEND log.
           ENDLOOP.
         ENDIF.
         REFRESH : ITEMS,RET.
         CLEAR : HEADER,RETURN.
         CLEAR: TESTRUN  ,
                RETURN,
                ITEMS[],
                SERIAL[],
                RET[],
                HEADER,
                IT_TEMP[] ,
                IT_TEMP1[].
         IT_TEMP[] = DATA[].
         IT_TEMP1[] = DATA[].
       ENDLOOP.
    ENDFORM. " UPDATE_DATA
    Regards,
    Suresh bheema

  • Java run time error while executing JavaFX code

    Hi
    I copied the code from [http://java.sun.com/javafx/1/tutorials/ui/overview/UIControls.fx|http://java.sun.com/javafx/1/tutorials/ui/overview/UIControls.fx] while
    reading in [http://java.sun.com/javafx/1/tutorials/ui/overview/#controls|http://java.sun.com/javafx/1/tutorials/ui/overview/#controls] tutorial and paste it to my
    netbeans editor but i got following error.
    init:
    deps-jar:
    compile:
    jar:
    standard-run:
    # An unexpected error has been detected by Java Runtime Environment:
    #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d94513f, pid=5152, tid=5996
    # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode, sharing)
    # Problematic frame:
    # V  [jvm.dll+0xd513f]
    # An error report file with more information is saved as hs_err_pid5152.log
    # If you would like to submit a bug report, please visit:
    #   http://java.sun.com/webapps/bugreport/crash.jsp
    BUILD FAILED (total time: 18 seconds)can anyone tell whether its netbeans fault or javaFX. I am using netbeans 6.5.1 on windows vista. I have added following plugin in netbeans for javaFX
    *JavaFX Kit
    *JavaFX SDK for Windows
    is anyone also getting this error for this code and have solution for this.

    You are correct the crash is causing due to ToggleButton and ProgessBar. the code is correct because i tried it on eclipse 3.4 and it worked fine.This is definitely netbeans error. because its giving error even if u try to execute javafx code with just one ToggleButton or ProgressBar. I tried the following simple code in netbeans 6.5
    import javafx.stage.Stage;
    import javafx.scene.Scene;
    import javafx.scene.control.ToggleButton;
    import javafx.scene.control.ProgressBar;
    var toggle=ToggleButton {
                    translateX:50
                    translateY:50
                    text: "First"
                    width:100
                    height:20
    var progress= ProgressBar {
            progress: bind ProgressBar.computeProgress( 100, 30 )
    Stage {
        title : "Toggle Button Test"
        scene: Scene {
            width: 200
            height: 200
            content: [ toggle
    } When i just added toggle button to contents then button showed up in window but on clicking it window disappear and compiler gave crash error on the other hand when i added just progess bar it just throws the error.The same code is running fine on eclipse
    Is there any workaround in netbeans for this if its a bug and if not what should i do to correct it.

Maybe you are looking for

  • Copy and Pasting Text in Photoshop

    Everytime I've tried pasting text from a Word document or website, all the words jumble on top of each other into one line. Why can't they separate into separate lines like they were originally formatted to look like? Thanks, Mason

  • Crystal Report 8 download

    Hi, I can download Crystal Report 8 or 8.5? And I can use it with my VB6 program in Windos7? Thanks,

  • While using Build App installer, how does one include drivers for hardware

    I have a LabView vi and I would like to create an application to be installed on a different computer that also requires a PCI-6503 digital IO card for the purpose. While using Build Application to create the installer, is there a way I can include t

  • Installing Adobe Reader without getPlus+ 1

    Hi As getPlus+ 1 is licensable is there a way I can make sure that it is not installed when Adobe Reader updates? Our SAM tool is saying that the software is remaining as installed even though the update has completed. This has made us non-compliant

  • Regarding BOM explosion

    Hi all, In CS11, CS12 and CS13, why the system does not display prices of the materials (both standard or moving). It is there in layout.  But it is showing blank. Is some setting is required ? Regards, YR