Exception Condition "Table_not_Exist" raised in query Level.

Hi,
I have a Hirarchy data in my Object level as below
X
->   X1
     ->-> X001 (Values or at this level)
I have created a variable on this object in the query level ( Entry is Optional) and executing the query.then I am getting the error mesage  Exception Condition "Table_not_Exist" raised.
If I am putting the Variable Value as x* then query is displaying values properly .If i am not giving any values then error is coming. and without variable also executing but values in the output showing X001 lvel.
So plz get back to me with the solution.
"Appritiate Your help inadvance"
Regards
Ram.
Edited by: Ramakanth Deepak Gandepalli on Dec 21, 2009 10:59 AM

Hi,
Please check the link below:
http://www.saptechies.com/sap-47-installation-error-ora00942-table-or-view-does-not-exist/
-Vikram Srivastava

Similar Messages

  • Exception condition "TABLE_NOT_EXISTS" raised.

    Hello all,
    when I try to open certain queries in BEx 7.0, I get the following error....
    An error occured while communicating with BI Server.
    As a result of this error, the system has been disconnected from the BI Server.
    Detailed Description:
    Exception condition "TABLE_NOT_EXISTS" raised.
    Any ideas on this? Pls help.
    Thanks,SD

    Laufzeitfehler         RAISE_EXCEPTION
    Datum und Zeit         12.05.2009 14:47:47
    ABAP-Kurzdump ist nicht komplett abgespeichert (zu groß)
    Kurztext
         Ausnahmebedingung "TABLE_NOT_EXISTS" ausgelöst
    Was ist passiert?
         Das laufende ABAP-Programm ist auf eine nicht vorhergesehene Situation
         gestoßen.
    Fehleranalyse
         In dem Programm "SAPLRSDU_PART" wurde durch eine RAISE-Anweisung die Exception
         (Ausnahmebedingung) "TABLE_NOT_EXISTS" ausgelöst.
         Da die Exception nicht durch ein in der Aufrufhierarchie darüber-
         liegendes Programm abgefangen ist, wurde die Verarbeitung abgebrochen.
         Kurztext zur Ausnahmebedingung:
         Tabelle unbekannt
         Eine ausführliche Dokumentation der Ausnahmebedingung finden Sie
         über Transaktion SE37 (Funktionsbibliothek). Den gerufenen
         Funktionsbaustein können Sie der Anzeige der aktiven Aufrufe
         entnehmen.
    Auslösestelle des Laufzeitfehlers
         Programm                                SAPLRSDU_PART
         Include                                 LRSDU_PARTU02
         Zeile                                   47
         Modultyp                                (FUNCTION)
         Modulname                               RSDU_PARTITIONS_INFO_GET
    Ausschnitt Quelltext
    Zeile Quelltext
       17     l_processed       TYPE rs_bool.
       18
       19   l_processed = rs_c_true.
       20
       21 * get name of the DBMS-specific function module .
       22   CALL FUNCTION 'RSDU__FUNCTION_NAME'
       23     EXPORTING
       24       i_function       = 'RSDU_PARTITIONS_INFO_GET'
       25     IMPORTING
       26       e_dbsys_function = l_dbfunc.
       27
       28 * DB-dependent implementation of 'RSDU_PARTITIONS_INFO_GET'
       29   CALL FUNCTION l_dbfunc
       30     EXPORTING
       31       i_tablnm              = i_tablnm
       32     IMPORTING
       33       e_partype             = e_partype
       34       e_partkey             = e_partkey
       35       e_ts_part_info        = e_ts_part_info
       36     CHANGING
       37       c_processed           = l_processed
       38     EXCEPTIONS
       39       table_not_exists      = 1
       40       table_not_partitioned = 2
       41       OTHERS                = rsdu_c_exceptions-inherited.
       42
       43 * generic error handling
       44   CASE sy-subrc.
       45     WHEN 0.
       46     WHEN 1.
    >>>>>       RAISE table_not_exists.
       48     WHEN 2.
       49       RAISE table_not_partitioned.
       50     WHEN OTHERS.
       51       RAISE inherited_error.
       52   ENDCASE.
       53
       54 *----
       55 * DB-independent implementation
       56 *----
       57
       58 ENDFUNCTION.

  • 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 "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 "INFOCUBE_NOT_FOUND" raised.

    Hi
    Merry Christmas
    An error occured in the communication with the BW server. Due to this , the connection had to be closed.
    Detail Description :
    Exception condition "INFOCUBE_NOT_FOUND" raised.
    This error appear when I execute my query in BEx Analyzer. The virtual cube (which is used in the query) already exist in system.
    Anyone know what is the actual problem and how to solve it?
    Thanks.

    Please check SAP Note 1055704, which may be relevant.
    If you are getting dump as well, please check SAP note 1068154.
    Thanks
    PS: Please award points if the answer is useful.

  • RFC_ERROR_SYSTEM_FAILURE: Exception condition "FAILED" raised on Publish of

    Hi,
    When i preview my Bi query in potal i am getting following exception :
    RFC_ERROR_SYSTEM_FAILURE: Exception condition "FAILED" raised
    Earlier i had already published some query which is working properly, but the new one which i am publishing now is giving me above exception.
    Regards,
    Jigar Oza

    Hi,
    Check the target on which the query is built is active in the same server.

  • 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 "CNTL_ERROR" raised for u201CSAPLBEA_OBJ_UF02u201D

    Dear All
    I am getting the error {Exception condition "CNTL_ERROR" raised.} for the program. SAPLBEA_OBJ_UF02. The billing document is being posted to accounting but I am getting the above error when I view the accounting document through  /BEA/CRMB11 (display accounting document). We are using CRM billing.
    Plz help
    Rgds
    Praveen

    Hello Praveen,
    Can you apply notes ;
    893175 Fixed CNTL_ERROR when using RFC-recorder in tRFC
    1303765 Query text or diagnosis text not displayed correctly
    thanks
    Willie

  • Exception condition "INCONSISTENCY" raised

    Hi Experts,
    Greetings!
    I was revising the configuration of my FG Inventory Report when I
    encountered this error after saving the Query Designer and running the BEx Analyzer:
    Exception condition "INCONSISTENCY" raised.
    Afterwards, I cannot able to continue working on BEx Query Designer on the report anymore because of the error.
    In the reporting tool ANALYZE_RSZ_TABLES in SE38, I got the following result:
    Table RSZELTXREF
    Unresolved relations between query elements.
    Missing elements in existing query components
    Critical error: listed query elements are parts of definitions of
    existing queries or query components. Elements are not found in the
    table RSZELTDIR in required objects version and can not be used.
    Further investigations are required at SAP. Create an OSS message for
    BW-BEX-ET-QDEF
    Missing element ELTUID
    48NRDU7QW9H30633XZDD0G9V3
    Check results:
    Exception condition INCONSISTENCY dump accesing listed components.
    List of affected query components:
    Technical Name: ZPP_JMV1_Q001
    Technical ID: 484ZV76Y10KGXAALQJ2K78YY9
    Component Type: REP
    Info Provider: ZPP_JMV1
    Package: ZBIDEV
    Created in: BID
    How should I fix the missing element?
    Missing element ELTUID
    48NRDU7QW9H30633XZDD0G9V3
    You assistance is appreciated.
    Thank you.
    Regards,
    Btup

    Hi,
    If You have an element in another system I would suggest to perform a transport of a query using this element from one system to the other.Just from the investigations done by you, I see that there is only 1 'missing' element which is used in other queries. Please find out in which queries exactly this element is used. This can be done using the same report ANALYZE_RSZ_TABLES (table RSZELTXREF).You will find
    'affected queries or query component'. This is WHERE-USED list for this 'missing' element. Check the existence and consistency of those queries in the QAS and if they are correct, You may simply transport them to this system.
    Rgds
    Manoj Kumar

  • Exception condition "PROBLEM_WITH_QUERY" raised.

    Hi Experts,
    I have  a problem when I Appended a ibase field to service contract search page and enhanced the eh_onsearch_btn where  I
    added the code for searching the service contract based on ibase if i search the  other than the ibase fields result is coming properly when I search provinding value to the search page it is giving below exception
        The following error occurred in system  : Exception condition "PROBLEM_WITH_QUERY" raised.
        The error occurred on application server  and in work process 4 .
        The termination type was: RABAX_STATE
        The ABAP call stack was:
        Method: MAKE_INSTANCE_VALID of program CL_CRM_REPORT_ACCRULE=========CP
        Method: MAKE_INSTANCE_VALID of program CL_CRM_REPORT_ACCRULE_ONEORDERCP
        Method: GET_INSTANCE of program CL_CRM_REPORT_ACCRULE=========CP
        Method: CREATE_ACCRULE of program CL_CRM_REPORT_QUESTION========CP
        Method: CONSTRUCTOR of program CL_CRM_REPORT_QUESTION========CP
        Function: CRM_BSP_OIC_1O_SEARCH_FROM_RF of program SAPLCRM_BSP_OIC_1O_SEARCH
        Method: GET_RESULT_GUIDS of program CL_CRM_Q1O_SEARCH=============CP
        Method: GET_RESULT_VALUES of program CL_CRM_Q1O_SEARCH=============CP
        Method: IF_CRM_QUERY_RUNTIME_BTIL~GET_DYNAMIC_QUERY_RESULT of program CL_CRM_QSRVCON_RUN_BTIL=======CP
        Method: EXECUTE_DYNAMIC_QUERY of program CL_CRM_INTLAY_BTIL============CP
    Answer will be appreciated.
    Thanks & Regards
    Chetan Agali.

    Is this parameter also present on the Genil Component ? If you are actually trying to query also on this parameter then this parameter should be present on the Genil. Only appending the query input structure would not help here.
    Regards
    Kavindra

  • 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

  • "Exception condition "CONTROL_FLUSH_ERROR" raised." during background jobs

    hi all,
    the program ZTEST is used for downloading a txt file into D: using GUI_DOWNLOAD. this program works fine but when I schedule this porgam in background jobs in tcode SM36 using "job wizard", i am getting errors as  Exception condition "CONTROL_FLUSH_ERROR" raised and the error analysis is as
    'A RAISE statement in the program "SAPLSFES " raised the exception condition "CONTROL_FLUSH_ERROR".
    Since the exception was not intercepted by a superior program
    in the hierarchy, processing was terminated.'
    How to rectify this error???
    points will be rewrded
    thanks in advance

    GUI_DOWNLOAD is a FM that is designed to download files by interation with the PC directories (only possible in foreground). If the file download is the requirement the u can use application server files for it.
    But if you are insisting on notepad and excel documents, then you have to use CLIP and EXECUTE function modules. Refer to Class CL_GUI_FRONTEND_SERVICES that has all the required methods

  • Error in BEx Analyzer Exception condition "HIERARCHY_NOT_FOUND" raised.

    When i run report 0FIAA_C02_Q1001 with input variable as  "My controlling area" i get this error.
    ERROR:
    Exception condition "HIERARCHY_NOT_FOUND" raised.
    ERROR Analysis:
    A RAISE statement in the program "SAPLRRH1" raised the exception
    condition "HIERARCHY_NOT_FOUND".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Please sugggest how to resolve this.
    HOw to see which hierarachy it is talking about?
    Thanks,
    Harika.
    Edited by: harikag on Oct 12, 2011 7:11 AM
    Edited by: harikag on Oct 12, 2011 7:12 AM

    HI
    FOr 0Costcenterinfoobject->attribute tab->no hierarhcies
                                             ->hierarchy tab->i see hierarchy tables are enabled.But when i click on
                                                 "MaintainHierachy" there are no hierrachies in it.
    For 0CO_AREA infoobject->attribute tab->0CCA_HIENM,0PCA_HIENM hierarchies are there.
                                             ->hierarchy tab->nothing is there.
    please help out.I didnt load 0COSTELMNT_0102_HIER master datasource in CO_IO.
    Is that the reason?

