Error in BEx Analyzer Exception condition "HIERARCHY_NOT_FOUND" raised.

When i run report 0FIAA_C02_Q1001 with input variable as "My controlling area" i get this error.
ERROR:
Exception condition "HIERARCHY_NOT_FOUND" raised.
ERROR Analysis:
A RAISE statement in the program "SAPLRRH1" raised the exception
condition "HIERARCHY_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Please sugggest how to resolve this.
HOw to see which hierarachy it is talking about?
Thanks,
Harika.
Edited by: harikag on Oct 12, 2011 7:11 AM
Edited by: harikag on Oct 12, 2011 7:12 AM

HI
FOr 0Costcenterinfoobject->attribute tab->no hierarhcies
                                         ->hierarchy tab->i see hierarchy tables are enabled.But when i click on
                                             "MaintainHierachy" there are no hierrachies in it.
For 0CO_AREA infoobject->attribute tab->0CCA_HIENM,0PCA_HIENM hierarchies are there.
                                         ->hierarchy tab->nothing is there.
please help out.I didnt load 0COSTELMNT_0102_HIER master datasource in CO_IO.
Is that the reason?

Similar Messages

Exception condition "HIERARCHY_NOT_FOUND" raised. - SAPLRRHI

Hello all,
My issue is very similar as the one described in thread : HIERARCHY_NOT_FOUND, but not solved in the other thread.
I tried to update the system to SP21 as told in the topic, but the issue is still present :
when I open a query with the query designer, I'm still having the same issue. Via the RSRT transaction I get the following error message :
Short text
    Exception condition "HIERARCHY_NOT_FOUND" raised.
What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
Error analysis
    A RAISE statement in the program "SAPLRRHI" raised the exception
    condition "HIERARCHY_NOT_FOUND".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
Trigger Location of Runtime Error
    Program                                 SAPLRRHI
    Include                                 LRRHIU27
    Row                                     36
    Module type                             (FUNCTION)
    Module Name                             RRHI_ASOHIEDIR_READ
