BI Error - UNCAUGHT_EXCEPTION

Can you help with this ERROR.. Thanks in advance
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_SDB_ORA_PROGRAM_ERROR
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-00604: error occurred at recursive SQL level 1#ORA-01654: unable to extend
index SYS.I_HH_OBJ#_INTCOL# by 128 in tablespace SYSTEM#ORA-06512: at
"SYS.DBMS_STATS", line 13159#ORA-06512: at "SYS.DBMS_STATS", line
13179#ORA-06512: at line ...
BI

Thank you all for posting immediately.. now the questions are..
1. How do I find out which table space is issue with.. Because there is no DBA here, I need to tell exactly basis team, like which table space is errored out, and how much space that should be allocated.
2. Is there any manual which says for proper functioning of BI System, there should be so much SPACE should exists always in the system ? Is BI Production support manual, that can tell me what needs to be checked on a daily basis.
Thanks again
BI

Similar Messages

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

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,

Job DIM_OBSERVER is getting canceled with with a runtime error UNCAUGHT_EXCEPTION

Dear Experts,
Job DIM_OBSERVER is getting canceled with with a runtime error UNCAUGHT_EXCEPTION. Below are the details of runtime error.
Category
ABAP Programming Error
Runtime Errors
UNCAUGHT_EXCEPTION
Except.
CX_UJA_ADMIN_ERROR
ABAP Program
CL_UJA_MD_QUERY_OPT===========CP
Application Component EPM-BPC-NW-ADM
Date and Time
02.08.2014 23:35:46
I am unable to find related note and solution for the same. any help would be much appreciated.
Thanks,
Akbar.

Hi Akbar,
I believe this issue is coming up in BPC.
But could you please provide some more detailed information like when exactly(after performing which step) is this error occurring?
BR
Prabhith

Business content error UNCAUGHT_EXCEPTION CX_RSR_X_MESSAGE

Hi all,
I am on 7.0 and when I install Business content I get the following dump.
Also when I monitor my job it in the job log I can see " The object is not allowed to be empty" coming up several times and then just abruptly dumps.
I have checked the notes and forums but nothing matches to my problem...also we understand that we are on a low SP package 10 which I guess is the big problem.
Any advice,
DUMP:
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_RSR_X_MESSAGE
Date and Time          08.12.2008 15:05:52
Short text
     An exception occurred that was not caught.
What happened?
     The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
     terminated.

Hi
Did you resolve this issue. Because we are facing the same problem. wheniam now installing demo content.
Thanks

Runtime Errors       " UNCAUGHT_EXCEPTION ...... While loading data

Hi Gurus: Need yoyur help to resolve the loading issue (Data Mart)
Scenario:
    Loading data from BW layer to BI layer - Cube to Cube loading of data.
    Data loaded in DW layer cube with no issues. However, gives the following error when loading to
    BI layer cube (It is 1:1 mapping excpt for couple of convesrion routines on satndard objects such
    as Material Division, periods and Unit).
Message:
     *Runtime Errors         UNCAUGHT_EXCEPTION*
     *Exception               CX_RSR_X_MESSAGE*
This happens in Program - 'SAPLRRMS'; Include -"LRRMSU13"
What happened?
    The exception 'CX_RSR_X_MESSAGE' was raised, but it was not caught anywhere
    along the calhierarchy Since exceptions represent error situations and this error was
    not adequately responded to, the running ABAP program 'SAPLRRMS' has to be
    terminated.
We are aware of the following 2 OSS notes reference:
855424 - Error in Formula Compiler
872193 - Run Time Error 'UNCAUGHT_EXCEPTION' during upload
Any other solution for this? please let me know.
Thanks.......SMaalya

please replicate DM system.
-- sameer

Runtime Errors UNCAUGHT_EXCEPTION

Hi All,
while activating DSO the backgroung job getting cancelled with Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_SDB_ORA_PROGRAM_ERROR.
and the status of the request is in green.
my system service pack level is .
SP LEVEL IS 17
and the job log is as below.
Job started
Step 001 started (program RSODSACT1, variant &0000000000019, user ID HPDEV0105)
Activation is running: Data target ZDATSTOR, from 197 to 197
Overlapping check with archived data areas for InfoProvider ZDATSTOR
Data to be activated successfully checked against archiving objects
ABAP/4 processor: UNCAUGHT_EXCEPTION
Job cancelled .
could you please suggest me the solution for the above issue.
Thanks & regards
Yogee

