Webdynpro record working time general
Dear Expert,
I have a general question. Previously my company is using EP 6 with some transaction iview and they have upgrade to EP 7 with ECC 6.
My question is
1) Which webdynpro page should i use if i wanted to let the employees to key in over time.
2) Which webdynpro page should i use if wanted to let the employees to record their attandance.
3) Is there any standard workflow for overtime request and attandance request.
4) Where can i specify the workflow to use as like what i can specify for the leave.
Thanks in advance
Regards
Bryan
Hi Lee,
As u know that we have some standerd Business Packages for ESS/MSS, when we download it we will get some pre defined Roles, worksets, pages with iviews.
According to ur (2) point we have a Workset called Working Time --> Record Working Time --> u can record their attandance.
let me know if its help ful.
Regards,
Kishore
Similar Messages
-
Webdynpro record working time general question
Dear Expert,
I have a general question. Previously my company is using EP 6 with some transaction iview and they have upgrade to EP 7 with ECC 6.
My question is
1) Which webdynpro page should i use if i wanted to let the employees to key in over time.
2) Which webdynpro page should i use if wanted to let the employees to record their attandance.
3) Is there any standard workflow for overtime request and attandance request.
4) Where can i specify the workflow to use as like what i can specify for the leave.
Thanks in advance
Regards
BryanHi Lee,
As u know that we have some standerd Business Packages for ESS/MSS, when we download it we will get some pre defined Roles, worksets, pages with iviews.
According to ur (2) point we have a Workset called Working Time --> Record Working Time --> u can record their attandance.
let me know if its help ful.
Regards,
Kishore -
Header information not displaying in ABAP Webdynpro record working time
1. I am not seeing the header information, personnel number, name, cost center, on the ABAP Webdynpro record working time timesheet. When I run the timesheet profile in CAT2 the header contains the personnel number, name, cost center, but these do not display when the ABAP Webdynpro timesheet is run
2. Is there a version of the ABAP webdynpro timesheet that prompts for the personnel number, date and profile prior to executing the timesheet? I want to define an ESS link for managers to update timesheets of individual teammates. The teammate do not necessarily have to be their direct reportsHi David,
CATS Webdynpro application is a OIF fpm. Please check if you have performed the FPM IDR configuration properly.
In standard, the ESS CATS does not prompt for the personnel number except in CE scenario. In MSS addon, you have an option to launch the ESS CATS application on-behalf of the employee. Please refer to the sap library documentation.
Hope this helps,
Regards,
Roy -
Hello Guru's,
We are working on Time Management and for this we are using Working Time iView in Employee Self-Service role.
We are using Record Working Time and in this we record the working times and in the WBS Element cell there is option like F4 which opens up a popup and we can search for Projects (or WBS element) I want to make changes to that screen.
Please guide me where to do the changes for that?
I looked into the code but couldn't find.
Thanks in Advance for your time.
Regards,
PramodHi Pramod,
In order to modify the standard webdynpro record working time application , you have to do below steps.
Import source code ( XSS Components ) in NWDI
Create a track.
From Developer studio , connect to DTR and check out the source code .
Create the sap.com/ess~cat (DC') project in NWDS.
Modify the standard SAP code as per your needs .
Refer JDI Cookbook for ESS.doc for above tasks.
Thanks
Aravinda -
Record working Time link in General Related Activities iView
Hello Gurus,
In the MSS Related Activities iView we have a link to navigate to Record Working TIme iView, but when I click on that link it is pointing to the production portal but I am testing in the development environment.
So please any one help he me out whether do we have to maintain any URL.
When I click Timesheet I can see the list of employees in employee search area and information in general section but when I click on the record working time link in the related activities area portal redirects me to the production portal URL and displays the production portal login screen. Please help me out in resolving the issue.Hmm this is interesting. Guess that's reason even when i am trying to call pdc location of iview "Record Working Time" it is unable to load fpm application based changes and some of personalizations.
Wondering if there is any way to generate or find absolute path to run these application, as they are running on Portal(it works just fine when i launch from my ESS role).
http watch was not great help..
Cheers,
Sudhir -
Record Working Time Error on Portal
Hi Experts,
I am getting following error which try to do record working time from portal. Need your kind solution to resolve the issue..
Thanks in advance.
Errors:
Record Working Time
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.
The current statement requires a character-type data object., error key: RFC_ERROR_SYSTEM_FAILURE
The current statement requires a character-type data object., error key: RFC_ERROR_SYSTEM_FAILURE:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The current statement requires a character-type data object., 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:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:779)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:714)
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.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:1244)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
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:313)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:730)
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(AccessController.java:180)
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: The current statement requires a character-type data object., 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)
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:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:779)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:714)
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.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:1244)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
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:313)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:730)
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(AccessController.java:180)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)Check transaction ST22 for exceptions/errors (that is usually the first place...thanks to Barin Desai for drilling that into my head long ago...haha...make sure you set the dates to check correctly). If nothing there (there should usually be with this kind of error), then also check your JCO connetions for the WebDynpro (you can do this in the portal or through Visual Admin but you will need J2EE admin permissions).
-
Java.lang.NullPointerException in the record working time iview
Hello,
I am getting java.lang.NullPointerException when I try to access the record working time iView. Below is the full exception chain.
Please help me out in fixing the issue.
java.lang.NullPointerException
at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.getEmployeenumber(FcEmployeeServicesInterface.java:115)
at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.getEmployeenumber(InternalFcEmployeeServicesInterface.java:175)
at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.getEmployeenumber(InternalFcEmployeeServicesInterface.java:235)
at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:791)
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:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:192)
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:864)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1351)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:550)
at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
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:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:192)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)Hi,
All the parameters are maintained in the SU01 but we are in strange situation here only for one test user id we are getting null pointer exception with the time sheet. We compared with the user id which is working there is no difference in the parameters
maintained. Please tell me why this behavior between two user ids.
These two are manager user ids. For employee user ids time sheet is working fine. -
Number of rows in Record Working Time.
Hello Guru's,
IN ESS- Record Working Time - the number of rows visible are set to 8 in the Web Dynpro Java Code.
I had a look at the Note:
Note 957741 - Few lines in the data entry grid of the timesheet webdynpro
The question I had is to have more than 8 rows visible, is it Java Code modification or any other alternative to change the number of Visible Row....
Please reply back asap.
Thanks in advance for your time.
Best Regards,
PramodHi Siddharth,
Thanks for the reply.
Looks like if need to change the no of rows need to do the WDJ code modifications.
Interesting to know the other details in the message.
But in the reply the interface you mentioned what for that is used,
Since when checked the where used list of the attribute it calls ADD_INITIAL_LINES_TO_TIMESHEET even in the debug it is not allowing to do the changes to value which is 6 by default.
Since the value is constant it cannot be changed.
what was your intention when you gave that reply, curious to know how would it solve the issue.
And one other questions In the Java Code
ListViewerSlim listViewer =
new ListViewerSlim(
view,
wdThis.getRFC_FieldList_Timesheet(),
"TimesheetData",
// listViewer.destroyAllColumnHeaders(); //XZQ110505
theTable = listViewer.getTableControl();
theTable.setVisibleRowCount(8); //Note SOW_957741
// theTable.setHeader(null); //XZQ110505
it is set to 8 why is it different in both the cases.
Since, when we login to the Portal it shows no of rows visible as 8 not 6 as it is in the interface?
any thoughts on this.
Kind Regards,
Pramod -
To unhide the columns of " Record Working Time " table
hi experts ,
Can any one suggest me how to unhide some columns of the table "Record Working Time" .
Actually I have tried the following procedure : content admin -> portal content -> iview -> Rclickctrlalt and check the property of the table and displayed all the columns . It shows all the columns perfectly .
Finally , when I checked the table in Employee self service -> Working time -> Record working time , I can not see some columns which are visible in content admin "Record Working Time " iview .
It is a standard webdynpro java application "CatDataRecord" .hi gorlisrinu ,
Thanks for your reply .
I have all the administration right . When I check the iview in 'Content Admin' I can see all the columns , but when I check the same iview under 'ESS role' i can not see some of the columns of "Record Working Table ". That is my problem . Can you tell me what is the reason behind it ? I always save all the changes after any modification .
Regards ,
Sumana
Edited by: sumana05 on Nov 18, 2011 7:39 AM -
How to implement Manager Selfservice - Recording Working Time - BP
Hi!
I would like to have a stepby step approach to implement business package for recording working time.
What I need is the following information?
1. Pre-requisites
2. How to create the iview ?
3. What R3 configurations need?
you can email if you have good documentation on this to [email protected]
Thank you
RameshThe primary limitation you will encounter when trying to do high speed
digital I/O using your E-Series hardware is that the digital lines are
all software timed. This means that for each and every digital
read it is necessary for your software to issue a command to your
hardware, read a single point, then receive the response from the
board. This prevents you from performing digital operations at
very high speed. In general, I would say that 100 microseconds is
a very good response using software-timed digital I/O on a Windows
computer.
It is difficult to make a good recommendation without more detail about
what you are trying to do. You may need to consider switching to
a Real-Time operating system, or upgrading your DAQ hardware to a board
that will allow you to time your digital acquisitions on the board
itself. These devices, such as the m-Series DAQ or the PCI-653x
series, would allow you to use hardware triggers for your digital
acquisitions, change detection, and buffered data acquisitions to
reduce the software overhead involved in a rapid acquisition. -
Dump in Record working time aplplication
Hi,
Getting dump as shown below in Record working time appli
HRESS_C_CATS
Category ABAP Programming Error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_SALV_WD_NC_PROGRAM_ERROR_UI
ABAP Program CL_SALV_WD_C_TABLE============CP
Application Component BC-WD-CMP-ALV
Date and Time 09/01/2011 21:55:11
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_SALV_WD_NC_PROGRAM_ERROR_UI' was raised, but it was not
caught anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_SALV_WD_C_TABLE============CP' has to be
terminated.
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.Category ABAP Programming Error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_SALV_WD_NC_PROGRAM_ERROR_UI
ABAP Program CL_SALV_WD_C_TABLE============CP
Application Component BC-WD-CMP-ALV
Date and Time 09/02/2011 04:31:37
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_SALV_WD_NC_PROGRAM_ERROR_UI' was raised, but it was not
caught anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_SALV_WD_C_TABLE============CP' has to be
terminated.
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
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SALV_WD_NC_PROGRAM_ERROR_UI', was
not caught and
therefore caused a runtime error.
The reason for the exception is:
Data no longer available when SALV_WD_TABLE GET_MODEL called
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:
"UNCAUGHT_EXCEPTION" "CX_SALV_WD_NC_PROGRAM_ERROR_UI"
"CL_SALV_WD_C_TABLE============CP" or "CL_SALV_WD_C_TABLE============CM01D"
"IF_SALV_WD_COMP_TABLE_IF~GET_MODEL"
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.
Server-Side Connection Information
Information on Caller of "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. " "
Caller Port........... " "
Universal Resource ID. "/sap/bc/webdynpro/sap/hress_a_cats_1"
Program............. "CL_SALV_WD_C_TABLE============CP"
Screen.............. "SAPMHTTP 0010"
Screen Line......... 2
Information on Caller ofr "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. " "
Caller Port........... " "
Universal Resource Id. "/sap/bc/webdynpro/sap/hress_a_cats_1" -
MSS Record Working Times header
I am losing the employee's name in the screen header when I use a custom Webdynpro Application Configuration for Record Working Times on Behalf of Employee in MSS.
Here is what I've done...
The ZHRESS_AC_CATS_1_CP_1 in the screenshot below is an exact copy of HRESS_AC_CATS_1. I did not make any changes to it.
When I specify the standard HRESS_AC_CATS_1 in the Launchpad:
This is what the Record Working Times header looks like:
But when I specify ZHRESS_AC_CATS_1_CP_1 (EXACT copy of HRESS_AC_CATS_1) in the Launchpad:
This is what the header looks like:
Does anyone know why I'm losing the employee's name, and how I get it back?Hello David,
I guess this is a limitation of CATS application.
Please go through the below thread carefully. You can find the hint in Martin's reply.
http://scn.sap.com/thread/2123734
BR,
RAM. -
Record Working Times (ERP 2005)
Hello Everyone,
I am looking for someone who has the ERP 2005 installed and is using the Record Working Times WebDynpro in order to compare it with the ERP 2004 version. We are evaluating the improvement, incase we migrate to ERP 2005. Can someone please send me some screenshots of the standard weekly view and daily view to [email protected]
Are we able with the new one to choose the CVR profile we want to enter like in the SAP Gui ?
Are we able to enter long text greater than 40 characters ??
Do we have more flexibiltiy with column and row sizes and adding new rows ??
Thanks for all the attention...
Regards,
Paulo Poinha....
-
"Record Working Time" application in ESS
I fill the number of hours per day for all the days in a week against an Att./Abs. type in the "record Working Time" webdynpro application in ESS, review the entries and save the entries.
When i come back to check the entries for the same week, it creates multiple rows with the same Att./Abs. type and fills the number hours per day accordingly, which results in a matrix display of entries.
Edited by: Suresh Kadari on Jun 30, 2010 4:15 PMSridhar,
Thanks for your response.
I have executed the transaction CAT2 in ECC and it was working fine. If there could be a problem with Data entry profile or CAT2 program how would it work fine in the back-end.
I guess there goes something wrong with the WD application. -
Record working time giving error
hi experts,
I have implemented one sap note 1017728.The description of the note is mentioned below:
The note is related to recording of working time in portal.The note is completely implemented in sap r/3 side ,but when the user is testing the same in the portal he is getting an error:
Page 1 from 21017728SAP Note Sep 19, 20075Version
Processor PRRUDRA
Processing Status In Process
Implementation Status Processor
Processing Status
Implementation Status
Language
Short Text
Component
THEMK_NAME
NOTE_TEXT
SAP Note
Version
DATELanguage E
Short Text CATS-WD:Duplicate line is created when template is saved.
Component CA-TS-IA-XS
Description
Symptom
In record working time a duplicate line is created when the template is saved or refreshed.This happens only when the
WBS element exists in the
data profile of the user.
Other terms
WBS, Save, template, refresh, duplicate, external, internal representation
Reason and Prerequisites
Program error.This issue happens because of the comparison between the
external and internal representation of the WBS element which are different.
Solution
Apply the attached correction instructions and also follow the below mentioned manual steps.
1.Create the method COMPARE_VALUES in the interface IF_XSS_CAT_UIA_TR_ACCESS.
The parameters for this method should be as follows.
PARAMETER Type Typing Method Associated Type Description FIELDNAME Importing Type FIELDNAME Fieldname
COMPARISON Importing Type Ref To DATA
RESULT Exporting Type BOOLE_D Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Apply the corresponding Support Package to incorporate the relevant
changes.
Valid Releases:
Software Component Release
DSCR
RELEASE
RELEASE
RELEASE
DSCR
ALSTXT
ALETXT
SAP Note
Version
DATESAP R/3 Enterprise AddOn Human Resource
500
600
700
References to Relevant Support Packages:
Software Component Release Package Name:
SAP R/3 Enterprise AddOn Human Resource
600 SAPKGPHD19
Please suggest what to do.
regards
PrasunWhat about the cats profile. You need to check the cats profile. This error is of cats profile only.
if the profile is set accordingly then you wont get this error.
Its not a workflow issue
ask your wf consultant to check
The reason is that with tast 31000004 the rule is not defined.
Pl follow the step below and it will start working
1. run pftc transaction
2. select task type - standard task
3. put task 31000004
4. Click on change
5. Click on default rule tab
6. key value 00000168/00000157
7. compile it
8. go to additional data -> agent assignment-> maintain
9. select the task and click on attributes
10. select radio button general task
11. click on transfer
12. click on generate button then back
13. save
Message was edited by:
Barin Desai
Maybe you are looking for
-
No Photobooth after hard drive replacement
Wasn't sure if this is the right place to ask this question, but a couple of days ago the hard drive had to be replaced on my macbook and i have just noticed that there is no photobooth icon in the dock. I have searched using spotlight and looked in
-
Change Icon (Symbols) for Alert in Analysis Item in BI 7 Web Templates
I want to change the Icons (Symbols) displayed for alerts in the Analysis Web Item. I want to choose between arrows and stop lights. I can define this in the Table Interface in BW 3.5. In BI7 you must use the Analysis Web Item SYMBOL but it is not do
-
Can we create a file in temporary folders of the server?
Hi all, can we create a file in the temporary folders of the server by getting the server temp path using System.getProperty("java.io.tmpdir") ? I dont have access to the server. I deployed my application in the server which should create a word file
-
I need help finding out warranty information on the Apple Magsafe 2 Power Adapter. When I enter the serial number, it is too long for the box. Any help would be appreciated. Thanks.
-
Installing Update Rollup 4 for R2. Question of post installation task
I will be installing Update Rollup 4 for Service Manager 2012 R2 on our Orchestrator, Data Warehouse, Service Manager and Portal Server as well as updating the client Consoles. Following MS article http://support2.microsoft.com/kb/2989601/en-us?sd=rs