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.
Runtime Errors UNCAUGHT_EXCEPTION
Exception : CX_SDB_ORA_PROGRAM_ERROR
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

Similar Messages

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.

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

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

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

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 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

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

UNCAUGHT_EXCEPTION runtime errors when changing the PO

Hi everyone,
We are facing the problem which is when changing the PO short dump UNCAUGHT_EXCEPTION is occurred then it will display "The page cannot be displayed"
I don't know what is the exactly that cause of this problem
Anyone who facing the same problem before, pls help on this. Hope anyone can help us on this.
Thanks,
quare

Hi Disha,
I found that only this PO cannot be change. Others are ok. There is an error in ST22 which is as below:
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_BBP_PD_ABORT
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assinged to the class 'CX_BBP_PD_ABORT', was not
     caught,
    which led to a runtime error.
    The reason for this exception is:
    Übernehmen
After further search of error there is also message that relates to this error:
Buffer table not up to date
Message no. BBP_PD001
Diagnosis
In FORM CHANGE_VERSION_MAP_ORG (function group SAPLBBP_PDCV) an inconsistent status was discovered.
Procedure
Start the transaction again. If the error occurs again, create an OSS message.
To analyze the error, you can set a breakpoint in the function module 'BBP_PD_ABORT' and look at the call-up hierarchy in debugging mode.
I wondering what is the problem. Since it occurs not for all PO but certain PO only.
Please help.
Thanks,
quare

Runtime error on BI Dev (UNCAUGHT_EXCEPTION)

Hi Team,
We are getting time error pn BI DEV . please check the below log .
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_RSR_X_MESSAGE
Date and Time          28.02.2012 11:50:17
     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
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"
SAP-Release 701
Application server... "pssapsbx"
Network address...... "10.10.32.114"
Operating system..... "AIX"
Release.............. "6.1"
Hardware type........ "00F6B2C64C00"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "pssapsbx"
Database type..... "ORACLE"
Database name..... "BD3"
Database user ID.. "SAPBP3"
Terminal.......... "inp-260888-1"
Char.set.... "en_US.ISO8859-1"
SAP kernel....... 701
created (date)... "Apr 1 2011 23:57:22"
create on........ "AIX 2 5 00CB5A5B4C00"
Database version. "OCI_102 (10.2.0.4.0) "
Patch level. 137
Kindly suggest , this has to be check by BASIS or BI DEV team.

Hi,
About this dump please see the instructions given in the solution
part of note 1157796.
#1157796 - Characteristic 0REQUEST must reference 0REQUID
The root cause could be the missing reference of 0REQUEST to 0REQUID
as mentioned in this note.
In addition to please check Infoobject 0REQUID in transaction RSD5.
Please compare the delivered version with the active version and if
difference exist install the content version again
as it is given in the note.
Thank You.
Regards,
Deepika

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

Webdynpro application runtime error CX_FQDN

Hi experts,
I am encountering following error when running a sample webdynpor application from SE80. I have included details of my Hosts file entries and profile parameter in the details below.
My SAP system is installed on my desktop computer as a standalone on a wrkgroup. Name of the host is 'ecc6'.
Step by step instructions preferably with some example will be greatly appreciated.
Thanks in advance. AP
What has happened?
The URL http://ecc6:8006/sap/bc/webdynpro/sap/z_tutorial_1 was not called due to an error.
Note
The following error text was processed in the system ECC : Die URL enthält keine vollständige Domainangabe (ecc6 statt ecc6.).
The error occurred on the application server ecc6_ECC_06 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
ST22 dump is:
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_FQDN
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_FQDN', was not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    Die URL enthält keine vollständige Domainangabe (ecc6 statt
    ecc6.).
System environment
    SAP-Release 700
    Application server... "ecc6"
    Network address...... "192.168.100.1"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x Intel 801686"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "ECC6"
    Database type..... "ORACLE"
    Database name..... "ECC"
    Database user ID.. "SAPSR3"
User and Transaction
    Client.............. 001
    User................ "SAPUSER"
    Language Key........ "E"
    Transaction......... " "
    Program............. "CX_FQDN=======================CP"
    Screen.............. "SAPMHTTP 0010"
    Screen Line......... 2
    Information on Caller ofr "HTTP" Connection:
    Plug-in Type.......... "HTTP"
    Caller IP............. "192.168.100.1"
    Caller Port........... 8006
    Universal Resource Id. "/sap/bc/webdynpro/sap/z_tutorial_1"
Information on where terminated
    Termination occurred in the ABAP program "CX_FQDN=======================CP" -
     in "CHECK".
    The main program was "SAPMHTTP ".
    In the source code you have the termination point in line 10
    of the (Include) program "CX_FQDN=======================CM002".
Entries in C:WINDOWSsystem32driversetchosts
127.0.0.1                 localhost
192.168.100.1     ecc6
Instance Profile in SAP transaction RZ10 is ECCDVEBMGS06_ECC6_
            Parameter Name                                      Parameter value
login/no_automatic_user_sapstar                      0
login/system_client                                            001
SAPSYSTEMNAME                                           ECC
SAPGLOBALHOST                                           ecc6
SAPSYSTEM                                                    06
INSTANCE_NAME                                             DVEBMGS06
DIR_CT_RUN                                                 $(DIR_EXE_ROOT)$(OS_UNICODE)NTI386
DIR_EXECUTABLE                                         $(DIR_INSTANCE)exe
PHYS_MEMSIZE                                             512
rdisp/wp_no_dia                                             6
rdisp/wp_no_btc                                            3
icm/server_port_0                                          PROT=HTTP,PORT=80$$
ms/server_port_0                                          PROT=HTTP,PORT=81$$
rdisp/wp_no_enq                                   1
rdisp/wp_no_vb                                    1
rdisp/wp_no_vb2                                  1
rdisp/wp_no_spo                                   1
DIR_CLIENT_ORAHOME                              $(DIR_EXECUTABLE)

HI ,
SAP has recommended it like that
for accessing SAP web dynpro abap application you have to give the full FQDN i.e. host name with domain.
simply hostname alone wont work.
http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/content.htm
Pls go through the link.This mite help
Thanks,
Aditya.

Runtime error: CX_SHM_OUT_OF_MEMORY

Hello Experts,
I have opened one program in SE38 in Quality system which contains so many routines.I need to check the source code of a routine say ZTEST.
For that i have double clicked on the name of routine(eg. Perform ZTEST).But am getting below runtime error.
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_SHM_OUT_OF_MEMORY
This is happenning irrespective of Users and Programs.(Both Standard and Customized programs)
But am able to view the source code of routine by double clicking on the routine name in Development system.
I have checked the profile parameter abap/shared_objects_size_MB which is same for both Development and Preproduction system.Could you please let me know why this is happening?Do I need to restart the SAP system.
Platform:
SAP ECC 6.0,UNIX,ORACLE
Thanks & Regards,
Gopi L.

Check
Note 1322182 - Memory consumption of ABAP Shared Objects
the default value is usually too low.
Markus

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

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.
The error message when run in BEx analyzer:
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.
And the ABAP dump log:
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.

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.

Runtime Errors UNCAUGHT_EXCEPTION ..CX_SDB_ORA_PROGRAM_ERROR

Similar Messages

Maybe you are looking for