Short Dump, Exception condition "NOT_EXIST" raised

Dear Colleagues!
I am having a problem with short dump, I am getting the message Exception condition "NOT_EXIST" raised.
I am trying to load data to ODS with full load and filtering via a DTP.
In the monitoring the load doesn't even get started.
I have already loaded data succesfully in this ODS... But now it doesn't work anymore..
I also tried to replicate and active all the rules and objects again.
And in the source system if I test the extractor it works fine.
I saw an earlier thread on this issue, and it recommended programs ZDMDELTAREPAIR or RSBDELTAREPAIR, but this thread was especially for BW 3.5. We are using 7.0 and have SP10. Are these programs still valid or is there another note for 7.0?
Hope you can help!
Regards Silje
Does anyone have any ideas?
regards, Uros

Hi again,
I tried RSBDELTAREPAIR and it worked!
Thanks to the forum again!
Silje

Similar Messages

  • Short Dump -   Exception condition "CNTL_ERROR" raised.

    hi all
    I  found a runtime error
    but i can't find the correct answer either in SDN or Sap Notes
    plz tell me what can i do to solve this problem
    sap version : 4.6c
    h3.
    Error analysis
    A RAISE statement in the program "SAPLOLEA " raised the exception
    condition "CNTL_ERROR".
    Since the exception was not intercepted by a superior program
    in the hierarchy, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    h3.
    Source code extract
    000010   FUNCTION AC_SYSTEM_FLUSH .
    000020   *"
    000030   ""Lokale Schnittstelle:
    000040   *"  IMPORTING
    000050   *"     VALUE(CALLED_BY_SYSTEM) TYPE  C OPTIONAL
    000060   *"  EXCEPTIONS
    000070   *"      CNTL_SYSTEM_ERROR
    000080   *"      CNTL_ERROR
    000090   *"
    000100     data: sysubrc like sy-subrc.
    000110
    000120     CALL FUNCTION 'AC_FLUSH_CALL'
    000130          EXPORTING
    000140               SYSTEM_FLUSH = 'X'
    000150               CALLED_BY_SYSTEM = CALLED_BY_SYSTEM
    000160          IMPORTING
    000170               MESSAGE_NR   = sysubrc
    000180               MESSAGE_TEXT = SY-MSGLI.
    000190
    000200     sy-subrc = sysubrc.
    000210
    000220     CASE SY-SUBRC.
    000230       WHEN 0.
    000240       WHEN 1.
    000250         RAISE CNTL_SYSTEM_ERROR.         "// system_error
    000260       WHEN 2.
    000270         RAISE CNTL_ERROR.                "// method_call_error
    000280       WHEN 3.
    000290         RAISE CNTL_ERROR.                "// property_set_error
    000300       WHEN 4.
         >              RAISE CNTL_ERROR.                "// property_get_error       -
    >>>>> here's the error occured
    000320       WHEN OTHERS.
    000330         RAISE CNTL_ERROR.
    000340     ENDCASE.
    000350
    000360   ENDFUNCTION.
    Edited by: kwang young kim on May 6, 2010 8:38 AM

    Hi,
    This error is pretty common when using ABAP GUI controls. Actually it says: "Something was wrong with some control data so the SAPGUI cannot handle it".
    Sometimes this happens accidently (might be a problem on the PC or something else), so you should try the same action (perhaps after restarting the SAP GUI or even the PC) and see whether the problem persists.
    if so (and also other users encounter the same problem) this is probably a program bug. Check your control handling program code for errors.
    If you cannot see any problem by just reviewing the code switch on the SAPGUI trace for errors (can be found in the SAPGUI settings popup). Depending on what data you want to be traced this trace file can be very huge! But eventually you will see the actual error message given by the SAPGUI and this normally gives you an idea what went wrong.
    Regards,
    Gerd Rother

  • Runtime error raise_exception (Exception condition "NOT_EXIST" raised)

    Hi,
    I tried to ran a DTP to load data in a Standard DSO. Once I run the DTP ,instantly it is showing me short dump.I tried to ran it 2 times. Every time it shows me dump
    Runtime Errors         RAISE_EXCEPTION
    Short Text : Exception condition "NOT_EXIST" raised.
    Error Analysis : A RAISE statement in the program "SAPLRSSM" raised the exception
    condition "NOT_EXIST".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    Thanks in advance,
    Regards,
    Snehasish

    Hi,
    This kind of issues occur in BI7.0, the cause is not clear.
    You can once again delete the Data in the DSO using SE14(If Production system, make sure you contact your Basis team for this).
    You will have to use the table names(check the Delete data option & click on Activate and adjust databas)
    Thanks,

  • Getting a dump  Exception condition "CNTL_ERROR" raised in ALV

    Hi ,
    I have a requirement where I have to do drag and drop operation of TOs from one queue to another queue in an ALV tree between nodes. The drag and drop operation is working fine, but suddenly i get a dump lilke * Exception condition "CNTL_ERROR" raised*  .  
    A RAISE statement in the program "CL_GUI_CFW====================CP" raised the
      exception
    condition "CNTL_ERROR".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    This dump is occuring from a customized transaction ZLRF1 ... where I copied all the includes from the LRF1. So, i will not be able to use any note. Can any1 please help me to resolve this issue <removed by moderator>
    Edited by: Thomas Zloch on Sep 15, 2011 1:46 PM

    Since you're saying you made a copy of all the includes to their corresponding zincludes, in the following includes
    ZLLRFMONTOP
    replace LRF1 with ZLRF1 and make sure the following includes are activated
    ZLLRFMONCLA
    ZLLRFMONTOP

  • Dump error  Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.

    hi ppl,
              I have created a simple badi,when i call this badi  its showing the dump error  Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.

    HI,
    I have checked all of them
    Actually i am trying this example  from saptechnical. com
    Even i have tried others examples also but everytime I am recieving dame dump
    Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.*
    Edited by: Sumesh Nair on Apr 24, 2009 7:08 AM
    Edited by: Sumesh Nair on Apr 24, 2009 7:09 AM
    Edited by: Sumesh Nair on Apr 24, 2009 7:09 AM

  • Exception condition "CONVERSION_ERROR" raised.

    Hi,
    We have been getting short dumps in our production system daily. I was unable to locate the problem by looking at the dump. The dump says that CONVERSION_ERROR raised.
    Which application raised this exception? Again no clue on the same. Please find the text of the dump.
    Short text
        Exception condition "CONVERSION_ERROR" raised.
    What happened?
        The current ABAP/4 program encountered an unexpected
        situation.
    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
        A RAISE statement in the program "CL_SWF_CNT_CONTAINER==========CP" raised the
         exception
        condition "CONVERSION_ERROR".
        Since the exception was not intercepted by a superior
        program, processing was terminated.
        Short description of exception condition:
        For detailed documentation of the exception condition, use
        Transaction SE37 (Function Library). You can take the called
        function module from the display of active calls.
    How to correct the error
        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:
        "RAISE_EXCEPTION" " "
        "CL_SWF_CNT_CONTAINER==========CP" or "CL_SWF_CNT_CONTAINER==========CM02J"
        "IF_SWF_CNT_CONVERSION~TO_XML"
        or
        "CL_SWF_CNT_CONTAINER==========CP" "CONVERSION_ERROR"
        or
        "SAPMSSY1 " "CONVERSION_ERROR"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
           Display the system log by calling transaction SM21.
           Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
        SAP-Release 700
        Application server... "zacwtbsrv0
        Network address...... "10.27.191.
        Operating system..... "Windows NT
        Release.............. "5.2"
        Hardware type........ "4x AMD64 L
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 9
        Shortdump setting.... "full"
        Database server... "ZACWTBSRV063"
        Database type..... "MSSQL"
        Database name..... "EP1"
        Database user ID.. "ep1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 21 2008 00:12:39"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 157
    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...... 8379680
    Heap.... 0
    Page.... 16384
    MM Used. 8164576
    MM Free. 212256
    User and Transaction
        Client.............. 100
        User................ "WF-BATCH"
        Language Key........ "E"
        Transaction......... " "
      Transactions ID..... "FB565CDDF6D0F1BFA292001E0B5D7336"
      Program............. "CL_SWF_CNT_CONTAINER==========CP"
      Screen.............. "SAPMSSY1 3004"
      Screen Line......... 2
      Information on caller of Remote Function Call (RFC):
      System.............. "EP1"
      Database Release.... 700
      Kernel Release...... 700
      Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
      Call Type........... "synchron and transactional (emode 0, imode 0)"
      Inbound TID.........." "
      Inbound Queue Name..." "
      Outbound TID........."0A1BBF4011A4488D408222BD"
      Outbound Queue Name.." "
      Client.............. 100
      User................ "HPRETORIUS"
      Transaction......... " "
      Call Program........."SAPLERFC"
      Function Module..... "ARFC_DEST_SHIP"
      Call Destination.... "WORKFLOW_LOCAL_100"
      Source Server....... "zacwtbsrv064_EP1_00"
      Source IP Address... "10.27.191.64"
      Additional information on RFC logon:
      Trusted Relationship " "
      Logon Return Code... 0
      Trusted Return Code. 0
      Note: For releases < 4.0, information on the RFC caller are often
      only partially available.
    Information on where terminated
        Termination occurred in the ABAP program "CL_SWF_CNT_CONTAINER==========CP" -
         in "IF_SWF_CNT_CONVERSION~TO_XML".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 67
        of the (Include) program "CL_SWF_CNT_CONTAINER==========CM02J".
    Source Code Extract
    Line  SourceCde
       37     lv_xml_table_req = 'X'.
       38   ENDIF.
       39   IF xml_stream IS REQUESTED.
       40     lv_xml_stream_req = 'X'.
       41   ENDIF.
       42
       43   IF use_xslt NE space.
       44
       45     cl_swf_cnt_conversion_service=>to_xml_xslt(
       46       EXPORTING
       47         container                  = me
       48         include_null_values        = include_null_values
      49         include_initial_values     = include_initial_values
      50         include_change_data        = include_change_data
      51         include_texts              = include_texts
      52         include_extension_elements = include_extension_elements
      53         save_delta_handling_info   = save_delta_handling_info
      54         xml_dom_req                = lv_xml_dom_req
      55         xml_table_req              = lv_xml_table_req
      56         xml_stream_req             = lv_xml_stream_req
      57       IMPORTING
      58         xml_dom                    = xml_dom
      59         xml_table                  = xml_table
      60         xml_stream                 = xml_stream
      61         xml_rendered_size          = xml_rendered_size
      62       EXCEPTIONS
      63         conversion_error           = 1
      64         OTHERS                     = 2
      65            ).
      66     IF sy-subrc <> 0.
    >>>>       RAISE conversion_error.
      68     ENDIF.
      69
      70   ELSE.
      71
      72     cl_swf_cnt_conversion_service=>to_xml_ixml(
      73       EXPORTING
      74         container                  = me
      75         include_null_values        = include_null_values
      76         include_initial_values     = include_initial_values
      77         include_typenames          = include_typenames
      78         include_change_data        = include_change_data
      79         include_texts              = include_texts
    Could you please help me out in resolving this issue?
    Is there any need to apply any OSS notes?
    Thanks in advance. And reward points will be given for the solution..
    Thanks,
    Ravikumar.

    Hi,
    U will receive this error when ever it is not possible to achieve runtime conversion.
    i.e When u r passing the data from one type variable to another type if the conversion is not defined or not possible u will get this dump. Just analyze the dump in ST22.
    Look at this simple example. Here i am trying to assign 101.23 to l_p for which length is not sufficient. So i will get dump. But if u do the same with character variable it will truncate the data.
    DATA: l_p(2) TYPE P DECIMALS 2.
    l_p = '103.23'.
    WRITE l_p.
    So check the place where u r getting the dump. It must be some assignment statement.
    Hope it gave some idea on ur case.
    Thanks,
    Vinod.

  • Exception condition "FAILED" raised.

    My TRM functional consultant has been trying to run end of day processes in the Transaction RKLNACHT but the following dump appears:
    Runtime Errors         RAISE_EXCEPTION                                                             
    Date and Time          16.05.2008 10:33:21                                                         
    Short text                                                                               
    Exception condition "FAILED" raised.                                                         
    What happened?                                                                               
    The current ABAP/4 program encountered an unexpected                                         
        situation.                                                                               
    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                                                                               
    A RAISE statement in the program "CL_POSITIONSERVICE_TRQ========CP" raised the               
         exception                                                                               
    condition "FAILED".                                                                               
    Since the exception was not intercepted by a superior                                        
        program, processing was terminated.                                                                               
    Short description of exception condition:                                                                               
    For detailed documentation of the exception condition, use                                   
        Transaction SE37 (Function Library). You can take the called                                 
        function module from the display of active calls.                                            
    How to correct the error                                                                               
    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:                                                                               
    "RAISE_EXCEPTION" " "                                                                        
        "CL_POSITIONSERVICE_TRQ========CP" or "CL_POSITIONSERVICE_TRQ========CM00I"                  
        "GET_POSITIONS_BY_DIFF"                                                                               
    or                                                                               
    "CL_POSITIONSERVICE_TRQ========CP" "FAILED"                                                                               
    or                                                                               
    "RKLNACHT " "FAILED"                                                                         
        If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                                                               
    1. The description of the current problem (short dump)                                                                               
    To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                               
    2. Corresponding system log                                                                               
    Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                               
    3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                                               
    4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                                               
    System environment                                                                               
    SAP-Release 700                                                                               
    Application server... "tetradev"                                                             
        Network address...... "192.168.1.81"                                                         
        Operating system..... "SunOS"                                                                
        Release.............. "5.9"                                                                  
        Hardware type........ "sun4u"                                                                
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 0                                                                      
        Shortdump setting.... "full"                                                                               
    Database server... "tetradev"                                                                
        Database type..... "ORACLE"                                                                  
        Database name..... "DEV"                                                                     
        Database user ID.. "SAPSR3"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                        
        created (date)... "Aug 31 2006 20:59:23"                                                     
        create on........ "SunOS 5.9 Generic_117171-13 sun4u"                                        
        Database version. "OCI_102 (10.2.0.2.0) "                                                                               
    Patch level. 75                                                                               
    Patch text.. " "                                                                               
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."               
        SAP database version. 700                                                                    
        Operating system..... "SunOS 5.9, SunOS 5.10"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 16759392                                                                               
    Heap.... 0                                                                               
    Page.... 180224                                                                               
    MM Used. 10608952                                                                               
    MM Free. 1957592                                                                               
    User and Transaction                                                                               
    Client.............. 300                                                                     
        User................ "DARLINGTON"                                                            
        Language key........ "E"                                                                     
        Transaction......... "KLNACHT "                                                              
        Program............. "CL_POSITIONSERVICE_TRQ========CP"                                      
        Screen.............. "SAPMSSY0 1000"                                                         
        Screen line......... 6                                                                       
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "CL_POSITIONSERVICE_TRQ========CP" -                
         in "GET_POSITIONS_BY_DIFF".                                                                 
        The main program was "RKLNACHT ".                                                                               
    In the source code you have the termination point in line 37                                 
        of the (Include) program "CL_POSITIONSERVICE_TRQ========CM00I".                              
    Source Code Extract                                                                               
    Line       SourceCde                                                                               
    7              l_selector         TYPE REF TO cl_flow_selector_dif,                               
        8      * workarea for table with positions                                                        
        9              l_tab_position     TYPE trqy_position_obj,                                         
       10              l_position         TYPE REF TO if_position_trq,                                    
       11              l_count            type i.                                                         
       12                                                                               
    13      * initialization                                                                               
    14        CLEAR re_tab_position.                                                                   
       15                                                                               
    16      * Get positions for ranges                                                                 
       17        CALL METHOD ca_pos_identifier_dif=>agent->get_persistent_by_range                        
       18          EXPORTING                                                                               
    19            im_context     = trqco_con_trq                                                       
       20            im_ranges      = im_ranges                                                           
       21          RECEIVING                                                                               
    22            re_identifiers = l_tab_identifier.                                                   
       23        CHECK NOT l_tab_identifier IS INITIAL.                                                   
       24                                                                               
    25        LOOP AT l_tab_identifier INTO l_identifier.                                              
       26                                                                               
    27          l_selector = l_identifier->derive_selector( ).                                         
       28                                                                               
    29      *   get TRQ positions for selectors                                                        
       30          CALL METHOD read_positions_by_selector                                                 
       31            EXPORTING                                                                               
    32              im_selector      = l_selector                                                      
       33            RECEIVING                                                                               
    34              re_tab_positions = l_tab_position.                                                 
       35          DESCRIBE TABLE l_tab_position LINES l_count.                                           
       36          IF l_count <> 1.                                                                       
    >>>>>            raise failed.                                                                        
       38          ENDIF.                                                                               
    39          APPEND LINES OF l_tab_position TO re_tab_position.                                     
       40        ENDLOOP.                                                                               
    41                                                                               
    42      ENDMETHOD.                                                                               
    Contents of system fields                                                                        
    Name          Val.                                                                               
    SY-SUBRC      0                                                                               
    SY-INDEX      0                                                                               
    SY-TABIX      2                                                                               
    SY-DBCNT      1                                                                               
    SY-FDPOS      0                                                                               
    SY-LSIND      0                                                                               
    SY-PAGNO      0                                                                               
    SY-LINNO      1                                                                               
    SY-COLNO      1                                                                               
    SY-PFKEY                                                                               
    SY-UCOMM                                                                               
    SY-TITLE      End-of-Day Processing                                                                   
    SY-MSGTY      E                                                                               
    SY-MSGID      64                                                                               
    SY-MSGNO      030                                                                               
    SY-MSGV1                                                                               
    SY-MSGV2                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    SY-MODNO      0                                                                               
    SY-DATUM      20080516                                                                               
    SY-UZEIT      103319                                                                               
    SY-XPROG      SAPLSBAL_DB                                                                             
    SY-XFORM      %_CONTROL_EXIT_DYNPRO                                                                   
    Does anyone have suggestions as to how I can solve this problem?
    Assistance will be appreciated.

    bumping...any suggestions...welcome

  • Exception condition "INVALID_POS" raised

    I have thousands of entries stuck in the outbound queue of my ERP system everyday. This is due to a failed transaction. SAP Support told me there is a problem with the P.O. associated with this transaction and that it is OK to delete the offending entry. Once that is done the remaining entries in the queue process until the queue is empty. My question is: "How do I identify the PO transaction that is not working correctly so I can fix the root cause of this problem? Can I correlate the TID from the SMQ1 tcode to a PO number in SRM?
    The entry below shows the error from SQM1 in the ERP system.
    Client  User    Queue     Destination    Date             Time        Status                                                             TID                                              
    123      Batch   QUEUE1 TARGET1       04/10/2015   18:05:19   Exception condition "INVALID_POS" raised. A20915474B805528491F978BD
    Host           Program
    ADBD123   RSM13000
    Next is the partial contents of the corresponding short dump in the SRM system
    Category                ABAP Programming Error
    Runtime Errors         RAISE_EXCEPTION
    ABAP Program           SAPLSXAB
    Application Component  BC-MID-RFC
    Short text
        Exception condition "INVALID_POS" raised.
    Information on where terminated
        Termination occurred in the ABAP program "SAPLBBP_PDH_NOTIFY_FOLLOWON" -
         "BBP_NOTIFY_FOLLOWON_INBOUND".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 66
        of the (Include) program "LBBP_PDH_NOTIFY_FOLLOWONU01".
    Source Code Extract
    Line  SourceCde
       36         i_with_itemdata = ' '
       37       IMPORTING
       38         e_header        = ls_po_header.
       39 *   check for existence and type of PO (extended)
       40     IF ls_po_header IS INITIAL
       41       OR ls_po_header-be_log_system IS INITIAL.
       42       DELETE lt_purch_orders.
       43       lv_invalid_pos = gc_yes.
       44       CONTINUE.
       45     ENDIF.
       46
       47     ls_document_tab-reqno     = &lt;fs_purch_orders>-po_
       48     ls_document_tab-logsys    = ls_po_header-be_log_s
       49     ls_document_tab-core_key  = lv_tst.
       50     ls_document_tab-doc_type  = gc_doc_be_po_call_off
       51     ls_document_tab-guid      = ls_po_header-guid.
       52     ls_document_tab-entrydate = sy-datum.

    Hello Timothy,
    I am dealing with the same issue as I reply to your query using a workaround we got from SAP.
    In addition to what Raghu has added, I want to share that apart from stuck outbound queue in ECC, we also see consistent periodic ABAP dumps in SRM for program SAPLBBP_PDH_NOTIFY_FOLLOWON.
    When I do a search in the ST22 ABAP dump in SRM system, I can find the PO number under the "Chosen Variable" section under the ABAP Developer view. 
    When I display the SRM PO in BBP_PD transaction, I see that field BE_LOG_SYSTEM - Table  BBP_PDBEH is blank and does not have the ECC system value.
    Executing function module BBP_PD_PO_TRANSFER_EXEC by entering SRM PO Header GUID not only updates the missing value in following fields in table BBP_PDBEH
    BE_LOG_SYSTEM
    BE_OBJECT_TYPE
    BE_OBJECT_ID
    but also starts to clear the stuck out bound queue in ECC.
    I am still not sure about the root cause but I know that the problem is because the BE_LOG_SYSTEM field value in SRM table BBP_PDBEH is not updated.
    Regards,
    Mehul

  • Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised

    Hi All,
    I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
    At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
    ===========================================
    Runtime Errors RAISE_EXCEPTION
    Date and Time 25.07.2008 08:31:11
    Short text 
    Exception condition "METADATA_MISSING" raised. 
    What happened? 
    The current ABAP/4 program encountered an unexpected 
    situation. 
    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 
    A RAISE statement in the program "SAPLDSVAS_SERV" raised the exception 
    condition "METADATA_MISSING". 
    Since the exception was not intercepted by a superior 
    program, processing was terminated. 
    Short description of exception condition: 
    For detailed documentation of the exception condition, use 
    Transaction SE37 (Function Library). You can take the called 
    function module from the display of active calls. 
    How to correct the error 
    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: 
    "RAISE_EXCEPTION" " " 
    "SAPLDSVAS_SERV" or "LDSVAS_SERVC7I" 
    "MAP_DSVAS_TT_DATA_TO_TT_25" 
    or 
    "SAPLDSVAS_SERV" "METADATA_MISSING" 
    or 
    "RDSMOP_MAIN " "METADATA_MISSING" 
    If you cannot solve the problem yourself and want to send an error 
    notification to SAP, include the following information: 
    1. The description of the current problem (short dump) 
    To save the description, choose "System->List->Save->Local File 
    (Unconverted)". 
    2. Corresponding system log 
    Display the system log by calling transaction SM21. 
    Restrict the time interval to 10 minutes before and five minutes 
    after the short dump. Then choose "System->List->Save->Local File 
    (Unconverted)". 
    3. If the problem occurs in a problem of your own or a modified SAP 
    program: The source code of the program 
    In the editor, choose "Utilities->More 
    Utilities->Upload/Download->Download". 
    4. Details about the conditions under which the error occurred or which 
    actions and input led to the error. 
    System environment 
    SAP-Release 700 
    Application server... "terra" 
    Network address...... "172.16.1.198" 
    Operating system..... "Windows NT" 
    Release.............. "5.2" 
    Hardware type........ "4x Intel 801586" 
    Character length.... 16 Bits 
    Pointer length....... 32 Bits 
    Work process number.. 2 
    Shortdump setting.... "full" 
    Database server... "TERRA" 
    Database type..... "ORACLE" 
    Database name..... "DSM" 
    Database user ID.. "SAPSR3" 
    Char.set.... "C" 
    SAP kernel....... 700 
    created (date)... "Oct 23 2007 01:07:18" 
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10" 
    Database version. "OCI_10201_SHARE (10.2.0.1.0) " 
    Patch level. 133 
    Patch text.. " " 
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.." 
    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.... 8176 
    EM...... 37628064 
    Heap.... 0 
    Page.... 65536 
    MM Used. 31785376 
    | MM Free. 1656912
    =============================================
    Configuration:
    OS :Windows 2003 server.
    Solution Manager 7.0 SP15
    Oracle 10.2
    RAM - 2 GB
    Its bit urgent, Please help out us.
    Thanks in advance.
    Best Regards,
    Pratyusha

    Hi
    Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
    This error is related to ABAP program.
    Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system.

  • Exception condition "T681Z_MISSING" raised

    Hello,
    The SD collegaues are getting following dump while creating an invoice in transaction VF02.I am not able to find any help on SDN or any notes for the same.Please help.
    Short text
    Exception condition "T681Z_MISSING" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    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
    A RAISE statement in the program "SAPLV61Z" raised the exception
    condition "T681Z_MISSING".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    How to correct the error
    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:
    "RAISE_EXCEPTION" " "
    "SAPLV61Z" or "LV61ZF0T"
    "T681Z_SELECT"
    or
    "SAPLV61Z" "T681Z_MISSING"
    or
    "SAPMV60A " "T681Z_MISSING"
    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.
    Regards,

    Hello,
    Thanks for the help.
    I am not an ABAP person but still trying to write what i figured.
    The debugger hints at a sitution wherein a variable "ts_kappl" receives a value 'V' but after an assignment to other variable "available" the value of "available" changes to "0" somewhere.
    This results in a dump on trying to deliver the order for the functional people.
    Can anyone give some idea on this.
    Regards,

  • Exception condition "HIERARCHY_NOT_FOUND" raised. -  SAPLRRHI

    Hello all,
    My issue is very similar as the one described in thread : HIERARCHY_NOT_FOUND, but not solved in the other thread.
    I tried to update the system to SP21 as told in the topic, but the issue is still present :
    when I open a query with the query designer, I'm still having the same issue. Via the RSRT transaction I get the following error message :
    Short text
        Exception condition "HIERARCHY_NOT_FOUND" raised.
    What happened?
        The current ABAP/4 program encountered an unexpected
        situation.
    Error analysis
        A RAISE statement in the program "SAPLRRHI" raised the exception
        condition "HIERARCHY_NOT_FOUND".
        Since the exception was not intercepted by a superior
        program, processing was terminated.
        Short description of exception condition:
        For detailed documentation of the exception condition, use
        Transaction SE37 (Function Library). You can take the called
        function module from the display of active calls.
    Trigger Location of Runtime Error
        Program                                 SAPLRRHI
        Include                                 LRRHIU27
        Row                                     36
        Module type                             (FUNCTION)
        Module Name                             RRHI_ASOHIEDIR_READ
    I add that the query use a 0cust_sales based hierarchy, when (at the query level) I remove the time dependance the query works fine, but when I select "type of derivation" in the hierarchy display and use 0D_FC_LM1 : I get the error.
    (transaction RSTHJTMAINT--> 0D_FC_LM1 based on 0calmonth and use "first day)
    Thanks in advance for help.

    First of all, thanks Maxim to spend time on my issue, it is really appreciated (and sorry for the late answer, I did not have any computers during the week-end).
    I checked both tables (SE16 then "number of entries" button) : RSHIEDIR has 5 entries and RSRHIEDIR_OLAP has 9.
    So I go to my info-object 0cust_sales, hierarchy tab, "maintain hierarchy" button and reactivate the hierarchy (I only have one line available) and I get the message "There is no modified version for this hierarchy." When I check again the entries number in both tables : no change, (still 5 and 9).
    Please find bellow the abap code I get with the message (when I use RSRT) :
    Source Code Extract
    Line  SourceCde
        6 *"  EXPORTING
        7 *"     REFERENCE(E_S_HIEDIR) TYPE  RRHI_S_HIEDIR
        8 *"  EXCEPTIONS
        9 *"      HIERARCHY_NOT_FOUND
       10 *"----
       11   data: l_hiesid  type rrhi_hiesid,
       12         l_TMPJOIN type rs_bool.
       13
       14   CALL FUNCTION 'RRHI_HIESIDASO_GET'
       15     EXPORTING
       16       i_hiesid           = i_hiesid
       17     IMPORTING
       18       E_HIESID_ASO       = l_hiesid.
       19
       20   if l_hiesid < 0.
       21     l_tmpjoin = rs_c_false.
       22   else.
       23     l_tmpjoin = rs_c_true.
       24   endif.
       25
       26   CALL FUNCTION 'RRHI_HIEDIROLAP_READ'
       27     EXPORTING
       28       i_hiesid    = l_hiesid
       29       I_TMPJOIN   = l_tmpjoin
       30     IMPORTING
       31       E_S_HIEDIR  = E_S_HIEDIr
       32     EXCEPTIONS
       33       hierarchy_not_found = 1.
       34
       35   if sy-subrc <> 0.
    >>>>>     raise hierarchy_not_found.
       37   endif.
       38
       39 ENDFUNCTION.
    Thanks again and please let me know if you need more informations.

  • Exception condition "OPR_NOT_FOUND" raised, in CO02

    Hi all,
    We faced Runtime Errors         RAISE_EXCEPTION 
    Short text : Exception condition u201COPR_NOT_FOUNDu201D raised.
    When technical person checked he come up reason is entries field of table RESB-COUNTER is greater than entry of table AFVC-COUNTER
    We come across below SAP note which provide report to rectify above mention inconsistence in tables
    Link :[https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=182011]
    After running this it rectify the inconsistence ,But we are unable to find root cause why this inconsistence is being generated.
    We are on SAP ECC 6.0, I tried to search relevant Note but didnu2019t find any, so if someone faced same in past please share your experience also suggest possible cause of generation of this inconsistence.
    want to add we are using Exit for component allocation , which is doing allocations based on custom logic.
    but i checked it activating as well as by deactivating it , in both cases facing same error.
    Thanks
    Ritesh

    Hello
    The following notes are the most recent corrections for program error which can cause this issue on production orders:
    1541774     Reading master data: RAISE_EXCEPTION: OPR_NOT_FOUND
    1364818     Exception condition "OPR_NOT_FOUND" raised.
    Best regards
    Caetano Almeida

  • RAISE_EXCEPTION with exception condition "PARAMETER_INCOMLETE" raised.

    Hi,
    we are getting this Runtime error daily more than 10 times...please find below details.
    Runtime Errors         RAISE_EXCEPTION
    Date and Time          2010.09.22 04:04:18
    Short text
    Exception condition "PARAMETER_INCOMLETE" raised.
    Client.............. 700
    User................ "TME10X"
    Language key........ "V"
    Transaction......... "VA01 "
    Transactions ID..... "4C97B7A4B90A004DE10080000A281E0C"
    Program............. "SAPLZSDCHECK"
    Screen.............. "SAPMV45A 4001"
    error analysis
       A RAISE statement in the program "SAPLZSDCHECK" raised the exception
       condition "PARAMETER_INCOMLETE".
       Since the exception was not intercepted by a superior
       program, processing was terminated.
    Short description of exception condition:
      For detailed documentation of the exception condition, use
       Transaction SE37 (Function Library). You can take the called
       function module from the display of active calls.
    Can you please suggest us..
    we hope this is related to functional issue.. any suggesions from BASIS end.
    regards,
    balaram

    Hi Balaram,
    How did you resolve the problem?Please provide the solution so that I will be helpful for others
    Regards
    Uday

  • How to handle message "Exception condition "CNHT_ERROR_PARAMETER" raised"?

    Hi,
        Whenever I try to open Web Dynpro Comp./Intf->Views using transaction SE80, I am getting a short dump showing message "Exception condition 'CNHT_ERROR_PARAMETER' raised'. In the analysis, I have found that A RAISE statement in the program "CL_GUI_HTML_VIEWER============CP" raised the exception condition "CNHT_ERROR_PARAMETER". Since the exception was not intercepted by a superior program, processing was terminated. Can anyone help to get rid of this problem?
    Thanks & Regards.
    Deepjyoti

    hi,
    Looks like, ITS services are not fully active or not compeltely published.
    Check whether webgui services are active in SICF.(test service).
    Also, check all the ICM parameters.
    Regards
    Srinivas

  • Exception condition "RATE_NOT_FOUND" raised in DTP

    Hi All,
    I have tried to run the DTP. Some of the PSA data loaded to Target (DSO). But DTP request got failed.If I look into the Issue,I was able to see that "Exception condition "RATE_NOT_FOUND" raised".
    I have browsed some of the SDN forums.I came to know that it is related to Some Currency related Issue.
    Could you please help us on this.

    Hi Krishna, Prasath,
    We are facing the same issue. This issue is coming after our recent patch upgrade to SAP_BI 7.0 SP14. Last month we had activated the Transformation through RSDG_TRFN_ACTIVATE. Now the rule call this function module "RWS_CURRENCY_TRANSLATION", this FM was not previosly present in the system and came only after the upgrade. Report gives a short dump in this function module only with 'Rate Not Found' error.
    Our client has urgent regulatory reports to be submitted to government. We are under high pressure to resolve this issue. Any suggestion and help will be highly appreciated.
    Please assist.
    Regards,
    Aditya

Maybe you are looking for