I add that the query use a 0cust_sales based hierarchy, when (at the query level) I remove the time dependance the query works fine, but when I select "type of derivation" in the hierarchy display and use 0D_FC_LM1 : I get the error.
(transaction RSTHJTMAINT--> 0D_FC_LM1 based on 0calmonth and use "first day)
Thanks in advance for help.

First of all, thanks Maxim to spend time on my issue, it is really appreciated (and sorry for the late answer, I did not have any computers during the week-end).
I checked both tables (SE16 then "number of entries" button) : RSHIEDIR has 5 entries and RSRHIEDIR_OLAP has 9.
So I go to my info-object 0cust_sales, hierarchy tab, "maintain hierarchy" button and reactivate the hierarchy (I only have one line available) and I get the message "There is no modified version for this hierarchy." When I check again the entries number in both tables : no change, (still 5 and 9).
Please find bellow the abap code I get with the message (when I use RSRT) :
Source Code Extract
Line SourceCde
    6 *" EXPORTING
    7 *"     REFERENCE(E_S_HIEDIR) TYPE RRHI_S_HIEDIR
    8 *" EXCEPTIONS
    9 *"      HIERARCHY_NOT_FOUND
   10 *"----
   11   data: l_hiesid type rrhi_hiesid,
   12         l_TMPJOIN type rs_bool.
   13
   14   CALL FUNCTION 'RRHI_HIESIDASO_GET'
   15     EXPORTING
   16       i_hiesid           = i_hiesid
   17     IMPORTING
   18       E_HIESID_ASO       = l_hiesid.
   19
   20   if l_hiesid < 0.
   21     l_tmpjoin = rs_c_false.
   22   else.
   23     l_tmpjoin = rs_c_true.
   24   endif.
   25
   26   CALL FUNCTION 'RRHI_HIEDIROLAP_READ'
   27     EXPORTING
   28       i_hiesid    = l_hiesid
   29       I_TMPJOIN   = l_tmpjoin
   30     IMPORTING
   31       E_S_HIEDIR = E_S_HIEDIr
   32     EXCEPTIONS
   33       hierarchy_not_found = 1.
   34
   35   if sy-subrc <> 0.
>>>>>     raise hierarchy_not_found.
   37   endif.
   38
   39 ENDFUNCTION.
Thanks again and please let me know if you need more informations.

Error while processing dimension: "Exception condition "X_MESSAGE" raised"

Hi,
I have recently transported an Appset from development to production environment. The transport finished successfully, without any error.
Then I update the members of the dimensions and I process it (Production Environment). I get "Exception condition "X_MESSAGE" raised."
I need to solve this problem as soon as possible.
Regards,
Miguel.

check the below link
Re: Dump when doing selective deletion

Exception condition "INCONSISTENCY" raised

Hi Experts,
Greetings!
I was revising the configuration of my FG Inventory Report when I
encountered this error after saving the Query Designer and running the BEx Analyzer:
Exception condition "INCONSISTENCY" raised.
Afterwards, I cannot able to continue working on BEx Query Designer on the report anymore because of the error.
In the reporting tool ANALYZE_RSZ_TABLES in SE38, I got the following result:
Table RSZELTXREF
Unresolved relations between query elements.
Missing elements in existing query components
Critical error: listed query elements are parts of definitions of
existing queries or query components. Elements are not found in the
table RSZELTDIR in required objects version and can not be used.
Further investigations are required at SAP. Create an OSS message for
BW-BEX-ET-QDEF
Missing element ELTUID
48NRDU7QW9H30633XZDD0G9V3
Check results:
Exception condition INCONSISTENCY dump accesing listed components.
List of affected query components:
Technical Name: ZPP_JMV1_Q001
Technical ID: 484ZV76Y10KGXAALQJ2K78YY9
Component Type: REP
Info Provider: ZPP_JMV1
Package: ZBIDEV
Created in: BID
How should I fix the missing element?
Missing element ELTUID
48NRDU7QW9H30633XZDD0G9V3
You assistance is appreciated.
Thank you.
Regards,
Btup

Hi,
If You have an element in another system I would suggest to perform a transport of a query using this element from one system to the other.Just from the investigations done by you, I see that there is only 1 'missing' element which is used in other queries. Please find out in which queries exactly this element is used. This can be done using the same report ANALYZE_RSZ_TABLES (table RSZELTXREF).You will find
'affected queries or query component'. This is WHERE-USED list for this 'missing' element. Check the existence and consistency of those queries in the QAS and if they are correct, You may simply transport them to this system.
Rgds
Manoj Kumar

Runtime error raise_exception (Exception condition "NOT_EXIST" raised)

Hi,
I tried to ran a DTP to load data in a Standard DSO. Once I run the DTP ,instantly it is showing me short dump.I tried to ran it 2 times. Every time it shows me dump
Runtime Errors RAISE_EXCEPTION
Short Text : Exception condition "NOT_EXIST" raised.
Error Analysis : A RAISE statement in the program "SAPLRSSM" raised the exception
condition "NOT_EXIST".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
Thanks in advance,
Regards,
Snehasish

Hi,
This kind of issues occur in BI7.0, the cause is not clear.
You can once again delete the Data in the DSO using SE14(If Production system, make sure you contact your Basis team for this).
You will have to use the table names(check the Delete data option & click on Activate and adjust databas)
Thanks,

Exception condition "HIERARCHY_NOT_FOUND"

Hello,
we have scenario in Xcelsius where we used QAAWS with different queries.
after upgrading to the EhP1 (BW System) we strated getting WIS errors in QAAWS tool wrt 0country hierarchy even though there are no hierarchies activated in queries.
I rebuilt all the connections but the error is not eliminated - when I try to create a new universe the error is triggered:
Error at quering the hierarchies for dimension 0COUNTRY (Cube xxx/xxxxxx):Exception condition "HIERARCHY_NOT_FOUND" raised.
tried to repair the InfoObjects as well, but it didn't work
any other suggestions?
thanks

Hi Ingo,
we don't want to use the hierarchy in the universe (thus it's not activated in the BW Query)
- i can run BW Query in BEX Web normally without any errors
- when i perform MDXTEST in BW system the exception HIERARCHY_NOT_FOUND is trigerred:
Auslösestelle des Laufzeitfehlers
    Programm                                SAPLRRH1
    Include                                 LRRH1U03
    Zeile                                   69
    Modultyp                                (FUNCTION)
    Modulname                               RRH1_HIERARCHY_IN_TO_EX
