ODS Activation Error - ABAP dump - UNCAUGHT_EXCEPTION

[Former Member]

Dear Gurus:

Yes, I have ods activation problem. Below I'll describe my ODS and humbly ask for your guidance ...

<b>BW 3.1 SP 23 ... from SPAM T-code</b>

SAPKB62055 SAP Basis Component Basis Support Pkg.

SAPKA62055 Cross-Application Component Appl. Interface SP

SAPKW31023 Business Information Warehouse BW Support Package

<b>Info object:</b> 2 info objects. 1 for key and 1 for data

both info objects have master data and text.

both info objects are characteristics (CHAR) - 10 width

<b>ODS infomation:</b>

1. Bex Reporting enabled - I guess this is the culprit

2. Automatic QA set to green

3. NOT Automatic activation - earlier yes, but I disabled it in order to simulate the problems.

Loading from text infosource. only simple comma separated text file with 1 row only and two columns only. Full update and no delta enabled info source / source system combination.

When I activate the ODS, I have these ABAP dump. I will cut paste only important information ... (in my perspective) to conserve spaces...

-

---

<b>Runtime Error : UNCAUGHT_EXCEPTION

Exception CX_RSR_X_MESSAGE </b>

Occurred on 15.08.2007 at 18:35:25

An exception that could not be caught occurred.

<b>What happened? </b>

The exception 'CX_RSR_X_MESSAGE' 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, 'SAPLRRMS', had to

be terminated.

<b>Error analysis</b>

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assinged to the class 'CX_RSR_X_MESSAGE', was not

caught, which led to a runtime error.

The reason for this exception is:

... No text available for this exception ...

<b>How to correct the error </b>

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"UNCAUGHT_EXCEPTION" CX_RSR_X_MESSAGEC

"SAPLRRMS" or "LRRMSU13"

"RRMS_X_MESSAGE"

-

---

-

---

<b>Information on where terminated</b>

The termination occurred in the ABAP program "SAPLRRMS" in "RRMS_X_MESSAGE". The main program was "RSODSACT1 ".

The termination occurred in line 76 of the source code of the (Include)program "LRRMSU13" of the source code of program "LRRMSU13" (when calling the editor 760).

The program "SAPLRRMS" was started as a background job.

-

---

Thanks for reading and I hope a good a solutions.

PS: Points will be awarded for sucessful answers. You can check my repuation on earlier postings.

Regards,

BWAS

[Former Member]

Hi Gurus:

I do not have problem activating ODS (not activate data), no problem with info object assignments. Both infoobjects has SID and no problem with SID numbering

I also search OSS notes and found nothing with this keyword:

"ODS Activation UNCAUGHT_EXCEPTION"

Regards,

BWAS

[Former Member]

Hi Bwas,

Even I had the same problem.Ask your basis guys.they will be able to solve it.

If i remember it right, sm59--and change some settings.

hope this helps

[Former Member]

Hi,

Does this ODS gave any warnings while ODS activation( not ODS data activation)saying this infoobjects selections to data fileds or key fields are incorrect. Like this infoobject must be key field or this infoobject be data field. Then change assignment of infoobjects in key & data fields.

Regards

Robyn.

[Former Member]

Hi...check an OSS note

[Former Member]

Hi,

For any reason, the system could not write to a log monitor.

Try other ODS, is it okay???