on 10-10-2008 1:02 AM
Dear Experts,
One user of the Travel Application(ESS portal) is getting the error "RFC PTRA_WEB_CUSTOMIZING_GET reported errors".
This error has been reported previously in this forum (another member) and a fix has been released through the note 954108.
When i checked that note the corresponding changes has already been done in our webdynpro component.
Any idea why this error is occuring still?
Here is the complete exception chain
RFC PTRA_WEB_CUSTOMIZING_GET reported errors.
RFC PTRA_WEB_CUSTOMIZING_GET reported errors.com.sap.pcuigp.xssfpm.java.FPMRuntimeException: RFC PTRA_WEB_CUSTOMIZING_GET reported errors.
at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
at com.sap.xss.tra.fc.customizing.FcTraCustomizing.rfcCustomizingGet(FcTraCustomizing.java:1105)
at com.sap.xss.tra.fc.customizing.FcTraCustomizing.updateCustomizing(FcTraCustomizing.java:592)
at com.sap.xss.tra.fc.customizing.FcTraCustomizing.onInit(FcTraCustomizing.java:234)
at com.sap.xss.tra.fc.customizing.wdp.InternalFcTraCustomizing.onInit(InternalFcTraCustomizing.java:1248)
at com.sap.xss.tra.fc.customizing.FcTraCustomizingInterface.onInit(FcTraCustomizingInterface.java:122)
at com.sap.xss.tra.fc.customizing.wdp.InternalFcTraCustomizingInterface.onInit(InternalFcTraCustomizingInterface.java:1153)
at com.sap.xss.tra.fc.customizing.wdp.InternalFcTraCustomizingInterface$External.onInit(InternalFcTraCustomizingInterface.java:1339)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:774)
at com.sap.xss.tra.trp.fc.plan.FcTrpPlan.onInit(FcTrpPlan.java:574)
at com.sap.xss.tra.trp.fc.plan.wdp.InternalFcTrpPlan.onInit(InternalFcTrpPlan.java:3870)
at com.sap.xss.tra.trp.fc.plan.FcTrpPlanInterface.onInit(FcTrpPlanInterface.java:125)
at com.sap.xss.tra.trp.fc.plan.wdp.InternalFcTrpPlanInterface.onInit(InternalFcTrpPlanInterface.java:2660)
at com.sap.xss.tra.trp.fc.plan.wdp.InternalFcTrpPlanInterface$External.onInit(InternalFcTrpPlanInterface.java:2874)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:774)
at com.sap.xss.tra.trp.fc.flight.FcTrpFlight.onInit(FcTrpFlight.java:335)
at com.sap.xss.tra.trp.fc.flight.wdp.InternalFcTrpFlight.onInit(InternalFcTrpFlight.java:4201)
at com.sap.xss.tra.trp.fc.flight.FcTrpFlightInterface.onInit(FcTrpFlightInterface.java:138)
at com.sap.xss.tra.trp.fc.flight.wdp.InternalFcTrpFlightInterface.onInit(InternalFcTrpFlightInterface.java:3739)
at com.sap.xss.tra.trp.fc.flight.wdp.InternalFcTrpFlightInterface$External.onInit(InternalFcTrpFlightInterface.java:3875)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:774)
at com.sap.xss.tra.trp.vc.planbuild.VcTrpPlanBuild.onInit(VcTrpPlanBuild.java:676)
at com.sap.xss.tra.trp.vc.planbuild.wdp.InternalVcTrpPlanBuild.onInit(InternalVcTrpPlanBuild.java:3240)
at com.sap.xss.tra.trp.vc.planbuild.VcTrpPlanBuildInterface.onInit(VcTrpPlanBuildInterface.java:172)
at com.sap.xss.tra.trp.vc.planbuild.wdp.InternalVcTrpPlanBuildInterface.onInit(InternalVcTrpPlanBuildInterface.java:144)
at com.sap.xss.tra.trp.vc.planbuild.wdp.InternalVcTrpPlanBuildInterface$External.onInit(InternalVcTrpPlanBuildInterface.java:220)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:466)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:179)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
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:347)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:382)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:618)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
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:180)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Regards,
Santhosh
Hello Santhosh,
This could be the problem:
The date that is passed to the RFC PTRM_WEB_CUSTOMIZING_GET is from
the J2EE engine where our travel application is running.
In your case it seems that this date is wrong.
Could you please verify that
a) The time and date setting of your J2EE is correct ?
b) Check whether the date provided in field I_DATE of RFC PTRM_WEB_CUSTOMIZING_GET remains always the same (you assume it is always the date of the last J2EE restart)
You can see the Time and Date in the J2EE in the start page for SAPMMC. The actual Date and Time from the J2EE is taken from the Date and Time of your Workstation computer.
Regards,
Raynard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Santhosh,
You have probably solved your problem, but for other people that accounter this error message this might be interesting.
I got the same problem while implementing ESS Travel, and removed sap_all from the user. Therefore I knew it had to do with roles and authorizations. The problem was to find exactly which one was missing.
This is the profiles I added to the user to remove the error:
P_TRV_ALL
F_TRAVL_ALL (To allow travel requests)
I also added these roles:
SAP_ESSUSER_ERP
SAP_FI_TV_TRAVEL_MANAGER
There might be some redundancy here, but at least it works as it should.
Regards,
Ellen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.