Clock-in clock-out process
Hi guys,
WRT to ESS MSS what is the clock-in clock-out process.
We are nw2004s SP9. We see the clock-in clock-out corrections ESS application. But we do not find any approval mechanism for the same in UWL for the manger. Though a work item is generated when clicked it opens the leave request approval web dynpro application.
What do we do to set up the approval mnechanism for managers through UWL?
regadrs
Sam
Message was edited by:
sameer chilama
Hi,
I am also working on clock in/out processing. How did you resolve the issues?
Thank you,
Regards
Similar Messages
-
Work flow in clock-in clock-out correction
Hi guys,
my clock-in clock-out is configured to have a approval process. The standard workflow "12300111" is assigned to the "WF ID New Clock-In/Out Entries" parameter for the clock-in clock-out correction. When i execute the report RPTCORDBVIEW it shows me the status of the WF item as been "started", but some how it does not turn up in MAnagers inbox even after a while.
The same WF when attched to leave request runs fine. Has any one faced this issue before. Myself not been pretty familiar with workflow am clueless as to what the issue coulc.
Any suggestions.
regards
Sam
Message was edited by:
sameer chilamaHi Raj,
Isnt this workflow WF12300111 'The General Workflow for Documents'? As per help.sap.com, this is the workflow we should be using for Clock In/ Out Corrections , besides Leave Request.
I am facing the same error..ie The workflow is trigerred, but the text says 'Approve Leave request" in Manager's inbox. In fact, there is no standard screen for approving the clock In/ Out corrections in webdynpro.
Have you made use of any other workflow instead?
Any inputs on the same would be greatly appreciated?
Regards,
Aditi -
Clock-in/clock out is not appearing
Dear All,
If we are giving the role SAP_EMPLOYEE_ERP & ZSAP_RFC its giving the below error, but if we are giving the SAP_ALL this service Clock-in/Clock out is opening properly. All other srvices are working normally.
ST22 ABAP Dump : No read authorization for infotype for pers. no
Please Help us find out which authorization is missing !
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 application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The current application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE
at java.lang.Throwable.<init>(Throwable.java:179)
at java.lang.Exception.<init>(Exception.java:29)
at com.sap.exception.BaseException.<init>(BaseException.java:131)
at com.sap.tc.cmi.exception.CMIException.<init>(CMIException.java:65)
at com.sap.tc.webdynpro.progmodel.model.api.WDModelException.<init>(WDModelException.java:68)
at com.sap.tc.webdynpro.modelimpl.rfcadapter.WDRFCException.<init>(WDRFCException.java:54)
at com.sap.tc.webdynpro.modelimpl.rfcadapter.WDExecuteRFCException.<init>(WDExecuteRFCException.java:57)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException.<init>(WDDynamicRFCExecuteException.java:71)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException.<init>(WDDynamicRFCExecuteException.java:43)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
at com.sap.xss.hr.wtcor.fcoverview.FcOverview.ReadCalendar(FcOverview.java:232)
at com.sap.xss.hr.wtcor.fcoverview.wdp.InternalFcOverview.ReadCalendar(InternalFcOverview.java:504)
at com.sap.xss.hr.wtcor.fcoverview.FcOverviewInterface.ReadCalendar(FcOverviewInterface.java:135)
at com.sap.xss.hr.wtcor.fcoverview.wdp.InternalFcOverviewInterface.ReadCalendar(InternalFcOverviewInterface.java:481)
at com.sap.xss.hr.wtcor.fcoverview.wdp.InternalFcOverviewInterface$External.ReadCalendar(InternalFcOverviewInterface.java:549)
at com.sap.xss.hr.wtcor.vcoverview.VcOverview.onBeforeOutput(VcOverview.java:278)
at com.sap.xss.hr.wtcor.vcoverview.wdp.InternalVcOverview.onBeforeOutput(InternalVcOverview.java:924)
at com.sap.xss.hr.wtcor.vcoverview.VcOverviewInterface.onBeforeOutput(VcOverviewInterface.java:156)
at com.sap.xss.hr.wtcor.vcoverview.wdp.InternalVcOverviewInterface.onBeforeOutput(InternalVcOverviewInterface.java:302)
at com.sap.xss.hr.wtcor.vcoverview.wdp.InternalVcOverviewInterface$External.onBeforeOutput(InternalVcOverviewInterface.java:414)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:601)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:467)
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:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:359)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:753)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:276)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:722)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:623)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:215)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:113)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:70)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:818)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1265)
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:750)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:715)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:113)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:107)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:276)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:623)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:215)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:113)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:60)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:101)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: The current application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE
at java.lang.Throwable.<init>(Throwable.java:179)
at java.lang.Exception.<init>(Exception.java:29)
at com.sap.aii.util.misc.api.BaseException.<init>(BaseException.java:96)
at com.sap.aii.proxy.framework.core.FaultException.<init>(FaultException.java:34)
at com.sap.aii.proxy.framework.core.SystemFaultException.<init>(SystemFaultException.java:29)
at com.sap.aii.proxy.framework.core.BaseProxyException.<init>(BaseProxyException.java:39)
at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:133)
at com.sap.xss.hr.wtcor.time_event_corr_adaptivemodel.TimeEventCorrAdaptiveModel.ptcor_Uia_Weekly_Calendar(TimeEventCorrAdaptiveModel.java:410)
at com.sap.xss.hr.wtcor.time_event_corr_adaptivemodel.Ptcor_Uia_Weekly_Calendar_Input.doExecute(Ptcor_Uia_Weekly_Calendar_Input.java:137)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
... 60 moreDear All,
please add infotype with read authorization in authorization object P_ORGIN with value 2011.
this will solve the above rfc error as this is related to authorization.
thanks,
Khurshid -
Doubt Clock-In/Clock-Out Corrections
Hi,
We are implementing ESS/MSS on EHP5.
I have a doubt when configuring Clock in/Clock out corrections. In SPRO "Clock-In/Clock-Out Corrections->Define Processing Processes", I left checked only the option "Corrections Have to Be Approved".
So I started the tests. I logged on with ESS user, made a correction e saved. After that I logged on POWL with the MSS user (who is the managet of the employee whose made de correction) and the entry was there. I approved, run the report RPTCORPOST and the entry was saved in TEVEN (IT 2011) table. That was perfect!!!
I went throught the second test, now with manager performing the correction for his employee. I logged with MSS user, selected the employee, made the correction and saved. In my mind, if the manager is correcting a clock-in/clock-out, it should be approved automatically. So, I run the report RPTCORPOST and the entry wasn´t saved in TEVEN (IT 2011) table. I thougth that weird, and i decided to check if the entry could be in POWL. I went to POWL and the entry was there, waiting to be approved.
The question is: Shouldn´t the entry be automatically approved when the manager performs a correction for his employees?
Thanks
BrunoHi Siddharth,
Thanks for your prompt reply. I will notifiy my customer that this behaviour is an enhance.
As a suggestion for the future ESS/MSS version, the solution could allow setup this configuration.
Thank you again.
Bruno. -
Hello All,
We are dong Clock in & Clock out in ESS. I have done with configuration.
But when i check in ESS for clock in & Clock out i'm getting error "There is no general processing process for rule group in period 11., error key: RFC_ERROR_SYSTEM_FAILURE".
Please let me know why system is giving this error.
Thank in advanceHi Eswar,
Have you check is there any dump in backend in st22 for the user.
That will be better idea of what exactly is the issue.
Thanks
Arun -
Hi All,
I have done backend config for clock-in/clock-out corrections service in r3. Now when i click on this service in portal I am getting the foll error
No more storage space available for extending an internal table., error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: No more storage space available for extending an internal table., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
at com.sap.xss.hr.wtcor.fcoverview.FcOverview.ReadCalendar(FcOverview.java:232)
at com.sap.xss.hr.wtcor.fcoverview.wdp.InternalFcOverview.ReadCalendar(InternalFcOverview.java:504)
at com.sap.xss.hr.wtcor.fcoverview.FcOverviewInterface.ReadCalendar(FcOverviewInterface.java:135)
at com.sap.xss.hr.wtcor.fcoverview.wdp.InternalFcOverviewInterface.ReadCalendar(InternalFcOverviewInterface.java:481)
at com.sap.xss.hr.wtcor.fcoverview.wdp.InternalFcOverviewInterface$External.ReadCalendar(InternalFcOverviewInterface.java:549)
at com.sap.xss.hr.wtcor.vcoverview.VcOverview.onBeforeOutput(VcOverview.java:278)
at com.sap.xss.hr.wtcor.vcoverview.wdp.InternalVcOverview.onBeforeOutput(InternalVcOverview.java:924)
at com.sap.xss.hr.wtcor.vcoverview.VcOverviewInterface.onBeforeOutput(VcOverviewInterface.java:156)
at com.sap.xss.hr.wtcor.vcoverview.wdp.InternalVcOverviewInterface.onBeforeOutput(InternalVcOverviewInterface.java:302)
at com.sap.xss.hr.wtcor.vcoverview.wdp.InternalVcOverviewInterface$External.onBeforeOutput(InternalVcOverviewInterface.java:414)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:602)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:568)
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: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:1246)
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: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: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:215)
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: No more storage space available for extending an internal table., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
at com.sap.xss.hr.wtcor.time_event_corr_adaptivemodel.TimeEventCorrAdaptiveModel.ptcor_Uia_Weekly_Calendar(TimeEventCorrAdaptiveModel.java:410)
at com.sap.xss.hr.wtcor.time_event_corr_adaptivemodel.Ptcor_Uia_Weekly_Calendar_Input.doExecute(Ptcor_Uia_Weekly_Calendar_Input.java:137)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
... 61 more
Can anyone please provide any input on this
We are on EP7 , ECC6
Thanks and Regards
ReshmaHi Reshma ,
I am also facing a similar problem as you faced : : No storage space available for extending an internal table., error key: RFC_ERROR_SYSTEM_FAILURE
Can you please explain as to how you got the problem solved
Thanks in advance ,
Vinay -
Clock-in Clock-out corrections - change existing entry
Hi,
The employee's clock-in clock-out records are updated from the time recording terminal to Infotype 2011 via an interface. Now, when we try to use the SAP's clock-in clock-out corrections application to change the existing clock-in or clock-out time for any particular day, the application is not giving the date and time fields to change. However, when we create a new clock-in clock-out entry from ess, we are able to change the date and time for that entry but not for any entry that is transferred from the time recording terminal.
Any idea if the standard application can be used to change existing clock-in clock-out record or how can this scenario be met in ESS?
Thanks,
Deepa Balanito ensure entries can be changed refer customisation in table V_PTCOR_WFATTR.
SPRO->Personell Managment->ESS->Service Specific Settings->CLOK in CLock
out Corrections->Processing Processes->Define Processing Process's docu
ment which reads:
Define Processing Processes (V_PTCOR_WFATTR)
this should be unchecked
Clock-In/Out Entries Cannot Be Changed
Specifies whether employees are permitted to change original clock-in/out postings (time events in the TEVEN table).
Note:
Time events that have been processed by a time administrator in the Time Events infotype (2011) cannot be changed or deleted in the Web application. >>>>>>>>>>> note this so you cant change, of course one can change already entered ESS time entries
This is a clock in clock corrections application where
in you can correct the Clock ins but cannot delete
the times entered through the terminal, but can
delete those corrections done through the application
itself. So in your case you can see
the difference, this application is not meant to
replace the recording terminal but to enhance it -
Clock-in Clock-out correction in ESS BP 1.0 2004s sp9
hi guys,
The clock-in clock-out correction application from XSS(ESS-MSS) looks to be incomplete from a process view. In the ESS application I can see that ther eis an aplication for Employees to change clock-in clock-outs. But ther eis no approval mechansim assocaited to it. When i assign a WF to the PRocess in the customization, the request goes and sits in the MWW UWL, but the manager does not ahev an opitio to actuall approve it or reject it from UWL. I do not see any web dynpro application for the approval mechanism as we see for the leave request approval mechanism.
The documentation also never says that manager can approve from the web.
Am i missing anything here or is this the general process that Managers have to approve from the backend and no topiton to approve from MSS.
It would be silly to explain to managers that they have to access UWL to approve leave and log on to R/3 to approve clock-in clock-out corrections.
Please let me know if i am m issing anyuthing here.
regards
sam
Message was edited by:
sameer chilamahi all
The documentation provided by SAP is misleading. SAP is in process of correcting the same. if you are looking at implemeting the workflow for clock in/out correction please follow the steps mentined below.
We have done this and it successfully works.
Description : Clock in/ out correction service under employee self service has a facility to use the worklfow but there is no workflow available that can be readily used. SAP advises to copy the standard leave workflow (WS12300111) and use the same. There is an approval program available (Transaction PTCOR -> Approve Docuement) for administrator. Using the same program we will be creating an approval workflow.
1. Create a custom transaction calling report program RPTCORAPP and selection screen 1000.(ZPT_APPROVE)
2. Create another custom transaction(Z_APPROVE_CLINOUT) with following code.
Call transaction ZPT_APPROVE AND SKIP FIRST SCREEN.
3. Using transaction sw01 create an object where call the above tranasaction.
4. Create a custom task with the above object and method (STEP 3) (There will be no parameter passed between the task container and the workflow as we are calling a transaction only)
5. Create Copy of WS12300111 using transaction SWDD.
6. Delete the step Process Request by Employee (TS12300116) from copied workflow.
7. In the copied workflow in the Approval process instead of standard approval task use the custom task created in step 4.
8. Activate the customized workflow.
9. Under spro config please follow the link Personnel Management -> Employee Self-Services-> Service Sepcific Settings-> working time ->Clock in\out Corrections-> Processing Processes -> Define Processing Processes
Under workflow template select the checkbox Use SAP Business Workflow.
Provide the number of Custom Workflow activated in Step 8 in the following fields.
WF ID New Clock-In/Out Entries
WF ID for Deletion of Entries
WF ID: Changed Clock-In/Out Entries
Once you are done with this process then on entering the clock in/ out time the workflow will be received by the next agent defined in the rule / expression that is used in workflow.
The output will work according to the report(RPTCORAPP) if in case there is any need to make change then a copy of the classes can be created that are used in the approval report and customization can be achieved. -
Doubt Clock-In/Clock-Out Approval
Hi,
We are using POWL inbox to approve clock in/clock out corrections.
I would like to know if it´s normal when clicking on the links of the column "Type of Correction" it doesn´t happen anything.
Follow a image regarding it
Image
Thanks,
BrunoClock in/out corrections approval has been developed and is present in
MSS addon 1.0 and not in ESS Ehp5.
In the MSS addon 1.0 we have a new query for processing clock in/out
corrections approval, similar to the leave request scenario. Also, we
have Webdynpro ABAP CICO approval detail screen where in the manager can
view the details of the CICO correction and could process the
requests(Approval/Reject). He could also navigate between the Clock
in/out requests using the Next and Previous buttons.
We recommend you to implement the MSS addon 1.0.
Regarding other enhancements provided in the MSS addon 1.0, please
refer to the note 1588625.
are you a ramp up customer for MSS ADD ON?
Please note to install this S/W component there are a few pre-requisites
that your Ehp5 system has to be at.
Software Component SAP_BASIS 702 SP07
Software Component SAP_ABA 702 SP07
Software Component SAP_BS_FND 702 SP05
Software Component WEBCUIF 701 SP04
Software Component SAP_HR 6.04 SP035
Software Component EA_HR 6.05 SP012
If you want to get to ramp up, Please let me know
If not you need to use RPTCORAPP for approval! -
How to delete the messages in clock-in/clock-out
Hi All,
I need to delete the messages in clock-in/clock-out which are appearing in portal, to delete this messages is there any report at R/3 side kindly suggest me help me in this
waiting for your responses .....
Regards,
Shilpa.you can run the report RPUP1D00 for the periods that you need to delete
the messages without any problems, but please read the documentation
carefully before starting.
Please note, that RPTERR00 always reports ALL errors. It does not matter
in which period they appeared. Please destinguish between errors and
notes.
The errors which appear during a time evaluation run are stored in table
ERT in cluster B1 and in table FEHLER in cluster B2 are intended to
store and display those errors as long as the errors are not corrected.
If you don't want these errors to be displayed any more you either have
to correct the errors or you must delete Cluster B1 via report RPUP1D00.
The old NOTES are transferred from the ERT/B1 to FEHLER/B2 with each
subsequent run of time evaluation.
Your time administrators should normally work with PT40 and confirm
'I' messages or correct errors by using the error handling.
This report can be run like this
Relation ID 'B1'
Sort field Pers.no. (eight-digit)
Delete? X
Password Username -
Clock in clock out corrections error
Hi;
We have implemented ESS/MSS.
We have employees from 4 companies accessing the portal.
Employees of 3 companies can do their clock in clock out corrections properly.But the employees of the 4th company get a dump when they click on the clock in clock out link.
The error is as follows:
The current application triggered atermination with a short dump,error key:RFC_ERROR_SYSTEM_FAILURE.
Can any one help us with this?Agreed with the other poster, please include details from your system dumps ST22 and SM21 logs. In addition inspect the NWA logs on the java stack to determine route failure.
Given that you have only 1 group terminating on RFC calls, it may be that this group does not have sufficient authorisation to leverage the RFC call or it may be that they use different EP System objects (should you have split EP roles) that are not configured correctly in EP. Hard to be correct since I am flying blind, but may be worth checking out. -
Clock In Clock Out Report without running Time Evaluation
Hi Every1
Is it possible to get report on clock in clock out without running time evaluation?? Can we get a report on Time events after uploading Punch in punch out from other system thru BDC?
Here requirement is as soon as punch in punch out is uploaded on daily basis thru BDC they shud get a report on Clock In from th system so that they can immediately find out in morning shift how many employees are present.
Thanks & Regards
NehaWell what tables are you uploading in the BDC ?? are the PTX tables being uploaded or the PA2011 Tables uploaded ?
If the PA2011 Tables are uploaded then yes we can run a report for each day as required but if the PTX tables are updated then they are either waiting for managers approval or to be transfered to HR which triggers updation of the Infotypes accordingly.
And when you transfer to HR i guess Infotype 2011 is not updated but rather 2001 and 2002 Tables are updated but have to check on this, time eval schema would not update 2011 Infotype but rather would update ZL tables with time types if present, try to figure out what table the BDC updates each night.
Edited by: insane saint on Jul 14, 2009 10:38 PM -
Clock-in Clock-out corrections using ESS
Hi,
When we change the Time data using Clock-in, Clock-out corrections in ESS, it is not appearing in 2011 (Teven table). When will this, gets updated to the table and is there any tiem limit set for the updation ??
Thanks & Regards,
Vidhya T.ROn ESS, there will be optoin to run Time evaluation. Generally the update happens after the Time eval.
If this helps, pl do reward.
Thanks
Narasimha -
Hi All,
I have a requirement for Clock in Clock out approval. Program RPTCORAPP is used to approve bulk clock in and clock out. But this program will not support for Substitutions. Can any one please provide details for handling substitutions by copying RPTCORAPP into Z-program.
Thanks,
SCHi Siddarth,
Now I copied the RPTCORAPP to Z-program and made changes for substitutes records for clock in out. For normal corrections it is reflecting properly where the link is open properly. But for substitutes it is not showing link in approval page where as record is displaying. So we canot open the request. How to do our newly added substitute records as link so that we can see the details of that request.,
Following changes I had done in Z-program.
First getting the substitute manager userids from table hrus_d2. Getting personnel numbers from that user ids.
And after that once again by using the subroutine get_worklist_for_approver and storing the worklist in temporary internal table. After that adding this temporary internal table records to main internal worklist event_data.
Other than this any thing changes we have to do for getting links in clock in out for approvers inbox.
Thanks,
SC -
Clock-in/Clock-out Request
Hi Experts,
Iam getting the error message in Clock-in/Clock-out when iam trying send the
request for the manager for approval the error is
Unable to send the request
you are not one of the possible agents of task ' WS99900004'
but the agent is already assigned for the user
waitng for your responses
Regards,
ShilpaHi
Already the agent was assigned and the agent is dynamic and it is general task so
any user id can acess it .
Regards,
Shilpa
Maybe you are looking for
-
Why do I get this error when executing this javascript?
== Issue == I have another kind of problem with Firefox == Description == <code>var firefoxWindow = getWindows()[0]; var browser = firefoxWindow.getBrowser(); var doc = browser.contentDocument; var elem = null; var elems = doc.getElementsByTagName('t
-
When I open Safari, it goes to the home page but there is no tool bar at the top of the window, and the home page is in the middle of a white window that is full screen. I cannot do anything with Safari because there is no toolbar. how do I get the t
-
Characteristics _organisational structure
hi there.. please let me know if my understanding is correct about the characteristics for which we can generate internal balance sheet and profit and loss statement. 1) with Classic GL is it only Business Area for which internal b/s and p&l can be c
-
Open Directory LDAPv3 Password and Diradmin recovery
Hi Everyone, I have just inherited a 10.4.x PPC G5 server from another department and unfortunately the previous sysadmin didn't write down the Open Directory Admin username and password. Is there a way I can recover the username and reset the passwo
-
I have stored password in password manager. it is working properly but in last few day only account name appears and in password bar there is no password. How can I solved this problem?