I already repaired hierarchies and tables of the 0COUNTRY InfoObject in RSRV , but it didn't help.
Hierarchy is not found in rshiedir table, even though it's there in A version - how can I repair this issue?

Exception condition "E_CURRD_MISSING" raised. Using IDoc

Hello Friends, I need your help, something weird happens to me.
I need to interfase invoices from one legacy system to SAP, I made some test using the BAPI 'BAPI_ACC_INVOICE_RECEIPT_POST', but we had performance issues, so I decided to use the Idoc, so I setted up the "ACC_INVOICE_RECEIPT" msg type, and used the inbound process code BAPI, when I tested it using the WE19 tool, it worked fine and create the Idoc status 53, just executing the Function module but if I try to excecute from the statndard inbound, I cannot post the idoc properly and the document is not posted, I get a dump and this is the error msg I got:
Exception condition "E_CURRD_MISSING" raised.
The termination occurred in the ABAP program "SAPLFDIS" in
   "CASH_FORECAST_SUMMARY_REC_UPD".
The main program was "SAPMSSY4 ".
The termination occurred in line 118 of the source code of the (Include)
Í dont have a clue what could be happening,,   any help???
Thanks Imelda

Thanks for your answer Neil, actually we solve the problem yesterday, in the idoc I was using a 10 for currency type (company currency), and there was a configuration problem, I changed to 00 (Document currency) and now is working, in the future if we need any other curr type, I will verify with them.
Thanks for your time and advice.
Imelda

Exception condition "OPR_NOT_FOUND" raised, in CO02

Hi all,
We faced Runtime Errors         RAISE_EXCEPTION
Short text : Exception condition u201COPR_NOT_FOUNDu201D raised.
When technical person checked he come up reason is entries field of table RESB-COUNTER is greater than entry of table AFVC-COUNTER
We come across below SAP note which provide report to rectify above mention inconsistence in tables
Link :[https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=182011]
After running this it rectify the inconsistence ,But we are unable to find root cause why this inconsistence is being generated.
We are on SAP ECC 6.0, I tried to search relevant Note but didnu2019t find any, so if someone faced same in past please share your experience also suggest possible cause of generation of this inconsistence.
want to add we are using Exit for component allocation , which is doing allocations based on custom logic.
but i checked it activating as well as by deactivating it , in both cases facing same error.
Thanks
Ritesh

Hello
The following notes are the most recent corrections for program error which can cause this issue on production orders:
1541774     Reading master data: RAISE_EXCEPTION: OPR_NOT_FOUND
1364818     Exception condition "OPR_NOT_FOUND" raised.
Best regards
Caetano Almeida

Exception condition "PROBLEM_WITH_QUERY" raised.

Hi Experts,
I have a problem when I Appended a ibase field to service contract search page and enhanced the eh_onsearch_btn where I
added the code for searching the service contract based on ibase if i search the other than the ibase fields result is coming properly when I search provinding value to the search page it is giving below exception
    The following error occurred in system : Exception condition "PROBLEM_WITH_QUERY" raised.
    The error occurred on application server and in work process 4 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: MAKE_INSTANCE_VALID of program CL_CRM_REPORT_ACCRULE=========CP
    Method: MAKE_INSTANCE_VALID of program CL_CRM_REPORT_ACCRULE_ONEORDERCP
    Method: GET_INSTANCE of program CL_CRM_REPORT_ACCRULE=========CP
    Method: CREATE_ACCRULE of program CL_CRM_REPORT_QUESTION========CP
    Method: CONSTRUCTOR of program CL_CRM_REPORT_QUESTION========CP
    Function: CRM_BSP_OIC_1O_SEARCH_FROM_RF of program SAPLCRM_BSP_OIC_1O_SEARCH
    Method: GET_RESULT_GUIDS of program CL_CRM_Q1O_SEARCH=============CP
    Method: GET_RESULT_VALUES of program CL_CRM_Q1O_SEARCH=============CP
    Method: IF_CRM_QUERY_RUNTIME_BTIL~GET_DYNAMIC_QUERY_RESULT of program CL_CRM_QSRVCON_RUN_BTIL=======CP
    Method: EXECUTE_DYNAMIC_QUERY of program CL_CRM_INTLAY_BTIL============CP
