Work Flow RFC

[Former Member]

Hi,

i have made some changes to the SAP developed webdynpro application as per the requirement,

when the user changes the personal information in the ESS personal information screen the Standard RFC is getting called but, if the user made any chanegs to the First name or last name or martial status the Z rfc is getting called and the work flow triggers and the notification will go to the corresponding manager for approval once the manager approves the request then the changes will appear in the portal and also saved in the backend system.

bu while making changes the first name and last name or martial status and clicking the save button the following error is coming,

Personal Data

Critical Error

A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.

Please contact your system administrator.

An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE

An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE: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.ca.personal.fc.FcPerPersonalCA.callWorkFlowFM(FcPerPersonalCA.java:488)

at com.sap.xss.hr.per.ca.personal.fc.wdp.InternalFcPerPersonalCA.callWorkFlowFM(InternalFcPerPersonalCA.java:681)

at com.sap.xss.hr.per.ca.personal.fc.FcPerPersonalCAInterface.callWorkFlowFM(FcPerPersonalCAInterface.java:206)

at com.sap.xss.hr.per.ca.personal.fc.wdp.InternalFcPerPersonalCAInterface.callWorkFlowFM(InternalFcPerPersonalCAInterface.java:242)

at com.sap.xss.hr.per.ca.personal.fc.wdp.InternalFcPerPersonalCAInterface$External.callWorkFlowFM(InternalFcPerPersonalCAInterface.java:322)

at com.sap.xss.hr.per.ca.personal.review.VcPerPersonalCAReview.onBeforeOutput(VcPerPersonalCAReview.java:235)

at com.sap.xss.hr.per.ca.personal.review.wdp.InternalVcPerPersonalCAReview.onBeforeOutput(InternalVcPerPersonalCAReview.java:234)

at com.sap.xss.hr.per.ca.personal.review.VcPerPersonalCAReviewInterface.onBeforeOutput(VcPerPersonalCAReviewInterface.java:135)

at com.sap.xss.hr.per.ca.personal.review.wdp.InternalVcPerPersonalCAReviewInterface.onBeforeOutput(InternalVcPerPersonalCAReviewInterface.java:132)

at com.sap.xss.hr.per.ca.personal.review.wdp.InternalVcPerPersonalCAReviewInterface$External.onBeforeOutput(InternalVcPerPersonalCAReviewInterface.java:208)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseSaveEvent(FPMComponent.java:953)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseSaveEvent(FPMComponent.java:1116)

at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNavi.next(VcPersInfoReviewNavi.java:227)

at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNavi.next(InternalVcPersInfoReviewNavi.java:175)

at com.sap.xss.per.vc.reviewnavi.ReviewNaviView.onActionNext(ReviewNaviView.java:153)

at com.sap.xss.per.vc.reviewnavi.wdp.InternalReviewNaviView.wdInvokeEventHandler(InternalReviewNaviView.java:173)

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:321)

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.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)

at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)

at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)

at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)

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.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

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(Native Method)

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: 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.ca.personal.zhw201.model.ZHW201_PERSAPPR.zhw201_Persappr(ZHW201_PERSAPPR.java:179)

at com.sap.xss.hr.per.ca.personal.zhw201.model.Zhw201_Persappr_Input.doExecute(Zhw201_Persappr_Input.java:137)

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)

... 65 more

and my problem is that my application is working in the developement portal, but in testing it is giving error. please give me some suggestion s on this,

i have checked in the backend the RFC is available and executed successfully.

Cheers,

Apparao

[Former Member · Accepted solution]

Hi

did you check the RFC in the backend with the same inputs , is it working fine .

RFC_ERROR_SYSTEM_FAILURE An exception occurred that was not caught ,

this would occur if there is problem from your RFC side ,

put the code inthe try catch and try to test the application(which you are passing to the RFC) ,

instead of application throwing the runtime exception , you would figure out the exact exception .

even check the RFC in the backend with the same values you are passing , and execute the RFC .

or even you can put a external debugging where the RFC get called and check whether the

values are passed to the RFC , or other thing you can do it test the application inthe webdynpro

with hard cording the values .

[Former Member · Accepted solution]

Hi Murali,

i have tested the RFC also in the backend, it is working fine, but i have already insert the break points, the bapi is not getting called,

anu inputs on this.,

Cheers,

Apparao

[Former Member · Accepted solution]

hi

when you set the break point and your RFC is not called ,

the user id provided for the JCO 's should be as same as ECC when you debug your application ,

else it doesnot get triggered.

[Former Member]

they modified the standard BAPI

[Former Member]

Hi Murali,

i am able to debogg the RFC, and that is now getting called form portal also, it is populating the data also, when we make any changes in data and send it back with save button it is giving the RFC error,

we are now checking in authorization prespective also, do have any idea about this?

Cheers,

Apparao

[Former Member]

hi

is your ZRFC calling a standard RFC , if so they could be problem there ,

do check there or even the Work Flow RFC , becuase when even you make changes

i guess Work RFC gets triggered , so even that could cause problem .

Edited by: murali krishna reddy on Apr 16, 2009 6:27 AM