Hi Yogeeraj,
        Check below SAP note
SAP note No: 1152831
Thanks,
Vijay.

Could not activate InfoObject (Runtime Error = UNCAUGHT_EXCEPTION)

Dear Experts,
I got stuck on activating an existing InfoObject-A after changing one attribute.
Situation
- there was no data in the InfoObject at all.
- change attribute from InfoObject-B1 to InfoObject-B2
- activate InfoObject-A
- got short dump
Short dump detail
- Runtime Error = UNCAUGHT_EXCEPTION (An exception that could not be caught occurred.)
- Except. = CX_SY_SQL_ERROR
- What happened?
The exception 'CX_SY_SQL_ERROR' was raised but was not caught at any stage in the call hierarchy.
Since exceptions represent error situations, and since the system could not react adequately to this error, the current program, 'RSDRS_MSSQL_ROUTINES', had to be terminated.
Any suggestion for resolving this case would be appreciated.
Thank you very much.
-WJ-

Hi,
try to activate the infoobject with following program using transaction SE38:
RSDG_IOBJ_ACTIVATE
Hope you will get solution to your problem

Runtime Errors UNCAUGHT_EXCEPTION ..CX_SDB_ORA_PROGRAM_ERROR

I am currently working on Bi 7. I am trying to delete master data from infoobject
0RPM_IDGU, but when i try saving the saving Infoobject after delting the data, it gives me following error.
<b>Runtime Errors UNCAUGHT_EXCEPTION
Exception : CX_SDB_ORA_PROGRAM_ERROR</b>
Please help.

Hi,
here some notes: https://websmp108.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=998904&_NLANG=EN
https://websmp108.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=975948&_NLANG=EN
If they don't help, raise a message at http://www.service.sap.com
regards
Siggi

ABAP Run time error "UNCAUGHT_EXCEPTION" "CX_RSR_PROPAGATE_X"

Hi Gurus,
*This error occured after loading the Hierarchy & while saving the Hierarchy.*
Short text
    An exception occurred that was not caught.
What    happened?
    The exception 'CX_RSR_PROPAGATE_X' 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_RRHI_INCL_CREATOR==========CP' has to be
    terminated.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_PROPAGATE_X', was not caught
     and
therefore caused a runtime error.
    The reason for the exception is:
    An error occurred when getting data from the processor.
The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_RRHI_INCLTAB_LOCKED", which was raised in the program
     "CL_RRHI_INCL_CREATOR==========CP",
    specifically in line 33 of the (include) program
     "CL_RRHI_INCL_CREATOR==========CM00W".
    The cause of the exception was:
An exception has occurred
Plz advice.
Regards,
Shree.

Hi,
Refer to the Note:
Note 1130023 - Temp hierarchy join:CX_RSR_PROPAGATE_X, CL_RRHI_INCL_CREATOR
Symptom
You select the indicator "Temporal hierarchy join" for an InfoObject. You try to activate the InfoObject. This may result in the termination: UNCAUGHT_EXCEPTION, CX_RSR_PROPAGATE_X. The termination occurs at position: CL_RRHI_INCL_CREATOR, SAVEHIER. The main program is: RSDG_IOBJ_ACTIVATE.
Alternatively, the system may issue an error message during activation, which indicates a conflict with the maximum name length that is allowed.
Other terms
CL_RRHI_INCL_CREATOR, CX_RSR_PROPAGATE_X, temporal hierarchy join, rsd1, InfoObject
Reason and Prerequisites
This problem is caused by a program error.
Solution
SAP NetWeaver 7.1 BI
           Import Support Package 05 for SAP NetWeaver 7.1 BI (BI Patch 06 or SAPKW71006) into your BI system. The Support Package is available when Note 1126007 "SAPBINews BI 7.1 Support Package 6", which describes this Support Package in more detail, is released for customers.
