Runtime error when executing F4 help on 0FISPER or 0FISCYEAR

Question

Hi experts,
I got a problem on F4 help.
When executing F4 help on 0FISPER or 0FISCYEAR using tcode LISTCUBE,
abap dump occurs. The problem also exists when run query in BEx analyzer.
My BW version is NW2004s. And SAPKW70012 has been implemented.
Thanks very much for any advices.
<b>The error message when run in BEx analyzer:</b>
System error in program SAPLRRS2 and form EXTRA_FIELDS_SET-01- (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).
    For more information about recording a trace, see the documentation for
    the trace tool environment as well as SAP Note 899572.
<b>And the ABAP dump log:</b>
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_RSR_PROPAGATE_X
Date and Time          2007.04.28 15:08:47
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_RS_BASE====================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_PROPAGATE_X', was not caught
and
therefore caused a runtime error.
The reason for the exception is:
No text available for this exception
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_SY_NO_HANDLER", which was raised in the program
"CL_RSMD_RS_BUILD_QUERY========CP",
specifically in line 1 of the (include) program
"CL_RSMD_RS_BUILD_QUERY========CM00Y".
The cause of the exception was:
An exception with the type CX_RS_SQL_ERROR_SILENT occurred, but was neither
handled locally, nor declared in a RAISING clause
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_RS_SQL_ERROR_SILENT", which was raised in the program
"CL_RSDRS_SQL_QUERY============CP",
specifically in line 288 of the (include) program
"CL_RSDRS_SQL_QUERY============CM00J".
The cause of the exception was:
No text available for this exception
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 32 of the (include) program
"CL_SQL_STATEMENT==============CM004".
The cause of the exception was:
Invalid object name 'T009C'.
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_PROPAGATE_X"
"CL_RS_BASE====================CP" or "CL_RS_BASE====================CM005"
"X_PROPAGATE"
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... "sapdev2"
Network address...... "192.168.1.74"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "SAPDEV2"
Database type..... "MSSQL"
Database name..... "BW1"
Database user ID.. "bw1"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Sep 1 2006 00:19:17"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 75
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"
Memory consumption
Roll.... 16192
EM...... 14617568
Heap.... 0
Page.... 163840
MM Used. 4553264
MM Free. 663776
User and Transaction
Client.............. 100
User................ "HANDLCR"
Language key........ 1
Transaction......... "LISTCUBE "
Program............. "CL_RS_BASE====================CP"
Screen.............. "SAPMSHLP 0600"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "CL_RS_BASE====================CP" -
in "X_PROPAGATE".
The main program was "GP9QWV49ZUMYUSW6JLZIZ85P81N ".
In the source code you have the termination point in line 12
of the (Include) program "CL_RS_BASE====================CM005".
Source Code Extract
Line
SourceCde
1
METHOD X_PROPAGATE .
2
3
DATA: l_r_x TYPE REF TO cx_rs_no_check.
4
5
TRY.
6
l_r_x ?= i_r_root.
7
CATCH cx_root.
8
CLEAR l_r_x.
9
ENDTRY.
10
11
IF l_r_x IS INITIAL.
>>>>>
RAISE EXCEPTION TYPE cx_rsr_propagate_x
13
EXPORTING
14
previous = i_r_root.
15
ELSE.
16
RAISE EXCEPTION l_r_x.
17
ENDIF.
18
19
ENDMETHOD.

Answer 1

I got reply from SAP. The problem can be solved by running program RSDG_XPRA_IOBJ_TO_NW05. Note 939484 describes this.
Note 939484 - Input help for tech characteristic and time characteristics
Summary
Symptom
You upgraded to SAP NetWeaver 2004s. An open SQL error occurs when you execute input help for a technical characteristic, a time characteristic or a unit.
The 'SAPSQL_INVALID_FIELDNAME' short dump in the 'CL_RSDM_READ_MASTER_DATA' class indicates that these characteristics have not been maintained. This error may also occur when you activate InfoProviders, for example.
The error MAY occur for the following InfoObjects:
0CALMONTH
0CALMONTH2
0CALQUART1
0CALQUARTER
0CALWEEK
0CALYEAR
0CURRENCY
0FISCPER
0FISCPER3
0FISCVARNT
0FISCYEAR
0LOGSYS
0SOURSYSTEM
0UNIT
0WEEKDAY1
0RATE_TYPE
0DATE
0LANGU
Other terms
Input help, F4, 0CALMONTH, 0CALMONTH2, 0CALQUART1, 0CALQUARTER, 0CALWEEK, 0CALYEAR, 0CURRENCY, 0FISCPER, 0FISCPER3, 0FISCVARNT, 0FISCYEAR, 0LOGSYS, 0SOURSYSTEM, 0UNIT, 0WEEKDAY1, 0RATE_TYPE, 0DATE, 0LANGU, RSDG_XPRA_IOBJ_TO_NW05
Reason and Prerequisites
The problem can have the following causes:
The characteristic does not have any master data, although you did define a master data read class.
There is no generated master data table for the characteristic (for example, 0CURRENCY) and you have not defined a corresponding master data read class in the meta data.
Solution
Technical characteristics and time characteristics were delivered again for SAP NetWeaver 2004s with new properties. The first time you call the data warehousing workbench, the system activates the technical content. If the (time) characteristic already exists in the active version, the system does not copy it from the technical content again.  For SAP NetWeaver 2004s, however, the following conditions must be fulfilled:
The characteristic has the property "With master data", which ensures that the master data read class functions correctly.
If the active version of the characteristic does not have any master data, copy the characteristic from the content again. Make any necessary adjustments. Ensure that the "With master data" property is set.
The characteristic does not have a generated table, rather it has its own table, delivered by SAP (for example, unit 0CURRENCY -> table TCURC). The definition of the characteristic must include a relevant master data read class (for example, unit 0CURRENCY -> class CL_RSMD_RS_0CURRENCY).
The RSDG_XPRA_IOBJ_TO_NW05 XPRA defines a master data read class automatically. This XPRA is executed when you upgrade. It may, however, occur, that the XPRA is not executed successfully. If this happens, you can execute the XPRA again manually.
Start Transaction SE38.
Enter the name RSDG_XPRA_IOBJ_TO_NW05 in the 'Program' field.
Choose 'Execute' to execute the program.