UNCAUGHT_EXCEPTION CX_SXML_STATE_ERROR

Hi All
I'm getting the following error when running my print form and see that the error is generated in the following macro xml_open_tag i_folder_name. The function module in which this happens is FPCOMP_FOLDER_BEGIN and I'm not sure how to deal with this error. When I 'Generate Preview Data' in SFP->LAYOUT->EDIT->Defaults, the XML is tip-top, but calling the form from my print program generates this error. Any suggestions? Thank you.
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_SXML_STATE_ERROR
What happened?
    The exception 'CX_SXML_STATE_ERROR' was raised, but it was not caught anywhere
     along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CL_SXML_WRITER================CP' has to be
    terminated.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SXML_STATE_ERROR', was not caught
     in
    procedure "FPCOMP_FOLDER_BEGIN" "(FUNCTION)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Method 'IF_SXML_WRITER~OPEN_ELEMENT' cannot be called at this position in the
    XML stream

Hello,
if your form is working without the data and not with it, there is something malformed somewhere within:)) I can recommend you to experiment with your form context - one after another disable your context elements and find out which one causes the error.
I have experienced such problems when using certain DDIC types which were not processed correctly. I have never found the "right" solution, but I have found that if I replace the "bad" type with some other one which can hold the same information, it works and it is quick. That is what mattered the most for me.
Hope this helps a bit, Otto

