Runtime Error in Standard Include

Hi,
After upgrading from SAP 4.7 E to ECC 6.0, we have facing few problem in execution of Reports..
Main problem is that, it called Standard INCLUDES..
Error:-
Short text
    Format error with IMPORT.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "ZHINCANN1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
But, this program called a standard INCLUDE HINPAYMACRO ... that dump goes in it.
What's the problem...plz clear..
Thanks

Hi,
Error Message is:....
Short text
    Format error with IMPORT.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "ZHINCANN1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_IMPORT_FORMAT_ERROR', was not
     caught in procedure "IMP-RESULT-CLSTR" "(FORM)", 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:
When attempting to IMPORT the object "EPF", there was a format error.
Unable to read an IMPORT dataset.
The dataset may have been processed using SQL and is
thus no longer readable for the IMPORT.
How to correct the error
    Determine which actions resulted in the destruction of the
    dataset.
    The exception must either be prevented, caught within proedure
    "IMP-RESULT-CLSTR" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
This is complete error message...
Now plz. tell...

Similar Messages

  • Runtime error in Standard program "SAPMV45A"

    Hi Expert,
    i am getting problem in BDC , While creating the (sales order) VAO1 ,dump is occurs in standard program SAPMV45A. Because of in FM "Pricing_Dialog_Tabstrips" is incorrect and TAXI_TABSTRIP_C and TAXI_TABSTRIP_ITEM" specified here is a different field type.This is standard program we can not change field type. Kindly provide any OSS notes for this or any other solution.
    STANDARD PROGAM - SAPMV45A
    INCLUDE PROGRAM     - MV45AF0F_FCODE_PKO4
    ERROR  - Runtime Error CALL_FUNCTION_CONFLICT_TYPE has occurred
    Kindly help me, Its very uigent
    Thanks & Regards
    Md.MahaboobKhan

    Hi Archana ,
    Check is there any Inactive Versions in ur Systems ?
    useful tcodes are SPAU /SPDD for tables
    Regards
    prabhu

  • Syntax error in standard include RKEB090F in ECC6

    Hi,
    I have one issue with this include program RKEB090F. This program is being used in one of the custom program while checking this program we are getting syntax error field P_USEDB is unknown.
    When I compared 4.7 and ECC 6 version, the code contains in 4.7 version is
          FORM INITIALIZATION_EXIT                                      *
    FORM INITIALIZATION_EXIT.
    ENDFORM.
    but in ECC 6 the code contains
          FORM INITIALIZATION_EXIT                                      *
    FORM INITIALIZATION_EXIT.
       if rkb1d-smode = '7'.
         CALL FUNCTION 'AS_DATASOURCE_INIT'
           EXPORTING
             I_REPORT                   = 'KE30'
             I_REPORTTYPE               = 'TR'
           IMPORTING
             E_USE_DATABASE             = P_USEDB
             E_USE_ARCHIVE              = P_USEAR
             E_USE_INFOSYS              = P_USEAS
             E_ARCHOBJ                  = P_OBJECT
             ET_ARCH_SEL                = SO_FILES[].
         G_RKB2A-OBJECT = P_OBJECT.
         G_RKB2A-USEDB = P_USEDB.
         G_RKB2A-USEAR = P_USEAR.
         G_RKB2A-USEAS = P_USEAS.
         G_RKB2A-SO_FILES = SO_FILES[].
         PERFORM HANDLE_DATASOURCE USING 'EX'.
       endif.
    ENDFORM.
    due to this code I am getting the syntax errors. How can we know how this code is added.
    Please let me know if you get any inputs.
    Regards,
    Jyothi CH.

    Hi Guys,
    I am having the same syntax error with this include RKEB090F and the Field P_USERB, but instead the program is a SAP Program. I have been trying to archive a table and I keep getting this error for different G* programs. I regenerate one, the other one gives error. I tried regenerating all of them and I still got this error.
    Error in the ABAP Application Program
    The current ABAP program "SAPLKYP4_UC" had to be terminated because it h
    come across a statement that unfortunately cannot be executed
    The following syntax error occurred in program "GPC6ZZ9KJ35AEXCXNZFQDJG3
    in include "RKEB090F " in
    line 17:
    "Field "P_USEDB" is unknown. It is neither in one of the specified tabl"
    "es nor defined by a "DATA" statement. ."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    PLEASE HELP
    --Thanks in Advance,
    Fiyaz

  • Standard Runtime error with no SAP notes in OSS

    Hi All,
    Am getting a runtime error in standard sap functionality.
    I serched in market place for solution.
    I will be thankful for suggesting any other approach solution for standard runtime error?
    Thanks.
    Moderator message: please do not open multiple threads for the same or similar issue.
    Edited by: Thomas Zloch on Dec 12, 2011 6:31 PM

    Hi,
    I tried undoing note implemented.
    many dependent nots were inplemented along with note.
    Kindly guide how these notes can be unimplemented.
    Thanks.

  • Runtime Error in SM36 IMPORT_OBJECT_DESTROYED

    Hello,
    When i call up Tx : SM36 and choose Standard Jobs a runtime error is occurring "  IMPORT_OBJECT_DESTROYED".
    The short dump mentions as :
    Short text                                                                                       
        The IMPORT dataset has been destroyed.                                                       
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPLSEU_COMPONENT" had to be terminated because it                 
        has                                                                                         
        come across a statement that unfortunately cannot be executed.                               
    Error analysis                                                                                   
        Unable to import the dataset because it has an unexpected                                    
        format. It was                                                                               
        destroyed as a result of direct manipulation of the                                          
        IMPORT/EXPORT data by other means (for instance, explicit deletion                           
        of parts of the dataset using SQL instead of DELETE FROM DATABASE).                          
        In this case, the records in the dataset do not appear in the                                
        expected order, which is 0,1,2,3...                                                          
        (sequence counter in field SRTF2).                                                           
        The next record expected here is number 1,                                                   
        but number 0 appears.                                                                        
    Trigger Location of Runtime Error                                                                
        Program                                 SAPLSEU_COMPONENT                                    
        Include                                 LSEU_COMPONENTU01                                    
        Row                                     41                                                   
        Module type                             (FUNCTION)                                           
        Module Name                             RS_COMPONENT_VIEW                                    
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
       11
    *"  TABLES                                                                                 
       12
    *"      NODETAB STRUCTURE  SNODETEXT                                                       
       13
       14
       15
      DATA: subrc LIKE sy-subrc.                                                               
       16
      DATA: l_delete TYPE i.                                                                   
       17
      DATA: date LIKE sy-datum.                                                                
       18
       19
      CLEAR sy-subrc.                                                                          
       20
      date = sy-datum.                                                                         
       21
      REFRESH nodetab. CLEAR nodetab.                                                          
       22
      G_IGNORE_SFW_SWITCHES = IGNORE_SFW_SWITCHES.                                             
       23
       24
      if REFRESH ne SPACE.                                                                     
       25
        G_REFRESH_ALL = REFRESH_ALL.                                                           
       26
      endif.                                                                                   
       27
       28
      IF object_type = 'FUNC'.                                                                 
       29
        object_type = 'FUGR'.                                                                  
       30
      ENDIF.                                                                                   
       31
      IF object_type = space.                                                                  
       32
        object_type = 'APPL'.                                                                  
       33
      ENDIF.                                                                                   
       34
      apid-langu = language.                                                                   
       35
      apid-type  = object_type.                                                                
       36
       37
      IF refresh IS INITIAL.                                                                   
       38
    *   get table "nodetab" of all object lists                                                
       39
    *   of the desired type "object_type":                                                     
       40
        CATCH SYSTEM-EXCEPTIONS conne_import_wrong_comp_leng = 1.  "note 1553389               
    >>>>>
          IMPORT date nodetab FROM DATABASE dwtree(ap) ID apid                                 
       42
            ACCEPTING PADDING.                                                                 
       43
        ENDCATCH.                                                                              
       44
        subrc = sy-subrc.                                                                      
       45
      ENDIF.                                                                                   
       46
       47
      IF subrc NE 0 OR refresh = 'X'.                                                          
       48
        IF object_type = 'APPL' OR                                                             
       49
           object_type = 'DEVC'.                                                               
       50
          CASE object_type.                                                                    
       51
            WHEN 'APPL'.                                                                       
       52
              PERFORM get_components TABLES nodetab.                                           
       53
            WHEN 'DEVC'.                                                                       
       54
              PERFORM get_devc_view TABLES nodetab.                                            
       55
          ENDCASE.                                                                             
       56
          IF without_tree_setting IS INITIAL.                                                  
       57
            CALL FUNCTION 'RS_TREE_CONSTRUCT'                                                  
       58
              TABLES                                                                           
       59
                nodetab = nodetab                                                              
       60
              EXCEPTIONS                  
    I would appreciatte any help from you guys!
    Thanks in advance.
    Thales.

    wrong forum. this is not a bw/bi issue. ask your basis team to take a look.
    BR,
    M

  • WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR

    hi to all experts,
    whenever i try to delete a particular sale order im getting a runtime error
    stating that
    Short text
        Screen: Illegal message
    What happened?
        The current screen processing action was terminated since a situat
        occurred where the application could not continue.
        This is probably due to an error in the ABAP program or in the cur
        screen.
    Error analysis
        The program attempted to issue a " " message during "Exit Command" processing.
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    Trigger Location of Runtime Error
        Program                                 SAPMV45A
        Include                                 MV45AFZZ
        Row                                     370
        Module type                             (FORM)
        Module Name                             USEREXIT_SAVE_DOCUMENT
    SourceCde
                  message e001(zm) WITH text-335 ltab-kunnr text-334.
                else.
                  if ktab-jkunnr <> ltab-kunnr.
                    ktab-jkunnr = ltab-kunnr.
                    jobsitecode = ltab-kunnr.
                    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                    EXPORTING
                      input  = jobsitecode
                      IMPORTING
                      output = jobsitecode.
                    SELECT SINGLE * FROM kna1 WHERE kunnr = jobsitecode.
                    IF sy-subrc = 0.
                      ktab-jname1 = kna1-name1.
                      ktab-jstras = kna1-stras.
                    ENDIF.
                    chg_flg = 'X'.
                  endif.
                endif.
              else.
                message e001(zm) WITH text-336.
    * Validation for relationship between Sold-to Party and Ship-to Party
    *          if ktab-ckunnr+0(4) NE ktab-jkunnr+0(4).
    *            message e001(zm) WITH text-335 ktab-jkunnr text-337 ktab-ckunnr.
    *          endif.
              custcode1 = ktab-ckunnr.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = custcode1
                IMPORTING
                  output = custcode1.
              jobsitecode1 = ktab-jkunnr.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = jobsitecode1
                IMPORTING
                  output = jobsitecode1.
              SELECT SINGLE * FROM knvp
              WHERE kunnr = custcode1
                AND vkorg = vbak-vkorg
                AND vtweg = vbak-vtweg
                AND spart = vbak-spart
                AND parvw = 'WE'
    Error analysis
        The program attempted to issue a " " message during "Exit Command"
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    Trigger Location of Runtime Error
        Program                                 SAPMV45A
        Include                                 MV45AFZZ
        Row                                     370
        Module type                             (FORM)
        Module Name                             USEREXIT_SAVE_DOCUMENT

    Hi,
    Seems there is some problem with the user exit USEREXIT_SAVE_DOCUMENT..
    Put a breakpoint and see.
    Regards,
    Nagaraj

  • Runtime error while activating LO Datasource in Source System

    Hi Gurus,
    I have followed the below steps to activate the SD related LO extractor in ECC
    1. RSA5 --> Select all the 2LIS_11,12&13 data source and activate
    2. LBWE --> Choose the 2LIS_11,12&13 data source and activate.
    Upon execution of the second step , the system return me the following runtime error
    Runtime Errors         DDIC_TYPE_INCONSISTENCY
    Date and Time          07.07.2011 10:14:29
    Short text
         Inconsistency in the Dictionary for the structure "MCQALSB".
    What happened?
         Error in the SAP kernel.
         The current ABAP "SAPLMCEX" program had to be terminated because the
         ABAP processor detected an internal system error.
    Error analysis
         There is an internal system error.
         eliminated with ABAP/4.
    Trigger Location of Runtime Error
         Program                                 SAPLMCEX
         Include                                 LMCEX$04
         Row                                     26
    With this error i cant proceed to activate any of the LO data source
    Please help
    Thanks in advance

    The table MCQALSB need to be activated in SE11 and LBWE works fine

  • Error in Standard Program for Purchase Order

    Hello Everyone,
    I am getting an ABAP Dump Error while Displaying & Printing Purchase Order using TCODE : ME9F & ME23N.
    We have applied new Patches.
    for Logistics it is 26 & ABAP it is 58.
    I am getting Error in standard INCLUDE
    Program : LMEDRUCKF1K at line 64.
    The Error is :- "Field "ENJPREVIEW" is unknown. It is neither in one of the specified tables nor defined by a "DATA" statement."
    Declaration for "ENJPREVIEW" is also available in
    include LMEDRUCKTOP. still it gives an error.
    These lines of code is included by SAP note 855263.
    Before applying these Patches it was working properly, but now it gives an error.
    Please , Can anyone give solution for this.
    Regard's
    Archana.

    Hi Archana ,
    Check is there any Inactive Versions in ur Systems ?
    useful tcodes are SPAU /SPDD for tables
    Regards
    prabhu

  • Runtime error while executing ALV

    Hi all,
    I have implemented an ALV in OOPS concept and whenevr I am executing it I am getting a runtime error as GET WA NOT ASSIGNED
    Error analysis:
    You attempted to access an unassigned field symbol
    (data segment 32821).
    This error may occur if
    - You address a typed field symbol before it has been set with
       ASSIGN
    - You address a field symbol that pointed to the line of an
       internal table that was deleted
    - You address a field symbol that was previously reset using
       UNASSIGN or that pointed to a local field that no
       longer exists
    - You address a global function interface, although the
       respective function module is not active - that is, is
       not in the list of active calls. The list of active calls
       can be taken from this short dump.
    Trigger Location of Runtime Error
        Program                                 SAPLSLVC
        Include                                 LSLVCF36
        Row                                     3.231
        Module type                             (FORM)
        Module Name                             FILL_DATA_TABLE
    3201                               alv_style_align_center_top.
    3202         endif.
    3203
    3204         append ls_lvc_data to ct_lvc_data.
    3205       endif.
    3206
    3207 ************************************
    3208 * Column per Fieldcat Entry
    3209 ************************************
    3210       loop at it_fcat_local assigning <ls_fcat>.
    3211         clear: ls_lvc_data-href_hndl,
    3212                ls_lvc_data-drdn_hndl,
    3213                ls_lvc_data-style,
    3214                ls_lvc_data-style2,
    3215                ls_lvc_data-style3,
    3216                ls_lvc_data-style4,
    3217                ls_lvc_data-maxlen.
    3218
    3219         clear: lt_color_lvc, lt_color_slis.
    3220
    3221         add 1 to ls_lvc_data-col_pos.
    3222
    3223         if not <ls_fcat>-indx_field is initial.
    3224           assign component <ls_fcat>-indx_field
    3225                            of structure <ls_data> to <l_field_value>.
    3226         else.
    3227           assign component <ls_fcat>-fieldname
    3228                            of structure <ls_data> to <l_field_value>.
    3229         endif.
    3230
    >>>>         macro_cell_data_get
    3232           <ls_fcat>
    3233           <ls_data>
    3234           <l_field_value>
    3235           ls_lvc_data-value.
    3236
    3237 *>>> new API
    3238         if ir_salv_adapter is bound.
    3239           clear ls_lvc_data-style.
    3240
    3241 * color
    3242           if g_gui_type ne 1.
    3243             if <ls_fcat>-key eq abap_true.
    3244               ls_lvc_data-style = alv_style_color_int_key.
    3245             elseif l_style_color is initial
    3246                   and ( <ls_fcat>-emphasize is initial or
    3247                         <ls_fcat>-emphasize = '$' ).
    3248               if <ls_stin>-counter is initial.
    3249                 ls_lvc_data-style = alv_style_color_normal.
    3250               else.
    Please help me to sort out this issue

    FORM s_build_fldctlg .
      v_repid = sy-repid.
      DATA lw_fldctlg TYPE lvc_s_fcat.
      REFRESH i_fldctlg[].
      v_cpos = 0.
    * Column 1
      lw_fldctlg-col_pos = v_cpos.
      lw_fldctlg-row_pos = c_1.
      lw_fldctlg-ref_table = 'I_OUTPUT'.
      lw_fldctlg-fieldname = c_unlpt.
      lw_fldctlg-coltext = 'Unloading Point'.         "Unloading Point
      APPEND lw_fldctlg TO i_fldctlg.
      CLEAR  lw_fldctlg.
    * Column 2
      v_cpos = v_cpos + 1.
      lw_fldctlg-col_pos = v_cpos.
      lw_fldctlg-row_pos = c_1.
      lw_fldctlg-ref_table = 'I_OUTPUT'.
      lw_fldctlg-fieldname = c_vdrloc.       "Vendor Location
      lw_fldctlg-coltext = text-003.
      APPEND lw_fldctlg TO i_fldctlg.
      CLEAR  lw_fldctlg.
    * Column 3
      v_cpos = v_cpos + 1.
      lw_fldctlg-col_pos = v_cpos.
      lw_fldctlg-row_pos = c_1.
      lw_fldctlg-ref_table = 'I_OUTPUT'.
      lw_fldctlg-fieldname = c_nopkgs.       "No of packages
      lw_fldctlg-coltext = text-004.
      APPEND lw_fldctlg TO i_fldctlg.
      CLEAR  lw_fldctlg.
    * Column 4
      v_cpos = v_cpos + 1.
      lw_fldctlg-col_pos = v_cpos.
      lw_fldctlg-row_pos = c_1.
      lw_fldctlg-ref_table = 'I_OUTPUT'.
      lw_fldctlg-fieldname = c_delnote.     "Delivery Note
      lw_fldctlg-coltext = text-005.
      APPEND lw_fldctlg TO i_fldctlg.
      CLEAR  lw_fldctlg.
    * Column 5
      v_cpos = v_cpos + 1.
      lw_fldctlg-col_pos = v_cpos.
      lw_fldctlg-row_pos = c_1.
      lw_fldctlg-ref_table = 'I_OUTPUT'.
      lw_fldctlg-fieldname = c_reason.      "Reason
      lw_fldctlg-coltext = text-006.
      APPEND lw_fldctlg TO i_fldctlg.
      CLEAR  lw_fldctlg.
    * Column 6
      v_cpos = v_cpos + 1.
      lw_fldctlg-col_pos = v_cpos.
      lw_fldctlg-row_pos = c_1.
      lw_fldctlg-ref_table = 'I_OUTPUT'.
      lw_fldctlg-fieldname = c_status.
      lw_fldctlg-coltext = text-007.
      APPEND lw_fldctlg TO i_fldctlg.
      CLEAR  lw_fldctlg.
    ENDFORM.                    " S_BUILD_FLDCTLG
    This is my code.
    When i execute it without any values in my final table the ALV is getting displayed.
    But when I put some data in the final table I am getting this error

  • Runtime error in excise tax

    hi
    i am getting runtime error while doing googs receipt with tax code(without tax not getting error).please see this error.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          27.08.2008 20:32:45
    Short dump has not been completely stored (too big)
    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:
    Balance in transaction currency
    Long text of error message:
    Diagnosis
    A balance has occurred in transaction currency 'INR' with the
    following details:
    Exchange rate '00', amount '             8.00-' and currency key
    'INR'.
    The data in the transaction currency were transferred from the
    calling application.
    System Response
    Your data cannot be processed in FI.
    Procedure
    The error is probably in the calling application.
    Technical information about the message:
    Message class....... "F5"
    Number.............. 702
    Variable 1.......... 00
    Variable 2.......... " 8.00-"
    Variable 3.......... "INR"
    Variable 4.......... " "
    Trigger Location of Runtime Error
    Program                                 SAPLMBWL
    Include                                 LMBWLU21
    Row                                     59
    Module type                             (FUNCTION)
    Module Name                             MB_POST_GOODS_MOVEMENT
    Source Code Extract
    Line
    SourceCde
    29
       when a goods movement for an inbound or outbound delivery is posted
    30
       directly from VL31N/ VL01N, XBLNR is not yet known when we call
    31
       CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
    32
       BKPF as well. There is no other way to forward XBLNR to FI as not
    33
       every document is posted by MB_CREATE -> a new function module in
    34
       MBWL for transferring the information, called by FI, meant to load
    35
       the complete function group for all MBxx postings when this isn't
    36
       required (Performance). Would be the better way to transport the
    37
       information after switching off MBxx in later release.
    38
       corresponding IMPORT ... FROM MEMORY ... can be found in
    39
       AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
    40
    l_mem_id = 'MKPF-XBLNR'.                                   " 641365
    41
    EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
    42
    ENDIF.
    43
    IF xmkpf-xabln IS INITIAL.                               "note 434093
    44
    CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
    45
    ENDIF.                                                   "note 434093
    46
    47
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
    48
    49
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
    50
    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
    51
    EXCEPTIONS
    52
    error_message = 4.
    53
    As soon as we have started to put things into UPDATE TASK, we must
    54
    ensure that errors definitely terminate the transaction.
    55
    MESSAGE A is not sufficient because it can be catched from
    56
    external callers which COMMIT WORK afterwards, resulting in
    57
    incomplete updates. Read note 385830 for the full story.
    58
    IF NOT sy-subrc IS INITIAL.
    >>>>>
    MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
    60
    sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    61
        MESSAGE A263.
    62
    ENDIF.
    63
    Optische Archivierung
    64
    Spaete Erfassung mit Barcode
    65
    Redesign of barcode handling -> note 780365
    66
    PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
    67
    xmkpf-mjahr
    68
    barcode.
    69
    70
    MOVE-CORRESPONDING xmkpf TO emkpf.
    71
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    72
    EXCEPTIONS
    73
    error_message = 4.
    74
    MOVE-CORRESPONDING xmkpf TO emkpf.
    75
    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
    76
    EXCEPTIONS
    77
    error_message = 4.
    78
    IF NOT sy-subrc IS INITIAL.

    Hi,
    Please check the following notes
    Note 1242773 - Getting short dump when doing GR for combined requisitions
    Note 1047059 - Run time error in migo/Goods receipt
    Regards,
    Jigar

  • Runtime error in Adobe forms

    Hi,
    I am getting a run time error when i create ADOBE form and try to save. I am using SAP GUI 7.10 and ADOBE livecycle version 7.1. I did tried with ADOBE livecycle version 8.0 and getting same problem.
    NOTE:  This is the first ADOBE form i am trying to create in company.
    Below are the dump details ...Please let me know if any of you  have faced similar problem....Thanks
    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:
        Control Framework : Error processing control
        Long text of error message:
         Diagnosis
             An error occurred when the system tried to process the commands
             from the Automation Queue on the presentation server.
             There are several possible reasons for this:
             - The installation of the SAP GUI on the presentation server is
             faulty or obsolete.
             - There is an error in the application program
             - There is an error in the SAPGUI or an integrated control
         Procedure
             1. Make sure that you have imported the appropriate Support
             Package, the current kernel, and GUI patch for the release of your
             system
             2. Check whether the error occurs locally on one or a few PCs, or
             generally on all PCs. Note whether the error only occurs for some
             users, for example because of a specific Customizing setting.
             If it only occurs locally, this suggests an installation problem
             with the PC. Check the installation; if necessary, reinstall the
             software. In the dump, search for the SY-MSGLI field, since it may
             point to the cause of the error.
             3. Activate the Automation Trace (in accordance with SAP Note
             158985).
             4.Start the transaction and continue until the screen immediately
             before the dump.
             5. From the System -> Utilities menu, choose Autom. Queue,
             Synchronous Processing.
             The status bar of the GUI displays the text:
                "Automation synchron flush mode on"
             6. If you now proceed with the application, the short dump will
             display the ABAP call that caused the error; the Automation Trace
             will contain the error on the presentation server.
             7. If necessary, load the short dump and trace files on to
             sapservX, so that SAP can analyze them.
        Technical information about the message:
        Message class....... "CNDP"
        Number.............. 006
        Variable 1.......... " "
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLOLEA
        Include                                 LOLEAU02
        Row                                     29
        Module type                             (FUNCTION)
        Module Name                             AC_SYSTEM_FLUSH
    Source Code Extract
    Line  SourceCde
        1 FUNCTION AC_SYSTEM_FLUSH .
        2 *"----
        3 ""Lokale Schnittstelle:
        4 *"  IMPORTING
        5 *"     VALUE(CALLED_BY_SYSTEM) TYPE  C OPTIONAL
        6 *"  EXCEPTIONS
        7 *"      CNTL_SYSTEM_ERROR
        8 *"      CNTL_ERROR
        9 *"----
       10   data: sysubrc like sy-subrc.
       11
       12   CALL FUNCTION 'AC_FLUSH_CALL'
       13        EXPORTING
       14             SYSTEM_FLUSH = 'X'
       15             CALLED_BY_SYSTEM = CALLED_BY_SYSTEM
       16        IMPORTING
       17             MESSAGE_NR   = sysubrc
       18             MESSAGE_TEXT = SY-MSGLI.
       19
    20   sy-subrc = sysubrc.
    21
    22   CASE SY-SUBRC.
    23     WHEN 0.
    24     WHEN 1.
    25 *     system_error
    26       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.
    27     WHEN 2.
    28 *     method_call_error
    >>       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
    30     WHEN 3.
    31 *     property_set_error
    32       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
    33     WHEN 4.
    34 *     property_get_error
    35       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
    36     WHEN OTHERS.
    37       RAISE CNTL_ERROR.
    38   ENDCASE.
    39
    40 ENDFUNCTION.

    Hi Chandra,
    you can try following.
    Before saving PDF form, put external breakpoint in FM
    AC_FLUSH_CALL_INTERNAL.
    Save PDF Form, i guess it should go to this FM. Check which exception is setting sy-subrc = 2.
    (There are different checks in this FM for checking ActiveX, javabeen support etc).
    Hope this will help.
    Although, I never encountered the error you mentioned
    Regards,
    Mohaiyuddin

  • Runtime error in transaction ME31L

    Hi Experts,
    I am facing the problem with tranasaction code ME31L ,its showing the runtime error..
    here i am writting the  whole error discription which occurs at runtime.
      Short text
        Dynpro does not exist
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLXM06" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        The system attempted to use dynpro 0201 in program "SAPLXM06".
        This dynpro does not exist.
    Trigger Location of Runtime Error
        Program                                 SAPLXM06
        Include                                 MM06EO0C_CUSTSCR1_HEAD_SET_DAT
        Row                                     10
        Module type                             (FUNCTION)
        Module Name                             EXIT_SAPLEINM_013
    Source Code Extract
    Line  SourceCde
         1 ----
         2 *       MODULE CUSTSCR1_HEAD_SET_DATA OUTPUT                          *
         3 ----
         4 *       ........                                                      *
         5 ----
         6 MODULE CUSTSCR1_HEAD_SET_DATA OUTPUT.
         7
         8   PERFORM CUSTSCR1_HEAD_SET_DATA_PBO using fc_call.
         9
    >>>>> ENDMODULE.

    Hi,
    This means that the exit is not implemented yet. Infact what you are seeing is a warning message(ZX...).
    Is your system recently upgraded? Wrong OSS note implementation is also a possibility.
    Just debug and see at what point you are getting the error. Also did you check the program whether it has the required screen or not? If not available then you can raise an OSS note to SAP if you are not able to find any.
    Thanks,
    Vinod.

  • Runtime Error - DBIF_RSQL_INVALID_RSQL - Too many OPEN CURSOR

    When I try to train a Decision Tree Model via an APD process in RSANWB, I get a runtime error when my model is configured with too many parameter fields or too many leaves (with 2 leaves it works, with more it fails).
    By searching SAP Notes I see that there are many references to this kind of runtime errors. But no note on occurences of it in RSANWB / RSDMWB .
    Any information on this anyone?
    Claudio Ciardelli
    Runtime Errors         DBIF_RSQL_INVALID_RSQL
    Date and Time          29.07.2005 16:19:21
    |ShrtText                                                                                |
    |    Error in RSQL module of database interface.                                                   |
    |What happened?                                                                                |
    |    Error in ABAP application program.                                                            |
    |                                                                                |
    |    The current ABAP program "SAPLRS_DME_DECISION_TREE_PRED" had to be terminated                 |
    |     because one of the                                                                           |
    |    statements could not be executed.                                                             |
    |                                                                                |
    |    This is probably due to an error in the ABAP program.                                         |
    |                                                                                |
    |Error analysis                                                                                |
    |    The system attempted to open a cursor for a SELECT or OPEN CURSOR                             |
    |    statement but all 16 cursors were already in use.                                             |
    |    The statement that failed accesses table "/BIC/0CDT000030 ".                                  |
    |    The erroneous statement accesses table "/BIC/0CDT000030 ".                                    |
    |Trigger Location of Runtime Error                                                                 |
    |    Program                                 SAPLRS_DME_DECISION_TREE_PRED                         |
    |    Include                                 LRS_DME_DECISION_TREE_PREDU06                         |
    |    Row                                     103                                                   |
    |    Module type                             (FUNCTION)                                            |
    |    Module Name                             RS_DME_DTP_EVALUATE                                   |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                |
    |   73|* Prepare for Data evaluation                                                               |
    |   74|  CATCH SYSTEM-EXCEPTIONS OTHERS = 15.                                                      |
    |   75|    CREATE DATA ref TYPE (i_enum_dbtab).                                                    |
    |   76|    ASSIGN ref->* TO <fs_wkarea>.                                                           |
    |   77|    ASSIGN COMPONENT gv_class_dbposit OF STRUCTURE                                          |
    |   78|                      <fs_wkarea> TO <fs_class>.                                            |
    |   79|    CREATE DATA ref TYPE TABLE OF (i_enum_dbtab).                                           |
    |   80|    ASSIGN ref->* TO <ft_data>.                                                             |
    |   81|                                                                                |
    |   82|  ENDCATCH.                                                                                |
    |   83|  IF sy-subrc = 15.                                                                         |
    |   84|*   Error on Assignment.                                                                    |
    |   85|    CALL FUNCTION 'RS_DME_COM_ADDMSG_NOLOG'                                                 |
    |   86|      EXPORTING                                                                             |
    |   87|        i_type    = 'E'                                                                     |
    |   88|        i_msgno   = 301                                                                     |
    |   89|        i_msgv1   = 'EVALUATION_PHASE'                                                      |
    |   90|      IMPORTING                                                                             |
    |   91|        es_return = ls_return.                                                              |
    |   92|    APPEND ls_return TO e_t_return.                                                         |
    |   93|    EXIT.                                                                                |
    |   94|  ENDIF.                                                                                |
    |   95|                                                                                |
    |   96|* For the un-trained Rec-Ids, evaluate.....                                                 |
    |   97|  REFRESH lt_recinp.                                                                        |
    |   98|  APPEND LINES OF i_t_records TO lt_recinp.                                                 |
    |   99|  SORT lt_recinp .                                                                          |
    |  100|* Open Cursor..                                                                             |
    |  101|  DATA: l_curs TYPE cursor.                                                                 |
    |  102|  DATA: l_psize TYPE i VALUE 10000.                                                         |
    |>>>>>|  OPEN CURSOR WITH HOLD l_curs FOR                                                          |
    |  104|   SELECT * FROM (i_enum_dbtab)                                                             |
    |  105|     WHERE rsdmdt_recid NOT IN                                                              |
    |  106|        ( SELECT rsdmdt_recid FROM                                                          |
    |  107|             (i_learn_tab) ).                                                               |
    |  108|                                                                                |
    |  109|*  Start Fetch...                                                                           |
    |  110|  DO.                                                                                |
    |  111|    FETCH NEXT CURSOR l_curs                                                                |
    |  112|      INTO CORRESPONDING FIELDS OF TABLE <ft_data>                                          |
    |  113|      PACKAGE SIZE l_psize.                                                                 |
    |  114|    IF sy-subrc NE space.                                                                   |
    |  115|      EXIT.                                                                                |
    |  116|    ENDIF.                                                                                |
    |  117|                                                                                |
    |  118|*     Process records...                                                                    |
    |  119|    LOOP AT <ft_data> ASSIGNING <fs_wkarea>.                                                |
    |  120|                                                                                |
    |  121|*     Call Prediction Function.                                                             |
    |  122|      CALL FUNCTION 'RS_DME_DTP_PREDICT_STRUCTURE'                                          |

    Hi Claudio,
    well the message is very clear and I think in your case you need to split your model into a few somehow equal models, each not having more than 2 leaves.
    Another option might be to do more things serially instead of parallel.
    Hope it helps
    regards
    Siggi

  • Runtime error while log in to SP12 help.

    Hi SDN,
    I have installed ABAP Trail SP12 several time each & every time after 2 - 3 days i am getting one dump then i have to again format my whole system to get it work again.
    Since the registry cleanning tool is also not working.
    following is the DUMP
    Runtime Errors         DBIF_RSQL_INVALID_REQUEST                                                         
    Date and Time          2008-03-27 08:38:50                                                                               
    Short text                                                                               
    Invalid request.                                                                               
    What happened?                                                                               
    The current ABAP/4 program terminated due to                                                        
         an internal error in the database interface.                                                                               
    Error analysis                                                                               
    An invalid request was made to the SAP database interface in a statement                            
          in which the table "DOKTL " was accessed.                                                                               
    The situation points to an internal error in the SAP software                                       
         or to an incorrect status of the respective work process.                                           
         For further analysis the SAP system log should be examined                                          
         (transaction SM21).                                                                               
    For a precise analysis of the error, you should supply                                              
         documents with as many details as possible.                                                                               
    Trigger Location of Runtime Error                                                                       
         Program                                 SAPMSYST                                                    
         Include                                 SAPMSYST                                                    
         Row                                     2,556                                                       
         Module type                             (FORM)                                                                               
    Please Help,
    Regards,
    Rahul

    There's another thread here about the same problem and I noticed that it's exactly the same error message.
    Just for fun I did a search on Row 2,556 and found: SAPNW70 Runtime Error BDIF_RSQL_INVALID_REQUEST

  • Runtime Error in Scrapping of asset ABAVN

    Dear All,
    Runtime Errors         MESSAGE_TYPE_X.
    We are into ECC 6.00. I got following Error while doing Scrapping of asset using T.code ABAVN.
    *Runtime Errors         MESSAGE_TYPE_X
    Date and Time          18.02.2008 04:42:21
    Short dump has not been completely stored (too big)
    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).*
    Point for sure. If problem solved.
    Regards
    Senthamarai kannan

    Hi Mr. Mann
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          19.02.2008 01:46:41
    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:
         System error (termination point SORT_2)
         Long text of error message:
          Diagnosis
              An internal error has occurred.
          System Response
              You cannot continue with processing.
          Procedure
              Contact SAP to establish whether the error can only be rectified by
              a program correction, or whether it can also be rectified by
              changes to the settings. There may also be an error in the updating
              of the data which must be resolved.
              Specify the following parameters when reporting the error:
              o   Message           : GLT0/000
              o   Program           : SAPLGLT0
              o   Termination point : SORT_2
         Technical information about the message:
         Message class....... "GLT0"
         Number.............. 000
         Variable 1.......... "SORT_2"
         Variable 2.......... "SAPLGLT0"
         Variable 3.......... " "
         Variable 4.......... " "
    Trigger Location of Runtime Error
         Program                                 SAPLGLT0
         Include                                 LGLT0FER
         Row                                     38
         Module type                             (FORM)
         Module Name                             INTERNAL_ERROR
    Source Code Extract
    Line  SourceCde
       8 *       text
       9 ----
      10 FORM internal_error USING errorcode.
      11
      12 * Local fields
      13   DATA:
      14       subseq_flag     TYPE glt0_flag.
      15
      16 * Error?
      17   CHECK sy-subrc <> 0.
      18
      19 * Get subsequent posting flag
      20   PERFORM subsequent_posting USING    space
      21                              CHANGING subseq_flag.
      22
      23   IF errorcode = gc_clrbal.
      24     IF subseq_flag = xon.
      25       PERFORM message_send USING 'A000'
      26                            errorcode
      27                            sy-msgv2
      28                            sy-msgv3
      29                            sy-msgv4.
      30     ELSE.
      31       MESSAGE x000 WITH errorcode sy-msgv2 sy-msgv3 sy-msgv4.
      32     ENDIF.
      33   ELSE.
      34 * Subsequent posting -> message handler, else -> dump
      35     IF subseq_flag = xon.
      36       PERFORM message_send USING 'A000' errorcode sy-repid space space.
      37     ELSE.
    >>>>       MESSAGE x000 WITH errorcode sy-repid.
      39     ENDIF.
      40   ENDIF.
      41
      42 ENDFORM.                    " INTERNAL_ERROR
      43
      44 ----
      45 &----
      46 *&      Form  MESSAGE_STORE
      47 &----
      48 *       text
      49 ----
      50 FORM message_store.
      51
      52   CALL FUNCTION 'MESSAGE_STORE'
      53     EXPORTING
      54       exception_if_not_active = space
      55       arbgb                   = sy-msgid
      56       msgty                   = sy-msgty
      57       txtnr                   = sy-msgno
    Warm regards
    kannan

Maybe you are looking for