SAP NetWeaver 7.0 BI
           Import Support Package 17 for SAP NetWeaver 7.0 BI (BI Patch 17 or SAPKW70017) into your BI system. The Support Package is available when Note 1106569 "SAPBINews BI 7.0 Support Package 17", which describes this Support Package in more detail, is released for customers.
In urgent cases, you can implement the correction instructions as an advance correction.
You must first read Note 875986, which provides information about transaction SNOTE.
To provide information in advance, the notes mentioned above may already be available before the Support Package is released. In this case, the short text of the note still contains the words "Preliminary version".
Hope this hleps
regards
KP

Runtime Error "UNCAUGHT_EXCEPTION" in &VIEW_ELEMENT_TYPE

Hello,
I got a big problem, when I by accident configered with sap-config-mode the FITE_EXPENSES-application's LAYOUT_VIEW. I entered text in the Width-field and saved the configuration. The application run into the error in program CX_WDR_ADAPTER_EXCEPTION======CP. This is the note:
"Adapter error in &VIEW_ELEMENT_TYPE& "FORWARD_TOP" of view "FITV_FPM.LAYOUT_VIEW": The CS length specification in property "IFUR_NW5_BUTTON~WIDTH" contains invalid characters"
So, how to reset or correct the configuration setting, when aplication crashes every time I start it.
Seppo

>
Seppo Somppi wrote:
> Hello,
>
> I got a big problem, when I by accident configered with sap-config-mode the FITE_EXPENSES-application's LAYOUT_VIEW. I entered text in the Width-field and saved the configuration. The application run into the error in program CX_WDR_ADAPTER_EXCEPTION======CP. This is the note:
> "Adapter error in &VIEW_ELEMENT_TYPE& "FORWARD_TOP" of view "FITV_FPM.LAYOUT_VIEW": The CS length specification in property "IFUR_NW5_BUTTON~WIDTH" contains invalid characters"
> So, how to reset or correct the configuration setting, when aplication crashes every time I start it.
>
> Seppo
Hi,
Go the the layout of the view LAYOUT_VIEW of your component. Try to delete the text from the property 'WIDTH' of the element in the view.
Let me know if that works.
Regards
Prasenjit

Error:UNCAUGHT_EXCEPTION while loading data with exception CX_RSR_X_MESSAG

Hi,
Ours is a fresh installation..
When i am loading for the first time till PSA it is successful..
As HR data sources are 3.5 datasources, i am loading cube via infopackage..
When i start the load to cube it is giving me dump with exception CX_RSR_X_MESSAG.
i checked note 615389 which talks about "buffering of number range object BIM9999998". the 0REQID is not buffered, but it does not throw any error msg in RSRV to correct the error..
and one more note 1157796 which talks about patches with version BI 7.0.
Now we are in BI 730 with heighest level 0005.
Not sure how to solve this error
Any ideas?

S Simran wrote:
Hi,
>
> Ours is a fresh installation..
>
> When i am loading for the first time till PSA it is successful..
>
> As HR data sources are 3.5 datasources, i am loading cube via infopackage..
>
> When i start the load to cube it is giving me dump with exception CX_RSR_X_MESSAG.
>
> i checked note 615389 which talks about "buffering of number range object BIM9999998". the 0REQID is not buffered, but it does not throw any error msg in RSRV to correct the error..
>
> and one more note 1157796 which talks about patches with version BI 7.0.
>
> Now we are in BI 730 with heighest level 0005.
>
> Not sure how to solve this error
>
> Any ideas?
What's your SP? Are you having any master data updates left unattended? Check the Master data objects, check the flows. Related SAP Notes : 914304 / Check 967202(SP10) and 998673(SP11), 1157796, 763203 and 615389
Edited by: Arun Bala G on Feb 12, 2012 9:50 PM

Runtime Error-UNCAUGHT_EXCEPTION CX_RSR_X_MESSAGE

Hi All,
I am getting below runtime error when I am trying to load data from a flat file to Infocube.I am on Bi 7.0 and it is a totally new server.
Error message:
The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
terminated.
Information on where terminated
    Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 82
    of the (Include) program "LRRMSU13".
Please tell me what could be the issue.Is it related to some patch issue???
Regards,
Kshitij

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

BI Error - UNCAUGHT_EXCEPTION

Similar Messages

Maybe you are looking for