Answer will be appreciated.
Thanks & Regards
Chetan Agali.

Is this parameter also present on the Genil Component ? If you are actually trying to query also on this parameter then this parameter should be present on the Genil. Only appending the query input structure would not help here.
Regards
Kavindra

Exception condition "NO_TRIGGER_INSTANCE" raised error in SMQ2

Dear all,
i'm getting this error in SMQ2 transaction of xi server.
Exception condition "NO_TRIGGER_INSTANCE' raised
Did anyone encounter this issue before. Pls share your inputs in resolving it,
Regards,
Jack

Hi ,
Can you provide the details of this dump from ST22 for understanding .
Regards ,
Hanumant .

ERROR MESSAGE : Exception condition "OBJECT_ID_NOT_FOUND" raised

Hi All
We are on SRM 5.0.When I execute the report BBP_EXTREQ_TRANSFER to
transfer the PR's from R/3 into SRM Sourcing cockpit . The entries get
stuck in the outbound queue in R/3.I get the error as SYSFAIL-
"Exception condition "OBJECT_ID_NOT_FOUND" raised."
We have checked the user and the org structure.
Please Help
Thanks
Lebo

Hi Lebo,
check / do the following:
- Local POrg --> Function: Tick box "POrg; everything else blank
- Local PGroup --> Function Tab: Tick box "Pgroup; everything else blank
As you already have the RFC User assigned to the Entry Channel, just create a new SRM user via the Web and select the Local PGroup as the Org Unit to assign the user. You then should have a "normal" entry in the Org Structure, like for all other users.
Cheers,
Claudia

Error message "Exception condition "INTERNAL_ERROR" raised" in Backend.

Hi
I am trying to replicate the materials from Backend to SRM and every time I get the message "Exception condition "INTERNAL_ERROR" raised" in the backend system and the Outbound queue in R/3 system gets stuck.
I have maintained the middleware tables correctly and was able to download other objects.
Can someone kindly help me out in determining the error.
Regards
Manoj

Hello Manoj,
I suppose your´re working with a release < SRM4.0? Then please check the following settings:
SPRO
Customer Relationship Management > Master data > Condition Technique
Create general configuration parameters
Maintain here the TIMEZONE_MASTER_DATA_DB -> pls read the documentation for this point in customizing.
BR
Michael

Exception condition "NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILUR

Hi,
I am getting the following message when I click on workitems for CATS timesheet approval(TS3100007) that are received in UWL tasks inbox in MSS.
Exception condition "NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
at com.sap.xss.hr.cat.approve.blc.FcCatApprove.rfcExecute(FcCatApprove.java:307)
at com.sap.xss.hr.cat.approve.blc.FcCatApprove.rfcReview(FcCatApprove.java:435)
at com.sap.xss.hr.cat.approve.blc.wdp.InternalFcCatApprove.rfcReview(InternalFcCatApprove.java:220)
at com.sap.xss.hr.cat.approve.blc.FcCatApproveInterface.onReview(FcCatApproveInterface.java:379)
at com.sap.xss.hr.cat.approve.blc.wdp.InternalFcCatApproveInterface.onReview(InternalFcCatApproveInterface.java:153)
at com.sap.xss.hr.cat.approve.blc.wdp.InternalFcCatApproveInterface$External.onReview(InternalFcCatApproveInterface.java:333)
at com.sap.xss.hr.cat.approve.vac.dd.VcCatApproveDrillDownListInterface.onEvent(VcCatApproveDrillDownListInterface.java:128)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownListInterface.onEvent(InternalVcCatApproveDrillDownListInterface.java:127)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownListInterface$External.onEvent(InternalVcCatApproveDrillDownListInterface.java:217)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:533)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseReviewAndSaveEvent(FPMComponent.java:946)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseReviewAndSaveEvent(FPMComponent.java:1109)
at com.sap.xss.hr.cat.approve.vac.dd.VcCatApproveDrillDownList.fireEvent(VcCatApproveDrillDownList.java:330)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownList.fireEvent(InternalVcCatApproveDrillDownList.java:166)
at com.sap.xss.hr.cat.approve.vac.dd.VcCatApproveDrillDownListInterface.blcEvent(VcCatApproveDrillDownListInterface.java:228)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownListInterface.blcEvent(InternalVcCatApproveDrillDownListInterface.java:163)
at com.sap.xss.hr.cat.approve.vac.dd.VcCatApproveDrillDownListView.onActionReview(VcCatApproveDrillDownListView.java:303)
at com.sap.xss.hr.cat.approve.vac.dd.wdp.InternalVcCatApproveDrillDownListView.wdInvokeEventHandler(InternalVcCatApproveDrillDownListView.java:178)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
at com.sap.xss.hr.cat.approve.model.approval.CatsApproval.hrmss_Cat_Wd_Approval(CatsApproval.java:178)
at com.sap.xss.hr.cat.approve.model.approval.Hrmss_Cat_Wd_Approval_Input.doExecute(Hrmss_Cat_Wd_Approval_Input.java:137)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
Does anyone have any idea?
Thanks.
BNP

Hi,
It looks to me like the RFC Hrmss_Cat_Wd_Approval does not exist. Is your back-end system ECC 6.0? If not then I don't believe this will work. See page 93 of the document at this link:
https://www2.iviewstudio.com/support_content/_17296/BP_MSS_mySAPERP2005_SR1_EN.pdf
Bert

Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised

Hi All,
I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
===========================================
Runtime Errors RAISE_EXCEPTION
Date and Time 25.07.2008 08:31:11
Short text
Exception condition "METADATA_MISSING" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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
A RAISE statement in the program "SAPLDSVAS_SERV" raised the exception
condition "METADATA_MISSING".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
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:
"RAISE_EXCEPTION" " "
"SAPLDSVAS_SERV" or "LDSVAS_SERVC7I"
"MAP_DSVAS_TT_DATA_TO_TT_25"
or
"SAPLDSVAS_SERV" "METADATA_MISSING"
or
"RDSMOP_MAIN " "METADATA_MISSING"
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... "terra"
Network address...... "172.16.1.198"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "TERRA"
Database type..... "ORACLE"
Database name..... "DSM"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 23 2007 01:07:18"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 133
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
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.... 8176
EM...... 37628064
Heap.... 0
Page.... 65536
MM Used. 31785376
| MM Free. 1656912
=============================================
Configuration:
OS :Windows 2003 server.
Solution Manager 7.0 SP15
Oracle 10.2
RAM - 2 GB
Its bit urgent, Please help out us.
Thanks in advance.
Best Regards,
Pratyusha

Hi
Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
This error is related to ABAP program.
Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system.

Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR

Dear EP Expert,
We are trying to implement ECC 6 with EP 7. When i try to browse a standard webdypro iView provide by the ess business package i.e (record working time). The system return such error.
Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:468)
     at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:822)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:248)
     at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:344)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:234)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:484)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
     at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
     at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:879)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1280)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:552)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:191)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:221)
     at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 66 more
Other page like leave request is not displaying anything at all, just the blank page. Anyone knows what is wrong? I have read some previous thread and found that they are mentioning the "CVR". Anyone know what is it?
Thanks
Regards,
Bryan

Dear Brian
This problem may be arising from the error/changes required in Entry Profile...
In R/3
- SPRO
-   Cross-Application Components
-     Time Sheet
-       Set Up Data Entry Profiles
Go there and fix the problem and this should be resolved...
Best Regards,
Aslam Riaz

Error in BEx Analyzer Exception condition "HIERARCHY_NOT_FOUND" raised.

Similar Messages

Maybe you are looking for