Maybe you are looking for

  • Query help first two rows

    i need to sort desc order by date and need to take two rows only id date 1 1/2/1994 2 2/2/2000 3 1/5/88 4 6/5/2006 i need out put like this id date 4 6/5/2006 2 2/2/2000 plz give query with good perfomence thanks

  • Can't update or factory restore Apple TV

    I noticed the Apple TV I just bought for my Living Room hadn't updated to 1.1 even though I'd ran the installer a couple of weeks ago. So I tried running it again - I gave it the "Update Now" prompt, it restarted and when it rebooted I was still stuc

  • "package java.xml.registry does not exist" error in NetBeans

    Hi all I'm using netbeans for developing webservices and and have to use JAXR. I have downloaded and installed jwsdp1.5. When I view the source code for the JAXR sample java files that accompany the java EE tutorial in the NetBeans IDE Source Editor,

  • Passing values of some chkboxes to a function. Function recieving NULLs:(

    Hi, My aim is to pass the values of some checkboxes on a JSP to a function. I performed these steps but the function is getting called with NULL values(noticed that while debugging). Could somebody please tell me what I have missed ? These are the st

  • Alignment issues in CF pages

    I have 2 pages in question. 1, located at www.salleboise.com/club_tournaments.cfm and the other at http://www.salleboise.com/tournament.cfm?tid=1&f=1&e=1 My question is this. Why does the text at the top of the page differ so much in positioning? I d