Short dump Error-ABAP/4 Run time Error

Hi Expert,
Dump:ABAP/4 Processor:MESSAGE_TYPE_X Why this error came,I would like to Investigation on Perticular error,Please Some body give me an Exact answer,so that i closed the ticket.
Regards,
Raju.

Hi Suresh,
What is the actual issue?
When did you get this error.
To know about this type of error, check below link...
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=dump%3aABAP%2F4Processor%3A+MESSAGE_TYPE_X&adv=false&sortby=cm_rnd_rankvalue
Also check this:
Note 1016317 - SP13:PC: Start type 'Date & time' gets scheduled wrong
"Process chain scheduling results in dump- ABAP/4 processor: MESSAGE_TYPE_X"
Solution:
In the short dump analysis, the process fails at function module
RSS2_PSA_NEW_OLD_DS
call function 'RSDS_DATASOURCE_SINGLE_GET'
Regards,
KK.

Similar Messages

  • ABAP/4 run time error with error code  SNAP_NO_NEW_ENTRY

    Dear All,
               I've installed SAP R/3 IDES on Oracle on Windows 2003 server.After clicking Log on button , I should be asked to enter client,user and password.But, my system does not display such details.Instead I get ABAP/4 run time error with error code  SNAP_NO_NEW_ENTRY that too after a long time.
                Can you please address what is the reason for this problem and how to over ride it?
    Regards,
    S.Suresh

    Hi,
    the most probable reason is an archiver stuck. Backup the archived redo log files and delete them afterwards.
    The database will archive some more logs after this. Handle them in the same manor. For complete explanation search for brtools.
    Regards
    Ralph Ganszky

  • Cannot download itunes. error message is run time error 6034

    I cannot download itunes. the error message is run time error 6034. advices to contact application support team

    Try the following user tip if you're still having the 6034 issues:
    Troubleshooting issues with iTunes for Windows updates

  • Run time Errors GETWA_NOT_ASSIGNED at Time of Print Reports.

    Hello hy All experts.
    I ma trying to print Reports, but at time of preview i got an error message. Run time Errors GETWA_NOT_ASSIGNED.
    Please Give me Solutions.
    Thnks
    Bhavesh Panchal.
    Baroda

    FORM fetch_data.
      break mtabap.
      SELECT *
              FROM vbep
              INTO TABLE it_vbep
              WHERE edatu IN so_edatu
              AND vbeln IN so_vbeln.
      IF NOT it_vbep[] IS INITIAL.
        SELECT *
                       FROM vbak
                       INTO TABLE it_vbak
                       FOR ALL ENTRIES IN it_vbep
                       WHERE vbeln = it_vbep-vbeln
                       AND kunnr IN so_kunnr.
      ENDIF.
      IF NOT it_vbak[] IS INITIAL.
        SELECT *
                FROM vbpa
                INTO TABLE it_vbpa
                FOR ALL ENTRIES IN it_vbak
                WHERE vbeln = it_vbak-vbeln
                AND   posnr = space.
        SELECT *
                 FROM vbap
                 INTO TABLE it_vbap
                 FOR ALL ENTRIES IN it_vbak
                 WHERE vbeln = it_vbak-vbeln.
    Select all Customer Data
        SELECT * FROM kna1 INTO TABLE it_kna1
        FOR ALL ENTRIES IN it_vbak
        WHERE kunnr = it_vbak-kunnr .
        SELECT *
                 FROM vbkd
                 INTO TABLE it_vbkd
                 FOR ALL ENTRIES IN it_vbap
                 WHERE vbeln = it_vbap-vbeln.
               and posnr = IT_VBAP-POSNR.
        SELECT *
                 FROM vbbe
                 INTO TABLE it_vbbe
                 FOR ALL ENTRIES IN it_vbap
                 WHERE vbeln = it_vbap-vbeln
                 AND posnr = it_vbap-posnr.
        SELECT *
                 FROM vbup
                 INTO TABLE it_vbup
                 FOR ALL ENTRIES IN it_vbap
                 WHERE vbeln = it_vbap-vbeln
                 AND posnr = it_vbap-posnr.
        SELECT *
                 FROM konv
                 INTO TABLE it_konv
                 FOR ALL ENTRIES IN it_vbak
                 WHERE knumv = it_vbak-knumv
                 AND kinak = space .
        SELECT *
              FROM vbrp
              INTO TABLE it_vbrp
              FOR ALL ENTRIES IN it_vbak
              WHERE aubel = it_vbak-vbeln.
        IF NOT it_vbrp[] IS INITIAL.
          SELECT * FROM likp
                            INTO TABLE it_likp
                            FOR ALL ENTRIES IN it_vbrp
                            WHERE vbeln = it_vbrp-vgbel.
          SELECT * FROM lips
                            INTO TABLE it_lips
                            FOR ALL ENTRIES IN it_vbrp
                            WHERE vbeln = it_vbrp-vgbel
                            AND posnr = it_vbrp-vgpos.
        ENDIF.
      ENDIF.
      LOOP AT it_vbap.
        itab-posnr = it_vbap-posnr.
        itab-posar = it_vbap-posar.
    ITAB-BRGEW = IT_VBAP-BRGEW.
        itab-brgew = it_vbap-brgew.
        itab-ntgew = it_vbap-ntgew.
        READ TABLE it_vbak WITH KEY vbeln = it_vbap-vbeln.
        itab-vbeln = it_vbak-vbeln.
        itab-netwr = it_vbak-netwr.
        itab-kunnr = it_vbak-kunnr.
        READ TABLE it_vbep WITH KEY vbeln = it_vbap-vbeln.
        itab-edatu = it_vbep-edatu.
        READ TABLE it_kna1 WITH KEY kunnr = it_vbak-kunnr.
        itab-name1 = it_kna1-name1.
        READ TABLE it_vbkd WITH KEY vbeln = it_vbap-vbeln .
        itab-bstdk = it_vbkd-bstdk.
        itab-bstkd = it_vbkd-bstkd.
        READ TABLE it_vbrp WITH KEY aubel = it_vbap-vbeln aupos = it_vbap-posnr.
        READ TABLE it_lips WITH KEY vbeln = it_vbrp-aubel posnr = it_vbrp-aupos.
        itab-delivery = it_lips-vbeln.
        itab-lfimg = it_lips-lfimg.
        READ TABLE it_likp WITH KEY vbeln = it_vbrp-aubel   .
        itab-lfdat = it_likp-lfdat.
       itab-ntgew = it_likp-ntgew.
        break mtabap.
        READ TABLE it_vbup WITH KEY vbeln = it_vbap-vbeln posnr = it_vbap-posnr.
        itab-lfsta = it_vbup-lfsta.
        READ TABLE it_vbep WITH KEY vbeln = it_vbap-vbeln posnr = it_vbap-posnr.
        itab-wmeng = it_vbep-wmeng .
        itab-bmeng = it_vbep-bmeng.
        READ TABLE it_vbbe WITH KEY vbeln = it_vbap-vbeln posnr = it_vbap-posnr.
        itab-omeng = it_vbbe-omeng .
        READ TABLE it_konv WITH KEY knumv = it_vbak-knumv
                                    kposn = it_vbap-posnr
                                    kschl = 'PR00'.
       ITAB-KBETR = IT_KONV-KBETR / 10. " CONDITION RATE
        itab-kbetr = it_konv-kbetr.
        itab-kwert = it_konv-kwert . "CONDITION VALUE
       itab-pending_val =  ITAB-OMENG * ITAB-KWERT .
        itab-pending_val =  itab-omeng * itab-kbetr .
        APPEND itab.
      ENDLOOP.
    ENDFORM. "data_retrieval
    *&      Form  build_listheader
          text
         -->IT_LISTHEADER  text
    Show quoted text -
    FORM build_listheader USING it_listheader TYPE slis_t_listheader.
    DATA HLINE TYPE SLIS_LISTHEADER.
      DATA: ls_line TYPE slis_listheader.
    bhavesh
    HLINE-INFO = 'report Developed by Bhavesh'.
    HLINE-TYP = 'H'.
    Header
    Bhavesh
      CLEAR ls_line.
      ls_line-typ = 'H'.
    LS_LINE-KEY: not used for this type
      ls_line-info = 'Sales ORDER Report'.
      APPEND ls_line TO it_listheader.
    bhavesh
    ***Selection
      CLEAR ls_line.
      ls_line-typ = 'S'.
      ls_line-key = 'Key 1'.
      ls_line-info = 'SFEL'.
      APPEND ls_line TO it_listheader.
      ls_line-key = 'Key 2'.
      ls_line-info = 'SFEL'.
      APPEND ls_line TO it_listheader.
    ***Action
      CLEAR ls_line.
      ls_line-typ = 'A'.
    LS_LINE-KEY: not used for this type
      ls_line-info = 'Status list'.
      APPEND ls_line TO it_listheader.
    ENDFORM. "BUILD_LISTHEADER
    *ENDFORM. "build_listheader
    *&      Form  display
    *&       text
    FORM display.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
            EXPORTING
              i_callback_program      = sy-repid
             i_callback_top_of_page  = 'TOP_OF_PAGE'
              is_layout               = alv_layout
              it_fieldcat             = i_fieldcat
             it_events               = gt_events[]
              i_callback_user_command     = 'USER_COMMAND'
              i_grid_title            = 'BHAVESH REPORT'
            TABLES
              t_outtab                = itab[].
      CLEAR : itab .
    ENDFORM.                    "display
    *&      Form  top_of_page
          text
    FORM top_of_page.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          it_list_commentary = it_listheader[].
    i_logo = 'ENJOYSAP_LOGO'.
    I_END_OF_LIST_GRID =
    ENDFORM. "TOP_OF_PAGE

  • XL reporter 2005: Run time error 430

    Hi,
    When launching XL reporter 6.80.01.25 the following error message appear:
    "Run time error 430
    Class does not support automation or does not support expected interface."
    Please advice.
    Regards
    Thomas Lai

    Hi Thomas,
    We had exactly the same problem when upgrading to patch 25. I think it's a bug in that patch. We got around it by uninstalling patch 25, rebooting the workstation and then reinstalling patch 25 again (...not sure if the reboot made any difference but I thought I'd mention it anyway). The program then worked ok. Very strange!!
    Hope this helps,
    Owen

  • Template Builder not found followed by Run-time error '429'

    Hello,
    I am having problems with BI Publisher.
    I am running the application on a Windows 2003 server via a Citrix connection using Word 2007 (SP2) (multilingual French/English). On this forum, I have seen numerous threads about this type of error but none seems to be working for us.
    Symptoms:
    I installed BI Publisher with admin rights (account A) and it works fine using this account
    I copy the TBCrosstab.dot, TemplateBuilder.dot, WordAnalyzer.dot in another User Profile "%USERPROFILE%\Application Data\Microsoft\Word\STARTUP" (Account B)
    All macros are enabled in account B
    The Add-ins menu shows but when I click on Connection I get the Template Builder not found error followed by Run-time error '429'
    I uninstall BI Publisher from Account A and install it using account B
    It now works fine with account B but I get the error messages in account A...
    Does BI Publisher work using multiple accounts on a single machine?
    Thanks

    Did you find a solution to this problem?

  • WAD: Crashes with Run Time Error '339': Component 'formx.ocx' (missing)

    when using SAPGui 7.10 --> BW3.5x Web Application Designer the
    application fails to start and we get the following error message.
    Run Time Error '339': Component 'formx.ocx' or one of it's dependencies
    is not correctly registered: a file is missing or invalid.
    This works correctly on some machines but on others we get this error
    message. We have applied the latest patch.
    I suspect some non-sap software component has damaged my installation. How can I debug this? Re-installing SAPGUI doesn't do any good.
    Any ideas gratefully received.

    Check the following link. Is your issue related to this???
    Re: Error in WAD

  • Newbie question NON-FATAL RUN-TIME ERROR IN TUTORIAL (PlotY)

    I'm a first time user, following the tutorial and when when I click on Acquire I get the following error "NON-FATAL RUN-TIME ERROR:   "sample1.c", line 85, col 13, thread id 0x00000D54:   Library function error (return value == -10 [0xfffffff6]). The control is not the type expected by the function"
    Code is as follows (line 85 is PlotY......:
        case EVENT_COMMIT:                                                                                                       
            srand (time(NULL));                                                                                                  
            amp = rand ()/32767.0;                                                                                               
            SinePattern (100, amp, 180.0, 2.0, sine);                                                                            
            PlotY (panelHandle, PANEL_Waveform, sine, 100, VAL_DOUBLE, VAL_THIN_LINE, VAL_EMPTY_SQUARE, VAL_SOLID, 1, VAL_RED);  
            break;    
    Its not obvious why it crashes on this line, any help would be appreciated.
    Thanks
    Jeff

    Happy to hear that you have solved your problem.
    Just to be clear, there is no problem in using lowercase letters for control ID, but since the usual CVI behaviour is to use uppercase letters I was wondering if you created the control by yourself and if it could be a wrong one.
    CVI does not really address controls by name: if you see in the include file associated to the UIR you'll see that PANEL_CONTROL is really a macro with an associated value, which is the one the program really uses (see my first post to understand how PlotY operates; the same happens for all functions that operate on control like Get/SetCtrlVal or GetSetCtrlAttribute for example).
    Neither CVI operates any cross check between the panel handle and the control you are addressing: that's why I pointed you to the panel handle value, to be sure that you are not operating on a control using the handle of a different panel, a situation that may happen if you are using more than one panel at a time.
    These are the reasons that may rise an 'incorrect control type' error.
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • What causes Run Time Error 10086 when attempting an external calibration with the Calibrate_E_Series funcition.

    I am using Vb6(sp5), NT4, Component Works (latest), and Ni-Daq 6.9.1. The error occurs when using either a PXI-6052E or PXI-6070E. The Self Cal works fine but the external cal code generates this error during the call. The code used is taken directly from the programming example in the NI_DAQ programmers reference for the Calibrate_E_Series function.
    The Error Text is:
    Run-time error '10086':
    The external reference is invalid

    John;
    I found a Knowledge Base about that error you can refer to. The KB, originally, talks about Labview, but, as Labview makes NI-DAQ function calls in the same way any other Software language, you can apply the same concepts when using VB. The link is:
    http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a100753500/2d8abbbb8d45ff74862565f6005c8d7b?OpenDocument
    and the KB number is 18TAPEY5
    in case you prefer to search for it at our home page.
    Hope this helps.
    Filipe
    Applications Engineer
    National Instruments

  • Microsoft C++ Run Time Error

    hi experts...
    When iam login to sap b1 it's showing Run Time Error
    Microsoft C++ Run Time Error 
    Programs:C/progrmsfile/sap/sapb1.exe
    Abnormal programmer Terminations.
    We unistall totall .net s/w then it's showing same error.
    before i done some add-ons in my pc is it resone ?
    how i can solve this problem?
    Edited by: Darius Heydarian on Mar 25, 2008 5:56 PM
    Edited by: Darius Heydarian on May 6, 2008 5:15 PM

    Hello,
    In addition to Lucas suggestion, there is another SAP Note 852031 following above Note 808354. Try the suggested work around in this Note only after going over Note 808354. The work around is good for cases where more than one UI versions ar registered at the same time.
    Note 852031 Link:
    [https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0000852031]
    Hope this Note can be useful.
    Best Regards,
    Tim
    Edited by: Tim Dai on May 19, 2008 4:40 PM

  • XL Reporter Run-time Error '429' ActiveX component can't create object

    Hi Everyone,
    When trying to install XL Reporter on a Windows 2003 Server SP2 machine getting the following Error:
    XL Reporter
    Run-time error '429':
    ActiveX component can't create object.
    Did anyone get this error? Please advise of any steps we can try to resolve.
    Kind Regards,
    Kafil

    Dear Friend,
                 I had described the problem to our technical support team, and they replied as follows u2013
    They solved the Script related error by several stages.
    They checked the machine for any mal-ware existence by the tool provided by Microsoft (MS Mal-ware remover).
    Then they tried by installing the following patches from Microsoft u2013
    http://support.microsoft.com/kb/949140
    Windows Script 5.7 for Windows XP
    http://www.microsoft.com/downloads/details.aspx?familyid=887fce82-e3f5-4289-a5e3-6cbb818623aa&displaylang=en
    Windows Script 5.6 for Windows Server 2003
    http://www.microsoft.com/downloads/details.aspx?FamilyId=C717D943-7E4B-4622-86EB-95A22B832CAA&displaylang=en
    Windows Script 5.6 for Windows XP and Windows 2000
    The internal matter to this problem was about the following DLL and its version u2013
    C:\WINDOWS\system32
    vbscript.dll
    5.5.0.8820
    Desired
    5.6.0.8820
    Check, if the information helps you.

  • Run time error (short dump) executing program SCAN_BW_REFERENCES in SE80

    Hi experts,
    I am not an ABAPer, or Basis person, rather a hybrid functional/technical Key User for our Business Warehouse system (BW 3.5, Netweaver 2004).  We have a user who cannot save BW reports to his favorites and he is getting a number of error messages.  OSS note 887002 seems to address this and indicates that I should run program SCAN_BW_REFERENCES from transaction SE80.  The program is supposed to perform the checks for BW objects assigned to the Favorites and identify situations causing terminations in BW frontend applications.  I have attempted to execute this program on several occassions and always get run-time errors (short dumps).  Here is the error:
    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    Date and Time          2008.09.17 19:00:49
    ShrtText
         No storage space available for extending an internal table.
    What happened?
         You attempted to extend an internal table, but the required space was
         not available.
    I have been informed by our Basis group that I have reached a memory limit, but they will not extend the memory paramters.  Any ideas on a work-a-round or a way to minimize the number of records this program is pulling in, in an attempt to get it to run?
    Thanks,
    HC

    Hi,
    The only response I got from Basis was that they would not extend the memory parameters because they are for all users in the system.  Not sure what that means. 
    The full dump is too large to paste here.  I think what I will do is to see if our ABAPers can create a modified version of this program to include selection by user.  Typically it is for only one user that I need to run the program, and that surely would fall within the space requirements.
    Thanks for your answer.
    //HC

  • ABAP run time error

    Dear ALL,
    When we are creating sales order after entering sold-to-party, Material & Quantity when we press ENTER key That time
    we are getting following run time error
    Hoe to resolve this?
    Runtime Errors         SAPSQL_INVALID_FIELDNAME                                                    
    Except.                CX_SY_DYNAMIC_OSQL_SEMANTICS                                                
    Date and Time          15.01.2009 16:04:19                                                         
    Short dump has not been completely stored (too big)                                                                               
    Short text                                                                               
    A dynamically specified column name is unknown.                                               
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLV61Z" 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_DYNAMIC_OSQL_SEMANTICS', was                 
         not caught in                                                                               
    procedure "SEL_KONDTAB" "(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:                                                              
        An Open SQL clause was specified dynamically. The contained field name                        
        "ALAND" does not exist in any of the database tables from the FROM clause.                    
    How to correct the error                                                                               
    Check the field name in the SELECT clause.                                                                               
    If the error occures in a non-modified SAP program, you may be able to                        
        find an interim solution in an SAP Note.                                                      
        If you have access to SAP Notes, carry out a search with the following                        
        keywords:                                                                               
    "SAPSQL_INVALID_FIELDNAME" "CX_SY_DYNAMIC_OSQL_SEMANTICS"                                     
        "SAPLV61Z" or "LV61ZU01"                                                                      
        "SEL_KONDTAB"                                                                               
    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.                                                                               
    The exception must either be prevented, caught within proedure                                
        "SEL_KONDTAB" "(FORM)", or its possible occurrence must be declared in the                    
        RAISING clause of the procedure.                                                              
        To prevent the exception, note the following:                                                 
    System environment                                                                               
    SAP-Release 700                                                                               
    Application server... "slgsap-prd"                                                            
        Network address...... "10.140.1.11"                                                           
        Operating system..... "Windows NT"                                                            
        Release.............. "5.2"                                                                   
        Hardware type........ "8x AMD64 Level"                                                        
        Character length.... 16 Bits                                                                  
        Pointer length....... 64 Bits                                                                 
        Work process number.. 0                                                                       
        Shortdump setting.... "full"                                                                               
    Database server... "SLGSAP-PRD"                                                               
        Database type..... "MSSQL"                                                                    
        Database name..... "PRD"                                                                      
        Database user ID.. "prd"                                                                               
    Terminal................. "SD0123l"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                         
        created (date)... "May 6 2008 00:13:21"                                                       
        create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"                              
        Database version. "SQL_Server_8.00 "                                                                               
    Patch level. 159                                                                               
    Patch text.. " "                                                                               
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                              
        SAP database version. 700                                                                     
        Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows                
         NT 6.0"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 20949200                                                                               
    Heap.... 0                                                                               
    Page.... 196608                                                                               
    MM Used. 15928048                                                                               
    MM Free. 828016                                                                               
    User and Transaction                                                                               
    Client.............. 900                                                                      
        User................ "ADMIN"                                                                  
        Language key........ "E"                                                                      
        Transaction......... "VA01 "                                                                  
        Transactions ID..... "03F0E2DD6B35F16CBBFF002219897F24"                                                                               
    Program............. "SAPLV61Z"                                                               
        Screen.............. "SAPMV45A 4900"                                                          
        Screen line......... 930                                                                      
    Information on where terminated                                                                   
        Termination occurred in the ABAP program "SAPLV61Z" - in "SEL_KONDTAB".                       
        The main program was "SAPMV45A ".                                                                               
    In the source code you have the termination point in line 672                                 
        of the (Include) program "LV61ZU01".                                                          
        The termination is caused because exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"                    
         occurred in                                                                               
    procedure "SEL_KONDTAB" "(FORM)", but it was neither handled locally nor                      
         declared                                                                               
    in the RAISING clause of its signature.                                                                               
    The procedure is in program "SAPLV61Z "; its source code begins in line                       
        260 of the (Include program "LV61ZU01 ".                                                      
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    642     if se_prestep              = yes or                                                     
      643        se_read_only_one_record = yes.                                                       
      644       if t681-ksdat is initial.                                                             
      645         if se_read_all_prestep is initial.                                                  
      646           select * from (t681-kotab) appending table <cond_tab>                             
      647                  up to 1 rows                                                               
      648                  where kappl  = se_kappl                                                    
      649                  and   kschl  = se_kschl                                                    
      650                  and   (coding_tab).                                                        
      651           h_subrc = sy-subrc.                                                               
      652         else.                                                                               
    653           select * from (t681-kotab) appending table <cond_tab>                             
      654                  where kappl  = se_kappl                                                    
      655                  and   kschl  = se_kschl                                                    
      656                  and   (coding_tab).                                                        
      657         endif.                                                                               
    658                                                                               
    659 * it is enough to find one record in prestep                                                
      660 * (care must be taken with pool tables - depending on database this                         
      661 *  will cost performance instead of saving)                                                 
      662         if select_split ne 0 and h_subrc ne 0.                                              
      663           modify coding_tab from coding_alter index select_split.                           
      664           select * from (t681-kotab) appending table <cond_tab>                             
      665                  up to 1 rows                                                               
      666                  where kappl  = se_kappl                                                    
      667                  and   kschl  = se_kschl                                                    
      668                  and   (coding_tab).                                                        
      669         endif.                                                                               
    670       else.                                                                               
    671         if se_read_all_prestep is initial.                                                  
    >>>>>           select * from (t681-kotab) appending table <cond_tab>                             
      673                  up to 1 rows                                                               
      674                  where kappl  = se_kappl     
    Regards,
    Akshay
    Edited by: Akshay Dalal on Jan 17, 2009 6:25 AM
    Edited by: Akshay Dalal on Jan 17, 2009 6:30 AM

    Dear Akshay,
    We will NOT be able to provide you with a solution on this forum, because we have no clue what configuration do you have in your system and what user exits or other custom development may have been done in your specific system.
    Lakshmipathi has already correctly pointed to a similar post. You might want to get an ABAPer to set a breakpoint just before the error occurs, then he/she might provide you with more information, which may (or may not) be helpful.
    There is obviously something wrong in the pricing condition either on configuration level or in a user exit. If you write to SAP (which you should, because it's a standard program), they will ask to connect to your system, because they don't have any chrystal balls over there either.
    Just in case - before going any further, try running the program RV80HGEN (in the test system, of course), which re-generates requirements and formulas. Sometimes it helps, although I doubt that it is the case here.
    Also if you've used some custom (Z...) fields in the pricing configuration, that's where the problem is most likely.

  • 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

  • *FBCJ - CASH JOURNAL POSTING - ABAP RUN TIME ERROR*.

    Hai,
    My problem is, while FBCJ cash journal posting, Error message comes as Programme terminated, short dump is beeing formatted. The screen is quitting out to ABAP RUN TIME ERRORS.  Short text of error message- For object, CAJO_DOC2 101, numer range interval 01 does not exist.( I have given the number range, but result is same.) - Pls advice, document type for cash journal is DZ ?.expecting valued support- Iam working on SAP R/3 4.7 enterprise.- TITUS GEORGE.

    Hi,
    GOto SNUM, Input CAJO_DOC2...
    Click on change and click on document number ranges.
    Maintain the document number ranges for your company code..
    That should solve the problem.
    Good Luck
    Cheers,
    Redoxcube

Maybe you are looking for

  • Using US MacBooks in the UK

    I am trying to use my US Macbook in the UK. I tried to connect it to the power outlet botn with a conventional adapter and with a voltage converter; but in neither case does the adapter seem to be satisfied with the kind of power it gets. The light o

  • Hotmail help says to optimize Firefox to correct Attachment ID has bad format problem when there is not attachment - how do I optimized Firefox 3.6.12?

    Several day ago my Hotmail acct seemed to be hacked as the following email ''I think this is a nice website,I like it very much.If you have time please browse it.Maybe you can find some products that are suitable for you.Their priciple is :100% origi

  • Down payments country spec. issue

    This is one more country specific posting problem and it is related to down payment processing. When I receive down payment from customer I have to report it on separate GL account (DP on current assets). But difference then standard settings is that

  • Has anyone else noticed how selection is bugged in 5.1

    Hey - I wish there was a warning that adding a new product did not return to a draft message! OK - entering it again! IOS 5.1 has introduced bugs connected with '-- ' in front of a mail sig. If one clisks a blank line above, and 'select' there is no

  • Facetime stopped working. Help?!

    Out of no where facetime stopped working on my iphone 4. Ive tried resetting/restarting my phone as well as the router! I feel like an idiot for not being able to figure this out! Anyone have any ideas as to how to fx this?!