0TCT_C01 short dump when loading data to the InfoCube

[Former Member]

Hello

Seeing below issue with technical content infocubes in SAP BI. Activate the content Cubes, loaded master data but when trying to load data to 0TCT_C01 or 0TCT_C02 InfoCube(Delta) the load fails.

Data is loaded till PSA but does not go through update rules and just hangs up with a short dump. The request stays in yellow status and just hangs. Tried to debug the update rules could not find anything.

Thanks

Swetha

[roland_szajko]

Hi Sweetha

It would be good if you could attach the complete dump as a textfile to the post. The function RRMS_X_MESSAGE is the general error handling for all bex-ot related problems.

There might be an inconsistency with the aggregates or even a characteristic might be inactive as well.

Some possible problems:

• 0REQUEST is not active or it doesn't references to 0REQUID (Note 1157796)
• The number range for 0REQUID is incorrect (should be corrected in RSRV)
• The number range object for one of the characteristics doesn't exists.  In this case it is enough to reactivate the characteristic.

br

Roland

[MGrob]

Hi

Most likely caused by a program error. Have a look at note  1882150  - Dump SUBMIT_IN_ITAB_ILL_STRUCTURE during data load and see if it's relevant for you. Otherwise share the dump you get from st22.

hope that fixes it

Martin

[Former Member]

Hi Martin,

The note looks like it is applicable for 7.03 and higher versions. Is there any note that can be applied for BW 7.02?

For some reason data is not updated to InfoCube.Update PSA, transfer rules, update rules are all green but then the update to infocube step just hangs.

Below is the short dump:

Category               ABAP Programming Error
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_RSR_X_MESSAGE
ABAP Program           SAPLRRMS
Application Component  BW-BEX-OT
Date and Time          11/18/2013 14:44:08

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.

Error analysis
     An exception occurred which is explained in detail below.
     The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
      and
     therefore caused a runtime error.
     The reason for the exception is:
     No text available for this exception

Missing Handling of Application Exception
     Program                                 RSMO1_RSM2

Trigger Location of Exception
     Program                                 SAPLRRMS
     Include                                 LRRMSU13
     Row                                     82
     Module type                             (FUNCTION)
     Module Name                             RRMS_X_MESSAGE

Source Code Extract

Line  SourceCde

    52           ID 'KEY'  FIELD 'BI0'
    53           ID 'DATA' FIELD l_field.
    54
    55
    56   IF i_abend EQ rs_c_false.

Thanks

Swetha