Similar Messages

  • Early watch alert Dump:UNCAUGHT_EXCEPTION+ CX_DSVAS_API_CONTEXT_INSTANCE

    Hello All,
    I am facing issue while generating the early watch alert :
    In DSWP its showing ,DATA is available ;SAP earlywatch alert Session number :<>
    After processing button :  Start service processing
    Job schduling and getting failed Job Log:
    Job log overview for job:    SM:EXEC SERVICES 000000106120000 / 10520300
    Date       Time     Message text                                                                                Message class Message no. Message type
    02-06-2012 10:52:03 Job started                                                                                00           516          S
    02-06-2012 10:52:03 Step 001 started (program RDSMOPBACK_AUTOSESSIONS, variant &0000000000558, user ID BASISUSER)           00           550          S
    02-06-2012 10:52:03 MemSize Begin = 1368192   Bytes                                                                         DMD          000          I
    02-06-2012 10:52:05 Solution <000000106120000> "SID..." is being edited (Operations)                                       DSWP          438          S
    02-06-2012 10:52:05 <000000106120000> "SID..."(Operations)                                                                  DMD          000          I
    02-06-2012 10:52:05  ( EW_ALERT ) Session 2000000001331 for 02-13-2012 created (QDV)                                       DSWP          506          S
    02-06-2012 10:52:05 Difference "Create_Periodic_Services" = 278528                                                          DMD          000          I
    02-06-2012 10:52:05 Trying to perform session EC2000000001313                                                              DSWP          492          S
    02-06-2012 10:52:08 MODEL_KEY: SID <Installation Number> HANDLE: 6  MODEL_MODE: E  MODEL_VERSNR 00001 MODEL_CLASS: EWA Data Model      DMD          000          I
    02-06-2012 10:52:43 Internal session terminated with a runtime error (see ST22)                                             00           671          A
    02-06-2012 10:52:43 Job cancelled                                                                                00           518          A
    St22: Dump Log:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_DSVAS_API_CONTEXT_INSTANCE
    Date and Time          02-06-2012 10:52:43
    Short text
         An exception occurred that was not caught.
    What happened?
         The exception 'CX_DSVAS_API_CONTEXT_INSTANCE' was raised, but it was not caught
          anywhere along
         the call hierarchy.
         Since exceptions represent error situations and this error was not
         adequately responded to, the running ABAP program 'SAPLDSVAS_PROC' has to be
         terminated.
    Please post your valubale suuggestions and how to proceed further.
    Thanks
    Nekkalapu

    HI Arjun,
    Earlier (upto jan15th ) its working fine no issues generating earlywatch alerts .
    After 15th onwards i am facing this issue i have not done any chnages in configuration part.
    As per your suggestion I have checked the below points:
    1)transaction AGS_UPDATE is up to date ?
    Answer:AGS_UPDATE is updated (ALL availeble updates are downloaded) and its showing green color 3 options .
    2)able to connect to your satellite system via Trusted RFC or able to create sessions?
    Answer: Yes its generating sessions probelm while running dswp t code genarating sessions only.
    3)RTCCTOOL showing all green ?
    Answer:
    Five are showing in red and two are showing green
    Red:
    Addon upgrade ST-A/PI 01N_700SOL
    ST-A/PI Addon Supportpackage SP01
    Proc. after addon impl.
    Switch on digital content verification
    ST-PI Support Packages
    Green:
    Addon ST-PI 2008_1_700
    Collectors and TCOLL
    Kindly please suggest how to proceed further.
    Thanks
    Nekkalapu

  • Error while executing query on portal-SAPMSSY1 method : UNCAUGHT_EXCEPTION

    Hello all,
    I have created a quey and executed it on portal and everything just works fine. The query has few input varaibles at the start like fiscal year and some other inputs. I saved the query in my Portal favorites and then when I try to excute it from there it gives me a runtime BI error.
    Termination message sent ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION  MSGV1: SAPMSSY1  MSGV3: UNCAUGHT_EXCEPTION
    I guess it errors out because of the variable input part at the start of query.
    We already have note "950992" in the system so wonder what next now.
    Any inputs appreciated.
    Thanks,
    Kiran

    We are having the same issue too - we are SP13. Our query is built on a Infoset, and the problem comes with 0FISCPER variable, when we try to do a input help (F4) in Bex. this happens only when I use fiscper on queries bulit on INFOSETS, and it works perfectly alright with all other cubes.
    <i>System error in program CL_RSMD_RS_SPECIAL and form
    IF_RSMD_RS~READ_META_DATA-02 (see long text)
        Message no. BRAIN299
    Diagnosis
        This internal error is an intended termination resulting from a program
        state that is not permitted.
    Procedure
        Analyze the situation and inform SAP.
        If the termination occurred when you executed a query or Web template,
        or during interaction in the planning modeler, and if you can reproduce
        this termination, record a trace (transaction RSTT).</i>
        For more information about recording a trace, see the documentation for
        the trace tool environment as well as SAP Note 899572.
    and in portal, it gets to the point of variable screen and then throws a error msg.
    <i>ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
      MSGV1: SAPMSSY1
      MSGV3: UNCAUGHT_EXCEPTION</i>
    Message was edited by:
            voodi
    Message was edited by:
            voodi

  • Runtime Errors UNCAUGHT_EXCEPTION and Exception CX_RSR_COB_PRO_NOT_FOUND

    Hi ,
    When i tried to load data into my standard cube the following short dump error occure.
    The data was updated to PSA but while updating to further data target (my standard cube) the following error occured:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_RSR_COB_PRO_NOT_FOUND
    Date and Time          2010.12.13 10:20:48
    Short text
         An exception occurred that was not caught.
    What happened?
         The exception 'CX_RSR_COB_PRO_NOT_FOUND' was raised, but it was not caught
          anywhere along
         the call hierarchy.
         Since exceptions represent error situations and this error was not
         adequately responded to, the running ABAP program
          'CL_RSR========================CP' has to be
         terminated.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_RSR_COB_PRO_NOT_FOUND', was not
         caught and
        therefore caused a runtime error.
        The reason for the exception is:
        0REQUEST is not a valid characteristic for InfoProvider

    Please check the infoobject 0REQUEST, whether it is in active state, if not acivate it.
    Check for 0REQUEST Object in Infocube level at characteristics tab, if it is not available try to add this characteristic to cube.
    if 0REQUEST is not available, install it from the content and include it in the cube.
    rgds, Ghuru

  • Runtime Error : UNCAUGHT_EXCEPTION

    Hi Solman Experts,
    While downloading softwares through Maintenace Optimizer ( Solution Manager ),I am getting below error..
    First Error :
    Function module /SDF/AL_MAP_TRANSID_LOGH does not exist.
    The Maintenance Optimizer can automatically determine which files you require to update the ABAP and Java software components of your systems.
    The search is performed for all instances of the selected systems flagged as relevant.
    I have already checked in service market place and apply the SAP note 1135893 and we have activate the some components (BC Set)
    See Note 898614 after that i am getting big problem.
    Second Error : ( ABAP Dump )
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SOCM_NOT_IMPLEMENTED
    Date and Time          31.03.2008 15:04:31
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_SOCM_NOT_IMPLEMENTED' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_CHM1_CHANGE_REQU_INSTANCE==CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_SOCM_NOT_IMPLEMENTED', was not
    caught and
    therefore caused a runtime error.
    The reason for the exception is:
    An exception occurred
    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:
    *"UNCAUGHT_EXCEPTION" "CX_SOCM_NOT_IMPLEMENTED"
    "CL_CHM1_CHANGE_REQU_INSTANCE==CP" or "CL_CHM1_CHANGE_REQU_INSTANCE==CM009"
    "IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION"*
    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... "ALBE0510"
    Network address...... "10.201.180.10"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "ALBE0510"
    Database type..... "MSSQL"
    Database name..... "SP0"
    Database user ID.. "sp0"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Oct 23 2007 00:33:51"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 133
    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...... 41898400
    Heap.... 0
    Page.... 40960
    MM Used. 33604960
    MM Free. 4099184
    User and Transaction
    Client.............. 001
    User................ "KONS222"
    Language key........ "E"
    Transaction......... "DSWP "
    Transactions ID..... "AE21FFDCBA44F199AB15005056836080"
    Program............. "CL_CHM1_CHANGE_REQU_INSTANCE==CP"
    Screen.............. "RDSMOP_MAIN 0100"
    Screen line......... 5
    Information on where terminated
    Termination occurred in the ABAP program "CL_CHM1_CHANGE_REQU_INSTANCE==CP" -
    in "IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION".
    The main program was "RDSMOP_MAIN ".
    In the source code you have the termination point in line 612
    of the (Include) program "CL_CHM1_CHANGE_REQU_INSTANCE==CM009".
    Source Code Extract
    Line
    SourceCde
    582
    conditions_ok =  cl_socm_integration=>false.
    583
    ENDIF.
    584
    ENDIF.
    585
    586
    WHEN 'S_USER_CHECK'.
    587
    conditions_ok =  cl_socm_integration=>true.
    588
    CALL METHOD cl_sm_base_sender=>get_assigned_suser
    589
    EXPORTING
    590
    i_no_dialogue      = 'X'
    591
           IMPORTING
    592
             e_suser            = e_suser
    593
             e_partner_no       = lv_parnr
    594
    EXCEPTIONS
    595
    no_user_assigned   = 1
    596
    no_customer_number = 2
    597
    OTHERS             = 3.
    598
    IF sy-subrc  = 1 OR sy-subrc = 3.
    599
    conditions_ok =  cl_socm_integration=>false.
    600
    ENDIF.
    601
    WHEN 'NO_CRTCL_OBJ'.
    602
    conditions_ok = me->check_crtcl_obj( ).
    603
    WHEN '0NO'.
    604
    conditions_ok =  cl_socm_integration=>false.
    605
    WHEN '0YES'.
    606
    conditions_ok =  cl_socm_integration=>true.
    607
    WHEN '0BREAK'.
    608
    BREAK-POINT.                                         "#EC NOBREAK
    609
    WHEN space.
    610
    avoid exception since it is the default in table   TSOCM_COND_MAPP
    611
    WHEN OTHERS.
    >>>>>
    RAISE EXCEPTION TYPE cx_socm_not_implemented.
    613
    ENDCASE.
    614
    615
    ENDMETHOD.
    Please suggest. Thanks in Advance...
    Regards,
    Suresh Kumar

    Hi Ruben,
    I have Implemented  both notes now i am getting differt error...
    Error is : Error No customer numbers in transaction AISUSER ...
    Message Number: SOLMAN_SAP_BACKEND016
    Diagnosis
    There are no entries with a customer number in the 'Customer Number' field in the table AISUSER.
    System Response
    You cannot get customer number-specific RFC destinations.
    Procedure
    Maintain these entries manually or start the report
    SMBI_AISUSER_VAR_MIG to copy any existing customer number from the table AISDK_CF_OSS_USR.
    Please suggest..
    Thanks in Advance..
    Regards,
    Suresh Kumar
    Edited by: suresh k on Apr 15, 2008 3:15 PM

  • ABAP/4 processor: UNCAUGHT_EXCEPTION while activation

    Hi All,
    I am getting this error "ABAP/4 processor: UNCAUGHT_EXCEPTION" while the activation of DSO. I am attaching the dump
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SDB_ORA_PROGRAM_ERROR
    Date and Time          19.12.2008 03:02:53
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_SDB_ORA_UPDATE_STATS=======CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
    caught and
    therefore caused a runtime error.
    The reason for the exception is:
    An error occurred in the program:
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
    "CL_SQL_STATEMENT==============CP",
    specifically in line 31 of the (include) program
    "CL_SQL_STATEMENT==============CM002".
    The cause of the exception was:
    ORA-04031: unable to allocate 62208 bytes of shared memory ("shared
    pool","DBMS_STATS","PL/SQL MPCODE","BAMIMA: Bam Buffer")
    ORA-06508: PL/SQL:
    could not find program unit being called: "SYS.DBMS_STATS"
    ORA-06512: at line 1
    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:
    "UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR"
    "CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I"
    "UPDATE_STATS"
    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... "gwpsapci"
    Network address...... "10.220.136.60"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "0005E935D600"
    Character length.... 8 Bits
    Pointer length....... 64 Bits
    Work process number.. 30
    Shortdump setting.... "full"
    Database server... "de08u1642"
    Database type..... "ORACLE"
    Database name..... "GWP"
    Database user ID.. "SAPR3"
    Char.set.... "en_US.ISO8859-1"
    SAP kernel....... 700
    created (date)... "Aug 24 2008 21:05:40"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 175
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    Memory consumption
    Roll.... 16128
    EM...... 25139520
    Heap.... 0
    Page.... 24576
    MM Used. 12500304
    MM Free. 4256248
    User and Transaction
    Client.............. 950
    User................ "ZZSUPPORT"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "494AFB8FEB5A00D6E10080000ADC883C"
    Program............. "CL_SDB_ORA_UPDATE_STATS=======CP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "CL_SDB_ORA_UPDATE_STATS=======CP" -
    in "UPDATE_STATS".
    The main program was "RSPROCESS ".
    In the source code you have the termination point in line 40
    of the (Include) program "CL_SDB_ORA_UPDATE_STATS=======CM00I".
    The program "CL_SDB_ORA_UPDATE_STATS=======CP" was started as a background job.
    Job Name....... "BI_PROCESS_ODSACTIVAT"
    Job Initiator.. "E442207"
    Job Number..... 03030600
    Source Code Extract
    Line
    SourceCde
    10
    i_tablnm      = i_tablnm
    11
    i_signi       = i_signi
    12
    i_thresh_mod  = i_thresh_mod
    13
    i_degree      = i_degree
    14
    i_histo       = i_histo
    15
    i_granularity = i_granularity
    16
    i_cascade     = i_cascade
    17
    i_force       = i_force
    18
    i_flush       = i_flush
    19
    i_connection  = i_connection.
    20
    21
        Update Statistics
    22
    IF l_r_upd_stats->p_skip_upd IS initial.
    23
    CASE l_r_upd_stats->p_granularity.
    24
    WHEN 0. " DEFT
    25
    IF l_r_upd_stats->global_update_stats( ) = 'NO'.
    26
    l_r_upd_stats->part_update_stats( ).
    27
    ENDIF.
    28
    WHEN 1. " ALL
    29
    l_r_upd_stats->global_update_stats( ).
    30
    WHEN 2. " GLOBAL
    31
    l_r_upd_stats->global_update_stats( ).
    32
    WHEN 3. " PART
    33
    l_r_upd_stats->part_update_stats( ).
    34
    WHEN OTHERS. " AUTO
    35
    l_r_upd_stats->global_update_stats( ).
    36
    ENDCASE.
    37
    ENDIF.
    38
    39
    CATCH cx_sql_exception INTO l_r_exception.
    >>>>>
    RAISE EXCEPTION TYPE cx_sdb_ora_program_error
    41
    EXPORTING previous = l_r_exception.
    42
    CLEANUP.
    43
    TRY.
    44
    CATCH cx_sql_exception INTO l_r_exception.
    45
    RAISE EXCEPTION TYPE cx_sdb_ora_program_error
    46
    EXPORTING previous = l_r_exception.
    47
    ENDTRY.
    48
    ENDTRY.
    49
    50
    ENDMETHOD.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    0
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Process Variant Run
    SY-MSGTY
    E
    SY-MSGID
    DA
    SY-MSGNO
    300
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20081219
    SY-UZEIT
    030252
    SY-XPROG
    SAPCNVE
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    6 METHOD       CL_SDB_ORA_UPDATE_STATS=======CP    CL_SDB_ORA_UPDATE_STATS=======CM00I    40
    CL_SDB_ORA_UPDATE_STATS=>UPDATE_STATS
    5 FUNCTION     SAPLRSDU_UTIL_ORA                   LRSDU_UTIL_ORAU01                      86
    RSDU_ANALYZE_TABLE_ORA
    4 FUNCTION     SAPLRSDU_UTIL                       LRSDU_UTILU01                          38
    RSDU_ANALYZE_TABLE
    3 FUNCTION     SAPLRSSM_PROCESS                    LRSSM_PROCESSU30                     1476
    RSSM_PROCESS_ODSACTIVATE
    2 METHOD       CL_RSSM_ODSACTIVATE===========CP    CL_RSSM_ODSACTIVATE===========CM007   117
    CL_RSSM_ODSACTIVATE=>IF_RSPC_EXECUTE~EXECUTE
    1 EVENT        RSPROCESS                           RSPROCESS                             144
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       6 Ty.          METHOD
    Name  CL_SDB_ORA_UPDATE_STATS=>UPDATE_STATS
    I_TABLNM
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    I_SIGNI
    5775488
    0
    0
    I_THRESH_MOD
    0
    0000
    0000
    I_DEGREE
    3
    0000
    0003
    I_HISTO
    2
    0
    I_GRANULARITY
    0
    0000
    0000
    I_CASCADE
    0
    0000
    0000
    I_FORCE
    2
    0
    I_FLUSH
    X
    5
    8
    I_CONNECTION
    222222222222222222222222222222
    000000000000000000000000000000
    SPACE
    2
    0
    L_R_UPD_STATS
    |
    | 0000000F |
    | 80000027 |
    | %_DUMMY$$ |
    |  |
    | 2222 |
    | 0000 |
    | SY-REPID |
    | CL_SDB_ORA_UPDATE_STATS=======CP |
    | 4455445454555445455545533333334522222222 |
    | 3CF342FF21F504145F34143DDDDDDD3000000000 |
    | SY-XFORM |
    | CONVERSION_EXIT |
    | 444545544454545222222222222222 |
    | 3FE65239FEF5894000000000000000 |
    | L_R_EXCEPTION |
    |
    E0000001
    80000037
    SYST
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    SY
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    %_EXCP
    E0000001
    70000038
    %_SPACE
    2
    0
    SYST-REPID
    CL_SDB_ORA_UPDATE_STATS=======CP
    4455445454555445455545533333334522222222
    3CF342FF21F504145F34143DDDDDDD3000000000
    No.       5 Ty.          FUNCTION
    Name  RSDU_ANALYZE_TABLE_ORA
    I_ALL_COLUMNS
    2
    0
    I_FORCE_ESTIMATE
    X
    5
    8
    I_FORCE_STATISTICS
    2
    0
    I_PERCENTAGE
    1
    0000
    0001
    I_PERCENTAGE_SPECIFIED
    X
    5
    8
    I_TABLNM
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    I_TEMP_TABLE
    2
    0
    I_T_TABLNM
    Table[initial]
    C_PROCESSED
    2
    0
    SY-REPID
    SAPLRSDU_UTIL_ORA
    5454554555544545422222222222222222222222
    310C2345F549CFF2100000000000000000000000
    <L_TABLNM>
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    SYST-REPID
    SAPLRSDU_UTIL_ORA
    5454554555544545422222222222222222222222
    310C2345F549CFF2100000000000000000000000
    %_SPACE
    2
    0
    SY
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    %_DUMMY$$
    2222
    0000
    L_SIGNI
    5775488
    0
    0
    L_PARALLEL_DEGREE
    3
    0000
    0003
    L_HISTO
    2
    0
    L_FLUSH
    X
    5
    8
    SY-ONCOM
    S
    5
    3
    No.       4 Ty.          FUNCTION
    Name  RSDU_ANALYZE_TABLE
    I_FORCE_ESTIMATE
    X
    5
    8
    I_FORCE_STATISTICS
    2
    0
    I_PERCENTAGE
    1
    0000
    0001
    I_TABLNM
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    I_TEMP_TABLE
    2
    0
    I_T_TABLNM
    Table[initial]
    SYST-REPID
    SAPLRSDU_UTIL
    5454554555544222222222222222222222222222
    310C2345F549C000000000000000000000000000
    RSDU_C_OBJTYPE-VIEW
    VIEW
    5445
    6957
    L_DBFUNC
    RSDU_ANALYZE_TABLE_ORA
    554554444554554444545422222222
    2345F1E1C9A5F412C5FF2100000000
    SY-XFORM
    CONVERSION_EXIT
    444545544454545222222222222222
    3FE65239FEF5894000000000000000
    L_PERCENTAGE_SPECIFIED
    X
    5
    8
    %_VIASELSCR
    0
    4
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_PROCESSED
    2
    0
    RS_C_FALSE
    2
    0
    SY-SUBRC
    0
    0000
    0000
    SCREEN
    %_17NNS0000194530_%_%_%_%_%_%_
    2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
    5F17EE30000194530F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
    SY-REPID
    SAPLRSDU_UTIL
    5454554555544222222222222222222222222222
    310C2345F549C000000000000000000000000000
    L_MESSAGE
    222222222222222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000000000000000
    No.       3 Ty.          FUNCTION
    Name  RSSM_PROCESS_ODSACTIVATE
    I_CRT_ACTIVATION
    2
    0
    I_DROP_CREA_SEC_IND
    2
    0
    I_INSTANCE
    ODSA_4C7HUKHW8WV06KLJFFYZP95BW
    445453434544535533444445553345
    F431F43785B8787606BCA669A09527
    I_JOBNAME
    BI_PROCESS_ODSACTIVAT
    44555444555445445454522222222222
    29F02F3533FF43134961400000000000
    I_LOG_ID
    4C7HSJQKN58AR2DG5NSOGNB5O
    3434545443345344345444434
    43783A1BE58122475E3F7E25F
    I_NO_CONDENSE
    2
    0
    I_ODSOBJECT
    OD13ITM3
    443345432222222222222222222222
    F41394D30000000000000000000000
    I_PARENT_BATCH_ID
    222222222222222222222222222222
    000000000000000000000000000000
    I_SERIALIZE
    2
    0
    I_T_REQUEST_SEL
    Table[initial]
    I_VARIANT
    OD13ITM3_ACTIVATE
    443345435445454542222222222222
    F41394D3F134961450000000000000
    I_WITH_COMMIT
    X
    5
    8
    E_ERROR
    2
    0
    E_RNR
    ODSR_4C7HULKAVPVJRPAS8MAP3IYWS
    445553434544455545545344534555
    F432F43785CB1606A20138D1039973
    E_T_ACTIVATE_RNR
    Table[initial]
    E_T_ERROR_RNR
    Table[initial]
    E_T_MSG
    Table IT_18345[3x704]
    CLASS=CL_RSSM_ODSACTIVATEMETHOD=IF_RSPC_EXECUTE~EXECUTEDATA=L_T_MSG_PROC
    Table reference: 123
    TABH+  0(20) = 07000000A05FD4B0000000000000000000000000
    TABH+ 20(20) = 0000007B000047A900000003000002C0FFFFFFFF
    TABH+ 40(16) = 0400012500000D40001024C401800000
    store        = 0x07000000A05FD4B0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 123   (0x0000007B)
    label        = 18345 (0x000047A9)
    fill         = 3     (0x00000003)
    leng         = 704   (0x000002C0)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000050
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000A05750F0
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 10517 (0x00002915)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    E_T_ODSR_RNR
    Table[initial]
    L_LINES
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    SCREEN
    %_17NNS0000194530_%_%_%_%_%_%_
    2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
    5F17EE30000194530F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
    SY-REPID
    SAPLRSSM_PROCESS
    5454555455544455222222222222222222222222
    310C233DF02F3533000000000000000000000000
    SY-MSGID
    DA
    44222222222222222222
    41000000000000000000
    G_CHANGED
    2
    0
    SPACE
    2
    0
    SY-MSGNO
    300
    333
    300
    SY-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    L_PERFORMED_ANALYZE
    2
    0
    G_R_ALV_GRID
    F0000000
    F0000000
    RS_C_TRUE
    X
    5
    8
    L_S_ODSTABNAME-M_TAB
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    SYST
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    <%_TABLE_RSDS>
    RSAU_C_PROTCLASS
    1234
    3333
    1234
    SYST-REPID
    SAPLRSSM_PROCESS
    5454555455544455222222222222222222222222
    310C233DF02F3533000000000000000000000000
    G_BUTTON_REQUDEL
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_SPACE
    2
    0
    No.       2 Ty.          METHOD
    Name  CL_RSSM_ODSACTIVATE=>IF_RSPC_EXECUTE~EXECUTE
    I_VARIANT
    OD13ITM3_ACTIVATE
    443345435445454542222222222222
    F41394D3F134961450000000000000
    I_EVENT_START
    RSPROCESS
    55554445522222222222222222222222
    2302F353300000000000000000000000
    I_EVENTP_START
    4BO77YTX6F8UVLQ22AEHHYIPO
    3443355534355453344445454222222222222222222222222222222222222222
    42F7794866856C1221588990F000000000000000000000000000000000000000
    I_JOBCOUNT
    03030600
    33333333
    03030600
    I_BATCHDATE
    20081218
    33333333
    20081218
    I_BATCHTIME
    030306
    333333
    030306
    I_T_PROCESSLIST
    Table IT_123[18x528]
    PROGRAM=RSPROCESSDATA=G_T_PROCESSLIST
    Table reference: 37
    TABH+  0(20) = 07000000A02596D8000000000000000000000000
    TABH+ 20(20) = 000000250000007B0000001200000210FFFFFFFF
    TABH+ 40(16) = 040000740000116800102CC421800000
    store        = 0x07000000A02596D8
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 37    (0x00000025)
    label        = 123   (0x0000007B)
    fill         = 18    (0x00000012)
    leng         = 528   (0x00000210)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000069
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000A0262CF0
    pgHook       = 0x07000000A0258600
    idxPtr       = 0x07000000A0259788
    shmTabhSet   = 0x0000000000000000
    id           = 93    (0x0000005D)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32    (0x00000020)
    lineAlloc    = 32    (0x00000020)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    I_LOGID
    4C7HSJQKN58AR2DG5NSOGNB5O
    3434545443345344345444434
    43783A1BE58122475E3F7E25F
    I_T_VARIABLES
    Table[initial]
    I_SYNCHRONOUS
    2
    0
    I_SIMULATE
    2
    0
    I_REPAIR
    222222222222222222222222222222
    000000000000000000000000000000
    I_BATCHID
    222222222222222222222222222222
    000000000000000000000000000000
    E_INSTANCE
    ODSA_4C7HUKHW8WV06KLJFFYZP95BW
    445453434544535533444445553345
    F431F43785B8787606BCA669A09527
    E_STATE
    2
    0
    E_EVENTNO
    00
    33
    00
    E_HOLD
    2
    0
    SY-REPID
    CL_RSSM_ODSACTIVATE===========CP
    4455554544544545454333333333334522222222
    3CF233DFF4313496145DDDDDDDDDDD3000000000
    <%_L003>-RNR
    L_T_REQUESTS
    Table[initial]
    L_S_REQUESTS
    222222222222222222222222222222
    000000000000000000000000000000
    SY-SUBRC
    0
    0000
    0000
    SYST-REPID
    CL_RSSM_ODSACTIVATE===========CP
    4455554544544545454333333333334522222222
    3CF233DFF4313496145DDDDDDDDDDD3000000000
    ICON_GREEN_LIGHT
    @08@
    4334
    0080
    L_JOBNAME
    BI_PROCESS_ODSACTIVAT
    44555444555445445454522222222222
    29F02F3533FF43134961400000000000
    L_S_SELE-NO_CONDENSE
    2
    0
    L_S_ODS-OBJECT
    OD13ITM3
    443345432222222222222222222222
    F41394D30000000000000000000000
    L_S_SELE-ODSACTSERIAL
    2
    0
    L_ERROR_PROC
    2
    0
    L_T_MSG_PROC
    Table IT_18345[3x704]
    L_T_MSG
    Table[initial]
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    G_VARIANT
    OD13ITM3_ACTIVATE
    443345435445454542222222222222
    F41394D3F134961450000000000000
    G_TYPE
    ODSACTIVAT
    4454454545
    F431349614
    %_DUMMY$$
    2222
    0000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    G_OBJECT
    CL_RSSM_ODSACTIVATE
    445555454454454545422222222222
    3CF233DFF431349614500000000000
    G_INSTANCE
    222222222222222222222222222222
    000000000000000000000000000000
    SY
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    %_SPACE
    2
    0
    %_REPAIR_%_APP_%
    222222222222222222222222222222
    000000000000000000000000000000
    G_STATE
    2
    0
    G_EVENTID
    RSPROCESS
    55554445522222222222222222222222
    2302F353300000000000000000000000
    G_HOLD
    2
    0
    G_EVENTPARM
    4BO77YTX6F8UVLQ22AEHHYIPO
    3443355534355453344445454222222222222222222222222222222222222222
    42F7794866856C1221588990F000000000000000000000000000000000000000
    G_JOBCOUNT
    03030600
    33333333
    03030600
    G_BATCHDATE
    20081218
    33333333
    20081218
    G_EVENTNO
    00
    33
    00
    G_BATCHTIME
    030306
    333333
    030306
    G_T_VARIABLES
    Table[initial]
    G_T_PROCESSLIST
    Table IT_123[18x528]
    %F007017_1000
    Log ID (Internal Use Only)
    46624422467676662576246672222222222222222222222222222222222222222222222222222222222
    CF7094089E452E1C05350FEC99000000000000000000000000000000000000000000000000000000000
    G_LOGID
    4C7HSJQKN58AR2DG5NSOGNB5O
    3434545443345344345444434
    43783A1BE58122475E3F7E25F
    G_CHAIN
    ZLIS_13_VDITM
    5445533554454222222222222
    AC93F13F6494D000000000000
    G_REPAIR
    222222222222222222222222222222
    000000000000000000000000000000
    G_BATCHID
    INFO_4C7HUKA7PY9ANY239LWNF76M4
    444453434544355344533345443343
    9E6FF43785B170991E9239C7E676D4
    Internal notes
    The termination was triggered in function "raiseExcp"
    of the SAP kernel, in line 2099 of the module
    "//bas/700_REL/src/krn/runt/abexcp.c#7".
    The internal operation just processed is "EXCP".
    Internal mode was started at 20081219030246.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    => 64 bit R/3 Kernel
    => 64 bit AIX Kernel
    => Heap limit      = unlimited
    => Stack limit     = unlimited
    => Core limit      = 1073741312
    => File size limit = unlimited
    => Heap address  = 0x1154fc6a0
    => Stack address = 0xfffffffffffb080
    => Stack low     =  0xfffffffffffb080
    => Stack high    =  0xffffffffffff880
    => Stack Trace:
         AixStack() at 0x1000a2474
         CTrcStack2() at 0x1000a256c
         rabax_CStackSave__Fv() at 0x1000d0e3c
         ab_rabax() at 0x1000cd81c
         raiseExcp__F6HeadId() at 0x100429ba0
         ab_jexcp__Fv() at 0x100428d30
         ab_extri__Fv() at 0x10038e6dc
         ab_xevent__FPCc() at 0x100ab5cc4
         ab_trigg__Fv() at 0x100ab59b0
         ab_run() at 0x1014d42dc
         N_ab_run() at 0x100ed3f4c
         dynpmcal() at 0x100ed2d40

    HI karthik..
    The Error Msg is due to insufficient memory while storing the Data in Database(i,e ODS) and this error UNCAUGH EXCEPTION will come due to " like there is an exception raised but no code to catch it(to activate the ODS)".
    so chk the problem with the Basis People... those guys can give clear info pertaining to this kind of  problems...
    Genereally in our case we raise ticket to Basis people..
    hope useful....
    cheers
    Sukhai..

  • UNCAUGHT_EXCEPTION while executing Infospoke

    Hi All,
    I have created Openhub destination in BI 7.0 on sales cube. I tried extract file to application server with the default path DIR_HOME which system automaticaly gives. It was success. But I want to give different path in the application server to download data, So I have created Logical file in transaction FILE and used the path which I required and tried to download. When I am scheduling DTP, I am getting error message as below.
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_RSB_WRITE_ERROR
    Date and Time          04/05/2007 01:56:46
    Any clue about this error. Please help.
    Thanks in advance.
    Jayasudha

    It has nothing to do with authorization..you missed out some parameters in the FILE transaction side...make sure they are correct..
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8d/3e4ec2462a11d189000000e8323d3a/content.htm
    Hope it Helps
    Chetan
    @CP..

  • UNCAUGHT_EXCEPTION when a user is executing a variable selection in WT

    Hi Experts,
    There is strange problem to one User, when ever she uses the Varibale selection for 0FUNCT_LOC in Portal, the systems throws the below UNCAUGHT_EXCEPTION, in the Webtemplate screen.
    When i Checked that is displayed in  *Root Cause*,  it is showing as follows.
    " The initial exception that caused the request to fail was: 
    Termination message sent
    ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
      MSGV1: SAPMSSY1
      MSGV3: UNCAUGHT_EXCEPTION
    com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent
    ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
      MSGV1: SAPMSSY1
      MSGV3: UNCAUGHT_EXCEPTION
    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:172)
    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:128)
    And other messages that were displayed are below.
    ABEND: Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
    ABEND: System error in program CL_RSBOLAP_VARIABLE_CHARACTERI and form No hierarchy available (see long text)
    Here the problem is that, while others users have no problem with  the same Webtemplate,that is there is no exception raised for Functional location for them (And also when i checked from my side in Webtemplate, there was no problem displayed at my side too )
    But when We created the copy of the user id (With same roles and profiles) again it has showed the same problem again.
    We also checked in the Roles and Authorizations for that user, but could find no problem.
    Also the user is able to access the Function Loaction variable selection in Bex Analyzer without any problems.
    But  only when she uses the selection in Portal she is getting UNCAUGHT_EXCEPTION.
    Could anyone please help me how to trace where the problem is, and why it is happening only for that user.
    And when there is no problem at Bex Analyzer side, why the exception is raised at Portal.
    Thanks in advance for helping
    Regards
    Raghu

    Thanks Javier,
    But it could not help me to fix the issue, the problem occurs to only one user, when she selects Functional Location variable (Hierarchy Infoobject) in Portal. For me and others we do not have problem, but when i copy replica that user id with problem, and execute at my side i too see the same problem, any idea why?
    Do we need to do any user specific configuration at portal side, for case of Hier Infoobject variables incase?.
    Any help on this would be appreciated.
    Thanks a lot.
    Raghu

  • Getting dump Uncaught_Exception while giving filter values

    Hi Friends,
    We have recently upgraded the system from BW 3.5 to BI 7.0, and SP17 we have applied.
    Now the problem is we are not able give the filter values
    while executing queries. It's giving the dump UNCAUGHT_EXCEPTION.
    Error analysis:
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RS_PROGRAM_ERROR', was not caught
    and therefore caused a runtime error.
    The reason for the exception is:
    Error in BW: Error creating tmp table
    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:
    "UNCAUGHT_EXCEPTION" "CX_RS_PROGRAM_ERROR"
    "CL_RSBOLAP_BICS_SERVICES======CP" or "CL_RSBOLAP_BICS_SERVICES======CM003"
    "HANDLE_UNCAUGHT_EXCEPTION"
    Awaiting for your suggestions.
    Regards
    Udaya

    Hello everybody,
    we fixed our problem.
    It was a customizing issue.
    Switch on history in SPRO by "Activating personalization in BeX"
    regards
    Joerg

  • Error in ABAP Mapping (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION)

    Hi ,
      Scenario:  Manually Purchase Order is created, automatically Sales Order should be created in the Target System through PI,
                       I have used Message Mapping which is working fine for single Customer and Vendor,
                       For Multiple Customers and Vendors i am using one ZTABLE, Only Message Mapping is not  sufficient to my requirement.
                      Now i am using both Message Mapping and   ABAP Mapping  at a time in Interface Mapping. I created the class and                done  the   development., whene  i run the scenario i am getting the error as below,
    *<SAP:Stack>Error in mapping program ZCL_SD_IDTO_POSO (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference</SAP:Stack>*
      *<SAP:Retry>M</SAP:Retry>*
      *</SAP:Error>* 
    Please let me know.
    Best Regards
    Vamsi

    Have u seen the ABAP mapping guide?
    Refer this series to the ABAP mapping section.https:///people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii
    It will be very handy and useful.

  • While trying to load data Runtime Err UNCAUGHT_EXCEPTION Except.CX_RSR_X_ME

    Hi
    We are on BI.7 patch SAPKW70015 BI_CONT 703 - 0007 SAPKIBIIP7 and multi source system BI server. One is for R/3 it is already working and  another is for new IS Retail.
    While trying to load data to inventory (Z-cube) for first time in production system we get the following error :
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_RSR_X_MESSAGE
    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:
        "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
        "SAPLRRMS" or "LRRMSU13"
        "RRMS_X_MESSAGE"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
    Information on where terminated
        Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
        The main program was "RSBATCH_EXECUTE_PROZESS ".
        In the source code you have the termination point in line 73
        of the (Include) program "LRRMSU13".
        The program "SAPLRRMS" was started as a background job.
    Line  SourceCde
       43     BREAK-POINT.
       44     SET EXTENDED CHECK ON.
       45   ENDIF.
       46
       47   IF i_abend EQ rs_c_false.
       48 *... Nachricht an den Message-Handler schicken
       49
       50     DATA: l_type  TYPE smesg-msgty.
       51
       52 *... S-Meldung wenn kein Handler initialisiert
       53     IF g_active IS INITIAL.
       54       l_type = 'S'.
       55     ELSE.
       56       l_type = 'W'.
       57     ENDIF.
       58
       59     CALL FUNCTION 'RRMS_MESSAGE_HANDLING'
       60       EXPORTING
       61         i_class  = 'BRAIN'
       62         i_type   = l_type
       63         i_number = '299'
       64         i_msgv1  = i_program
       65         i_msgv2  = i_text.
       66   ELSE.
       67     DATA: l_text  TYPE string,
       68           l_repid TYPE syrepid.
       69
       70     l_repid = i_program.
       71     l_text  = i_text.
       72
    >>>>>     RAISE EXCEPTION TYPE cx_rsr_x_message
       74           EXPORTING text = l_text
       75                  program = l_repid.
       76   ENDIF.
       77
       78 ENDFUNCTION.
    The other data loads are working fine in the production system.
    We searched a lot on the forum and got various solutions  But none of them are working fine for us.
    Please suggest.
    Thanks you for your help.
    Ramana P

    Are you trying this load manually or through process chain?
    if process chain , the file should be placed in application server.
    chk if the file is closed b4 triggering the infopack.
    try loading other flat file load for different datasource and chk.
    Ramesh

  • UNCAUGHT_EXCEPTION Error in Our ECC Production Server

    Hi Gurus,
    We are getting UNCAUGHT_EXCEPTION ABAP Runtime error from last 3 months in our ECC Production Server, Daily it was throwing upto 200 times. we changed alvgrid parameters aslo no use. can you anybody suggest about this error
    please find below error details also
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_WD_GENERAL
    Date and Time          16.02.2010 15:37:12
    Short text
    An exception occurred that was not caught.
    What happened?
         The exception 'CX_WD_GENERAL' was raised, but it was not caught anywhere along
         the call hierarchy.
         Since exceptions represent error situations and this error was not
         adequately responded to, the running ABAP program
          'CX_WD_GENERAL=================CP' has to be
         terminated.
    Error analysis
         An exception occurred which is explained in detail below.
         The exception, which is assigned to class 'CX_WD_GENERAL', was not caught and
         therefore caused a runtime error.
    WebDynpro Exception:
    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:
    "UNCAUGHT_EXCEPTION" "CX_WD_GENERAL"
    "CX_WD_GENERAL=================CP" or "CX_WD_GENERAL=================CM00
    "RAISE"
    Regards,
    Balaram

    Hi..
    problem solved..
    regards,
    balaram

  • UNCAUGHT_EXCEPTION while creating Purchase Order in Extended classic SRM 7

    Hi Experts,
    I am getting the following message while creating Manual or SC/PO in Extended classic Scenario (SRM7.0 with ECC 6.0)
    Pl suggest what could be the problems.
    Error application is coming up.
    20091130
    E2001
    172331
    wicomp03
    http://wicomp03.wipro.com:8003/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/
    UNCAUGHT_EXCEPTION
    An exception has occurred in the procurement document methods
    Form: DETERMINE_MATNR of program SAPLBBP_BD_DRIVER_46A
    Form: FILL_BAPI_POITEM of program SAPLBBP_BD_DRIVER_46A
    Form: MAP_BBP_DPO_TO_BAPI of program SAPLBBP_BD_DRIVER_46A
    Function: BBP_DPO_TO_BAPI_MAP of program SAPLBBP_BD_DRIVER_46A
    Method: IF_EX_BBP_DOC_CHECK_ICC~BBP_DOC_CHECK of program /SAPPSSRM/CL_PO_TOLERANCE=====CP
    Form: DOC_CHECK_BADI_CALL of program SAPLBBP_PD
    Form: PROCDOC_CROSS_CHECKS of program SAPLBBP_PD
    Form: PROCDOC_UPDATE of program SAPLBBP_PD
    Function: BBP_PROCDOC_UPDATE of program SAPLBBP_PD
    Method: /SAPSRM/IF_PDO_BASE~SAVE of program /SAPSRM/CL_PDO_BO_PO==========CP
    http://wicomp03.wipro.com:8003/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/
    Regards,
    Mohan Raj

    The same error should appear in ST22. Run the transaction and locate this error entry. Then set an external break point at the statement before the dump and run the scenario in debug mode. You should be able to identify the error from there.

  • Run time Error : UNCAUGHT_EXCEPTION

    Hi Team
    Pls reply to resolve the below error
    When we are uploaded TB through flexible upload  and then Test run for Data Collection for that Cons unit, we got the below Run time error:
    Runtime Errors         UNCAUGHT_EXCEPTION                                                           Except.                CX_UCI_NO_CHECK     
    Short dump has not been completely stored                                                                               
    Short text                                                                               
    An exception occurred that was not caught.                                                   
    What happened?                                                                               
    The exception 'CX_UCI_NO_CHECK' was raised, but it was not caught anywhere                   
         along                                                                               
    the call hierarchy.                                                                               
    Since exceptions represent error situations and this error was not                           
        adequately responded to, the running ABAP program                                            
         'CL_UC_DATASTREAM==============CP' has to be                                                
        terminated.                                                                               
    Error analysis                                                                               
    An exception occurred which is explained in detail below.                                    
        The exception, which is assigned to class 'CX_UCI_NO_CHECK', was not caught and              
        therefore caused a runtime error.                                                            
        The reason for the exception is:                                                             
        An exception occurred                                                                               
    Missing Handling of Application Exception                                                        
        Program                                 UCUWB000                                             
    Trigger Location of Exception                                                                    
        Program                                 CL_UC_DATASTREAM==============CP                     
        Include                                 CL_UC_DATASTREAM==============CM003                  
        Row                                     150                                                  
        Module type                             (METHOD)                                             
        Module Name                             DTS_READ_TRANSACTION_DATA                            
    Source Code Extract                                                                               
    Line
    SourceCde                                                                               
    120
                 it_hry_field            = it_char_node                                         
      121
                 it_hry_field_attr       = it_char_attr_node                                    
      122
                 it_hry_node             = lt_hry_node                                          
      123
                 it_hry_attr_node        = lt_hry_attr_node                                     
      124
                 i_authority_check       = l_authority_check                                    
      125
                 i_keydate               = i_keydate                                            
      126
                 it_hry_nodename         = lt_hry_nodename                                      
      127
                 it_hry_attr_nodename    = lt_hry_attr_nodename                                 
      128
                 i_packagesize           = i_packagesize                                        
      129
                 i_cursor_mode           = i_cursor_mode                                        
      130
               importing                                                                        
      131
                 et_hry_data             = lt_hry_data                                          
      132
                 e_end_of_data           = e_done                                               
      133
                 et_message              = lt_message1                                          
      134
               changing                                                                               
    135
                 ct_data                 = ct_data                                              
      136
               exceptions                                                                       
      137
                 no_authorization        = 1.                                                   
      138
                                                                                    139
             if sy-subrc is not initial.                                                        
      140
               move-corresponding syst to ls_message2.                                          
      141
               raise exception type cx_uci_no_authorization                                     
      142
                  exporting ds_message = ls_message2.                                           
      143
             endif.                                                                               
    144
                                                                                    145
             if lt_message1 is not initial.                                                     
      146
               loop at lt_message1 into ls_message1.                                            
      147
                 move-corresponding ls_message1 to ls_message2.                                 
      148
                 insert ls_message2 into table lt_message2.                                     
      149
               endloop.                                                                         
    >>>>>
               raise exception type cx_uci_no_check                                             
      151
                  exporting dt_message = lt_message2.                                           
      152
             endif.                                                                               
    153
                                                                                    154
             call method dts_process_hry_result                                                 
      155
               exporting                                                                        
      156
                 it_hry_node          = lt_hry_node                                             
      157
                 it_hry_attr_node     = lt_hry_attr_node                                        
      158
                 it_hry_nodename      = lt_hry_nodename                                         
      159
                 it_hry_attr_nodename = lt_hry_attr_nodename                                    
      160
                 it_hry_data          = lt_hry_data                                             
      161
               importing                                                                        
      162
                 et_node_data         = et_node_data.                                           
      163
                                                                                    164
        call method lo_tx_data->read_data_from_infoprov                                      
      165
          exporting                                                                               
    166
            i_comp_s_field         = i_comp_s_char                                           
      167
            i_comp_s_kfig          = i_comp_s_kfig                                           
      168
            it_field               = it_char                                                 
      169
            it_kfig                = it_kfig                                                 
    Pls revert me immediately how to resolve the issue, i already do the following functionality as per OSS Note 1074424
    thanks & regards
    Madhu yl

    Hi Sanjyot,
    The solution is resolved by technical team ,
    I don't have suport documents to fulfill, they said they added data files and this run time occurs due to space problem
    Thanks
    Madhu
    Edited by: Madhu YL on Jun 10, 2009 1:32 PM

  • ABAP Programming error UNCAUGHT_EXCEPTION

    HI All,
    I am trying to install BI content  infocube with grouping before and after
    Category               ABAP Programming Error
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_RSD_INFOPROV_NOT_FOUND
    ABAP Program           CL_RSO_EXCEL_WORKBOOK_PROXY===CP
    Application Component  BW-WHM-MTD
    Date and Time          02.01.2007 04:42:08
    SAP Release..... 740
    SAP Basis level 0005
    Regards
    Kuzhanthaivel

    Hi,
    you can install one by one.
    if your facing any problem use the do only necessary objects
    please find the below doc it will give an idea.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/102906a4-f13d-2e10-7199-ce316ff254b8?overridelayout=true
    Thanks,
    Phani,

Maybe you are looking for