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

Similar Messages

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

Exception condition "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILU

Hi All,
After the custo of the ESSleave request in the IMG . I made some tests.
Evrethign is going fine but once i try to enter a leave request during a non wroking day, i'm getting this message
Exception condition "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILURE
I checked in st22 and they ask to find a sap note with those key words
"RAISE_EXCEPTION" " "
"SAPLSPO1" or "LSPO1F01"
"INSTANTIATE_CONTROL"
or
"SAPLSPO1" "CNTL_ERROR"
or
"SAPMSSY1 " "CNTL_ERROR"
I found nothing that can help me in sap service..
Did someone already encounter such error ?
Only usefull answers will be rewared .

Hi Adel,
Can you test the same application in the content administrator of the respective portal and check if you find the same error or another error.
Regards,
Narendra.

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 .

Exception condition "CNTL_ERROR" raised - Error in ITS

Dear all
I have created ITS link for Solman - Solar02 t.code When I was trying to upload document in Solar02 using ITS (both using ITS from Solman SICF service, I am getting a dump error,
Exception condition "CNTL_ERROR" raised.
But when i was uploaded in sapgui, it uploaded.
Let me know the solution for this?

This kind of error usually points to the incorrect use of Enjoy SAP controls like ALV, Text Edit, HTML viewer etc. They make use of a framework which can only be handled in the standard SAP GUI and not in WebBased applications. So I guess you will have to come up with something else, because I don't think this is going to work like this.

Exception "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILURE"

Hi All,
We have the Java web dynpro applications running smoothly in development system.
But in Quality system we are getting the following issue.
Exception condition "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILURE"
All users are created with same authorization as in development system.
Still getting the problem.
Any idea how to solve this problem.
Thanks in advance.
Regards,
Sumangala.

Hi ,
CNTL_ERROR" raised is something related to backend system . ask backend consultants to check any dumps related to this error.
Regards,
Koti Reddy

Help - Exception condition "NOT_FOUND" raised

Dear all,
i get the following error when i tried to execute a RFC.I have already check the JCO connection and tested it,everything is working fine.Any idea gurus? thx
Exception condition "NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILURE

Hi
The problem migh be, that the RFC does not get executed.[as there is no design time error] some of the reasons might be
You have not set the mandatory input parameters.
(try inputting these parameters through inputFields rather than just setting them through the code.)
The other reason can be that you have changed some datatype of some mandatory fields( change in the logic would not cause any problme as it is an adaptive rfc). In this case you will need a model re-import.
Regards
Abhijith YS

CONVERSION_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILURE

Hi Gurus,
User is getting the below error while accessing the Record Working time in ESS on portal. Pls help us if u already come across this type of errors.
null
[EXCEPTION]
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "CONVERSION_ERROR" 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:922)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
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:564)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
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:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
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:860)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1288)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:548)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:592)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:864)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
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:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "CONVERSION_ERROR" 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)
... 64 more
Regards,
Manje

Dear,
Could you please check your CAC2 profile for the same error. If you are getting this error due to currency :
'For explicitly specifying a unit in the timesheet, the column for 'Unit of measurement' must be displayed. This can be achieved via transaction CAC2 by customizing field selection for the data entry profile used to enter times. The field CATSD-UNIT must be set as input field. You may also specify a different unit by using customer exit CATS0002. In this case, you must also take care to clear the contents of field CATSHOURS and instead use CATSQUANTITY for the data entered. The corrections contained in note 720926 are only valid if you use customer exit CATS0002 to fill the unit for the wage type specified in the time
sheet.'
Best Regards,
Deepak

Exception condition "DESTINATION_NOT_OPEN" raised

Hi all,
I am getting the dump when loading data from 0CO_OM_WBS_6 from R/3.
RAISE_EXCEPTION
Exception condition "DESTINATION_NOT_OPEN" raised
Error analysis
    A RAISE statement in the program "SAPLCRFC" raised the exception
    condition "DESTINATION_NOT_OPEN".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
Can anyone help me to resolve the problem and finish my init load successfully?
Thanks in advance,
Venky

go through the blow link
http://help.sap.com/saphelp_47x200/helpdata/en/cf/f2bbc8142c11d3b93a0000e8353423/frameset.htm

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?

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

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

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.

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 "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR

Similar Messages

Maybe you are looking for