on 07-16-2007 6:08 PM
Hello,
I am on ERP05 and trying to point one of my ESS Applications to a Custom function group made by the ABAP guy ,I was able to do that successfully and get onto the overview screen of the application but when the ZHrxss_Per_Modify module is called I get the following error:
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
at com.sap.xss.hr.per.us.address.fc.FcPerAddressUS.modifyRecord(FcPerAddressUS.java:228)
at com.sap.xss.hr.per.us.address.fc.wdp.InternalFcPerAddressUS.modifyRecord(InternalFcPerAddressUS.java:608)
at com.sap.xss.hr.per.us.address.fc.FcPerAddressUSInterface.modifyRecord(FcPerAddressUSInterface.java:119)
at com.sap.xss.hr.per.us.address.fc.wdp.InternalFcPerAddressUSInterface.modifyRecord(InternalFcPerAddressUSInterface.java:218)
at com.sap.xss.hr.per.us.address.fc.wdp.InternalFcPerAddressUSInterface$External.modifyRecord(InternalFcPerAddressUSInterface.java:294)
at com.sap.xss.hr.per.us.address.detail.VcPerAddressUSDetail.onFlush(VcPerAddressUSDetail.java:243)
at com.sap.xss.hr.per.us.address.detail.wdp.InternalVcPerAddressUSDetail.onFlush(InternalVcPerAddressUSDetail.java:244)
at com.sap.xss.hr.per.us.address.detail.VcPerAddressUSDetailInterface.onFlush(VcPerAddressUSDetailInterface.java:146)
at com.sap.xss.hr.per.us.address.detail.wdp.InternalVcPerAddressUSDetailInterface.onFlush(InternalVcPerAddressUSDetailInterface.java:136)
at com.sap.xss.hr.per.us.address.detail.wdp.InternalVcPerAddressUSDetailInterface$External.onFlush(InternalVcPerAddressUSDetailInterface.java:216)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:491)
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.per.vc.detailnavi.VcPersInfoDetailNavi.next(VcPersInfoDetailNavi.java:226)
at com.sap.xss.per.vc.detailnavi.wdp.InternalVcPersInfoDetailNavi.next(InternalVcPersInfoDetailNavi.java:163)
at com.sap.xss.per.vc.detailnavi.DetailNaviView.onActionNext(DetailNaviView.java:156)
at com.sap.xss.per.vc.detailnavi.wdp.InternalDetailNaviView.wdInvokeEventHandler(InternalDetailNaviView.java:161)
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:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
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(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: An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
at com.sap.xss.hr.per.us.address.custom_model.ZHRXSS_PER_P0006_US.zhrxss_Per_Modify_P0006_Us(ZHRXSS_PER_P0006_US.java:305)
at com.sap.xss.hr.per.us.address.custom_model.Zhrxss_Per_Modify_P0006_Us_Input.doExecute(Zhrxss_Per_Modify_P0006_Us_Input.java:137)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
... 48 more
I wonder for the cause for this.
Any help would be highly appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Do you mean custom ABAP 'function module'? If so, you make sure that the function module runs with no errors on it's on in the backend first before you try calling it from web dynpro.
This exception is thrown when the execution of the function module from the web dynpro application fails. It usually happens when the function module itself is crashing with a runtime error. You can check for short dumps in the ERP by running transaction st22.
Hope this helps.
Cheers
Valerie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.