Clock-in/clock-out reason column

Hi Experts,
In manager clock-in/clock-out view a table will be there to approve the corrections but i need to add
one more cloumn which consists is of reason so to get this reason we used t55d and t705a view
but the reason for text is not updating accordingly please help me in this
Thanks & Regards,
Shilpa

Are you suggesting you are unable to see 'reason" info despite adding this field to MSS screen?
Can you please explain how did you manage to add this field... probably you have missed out something to read this additional field...
Also please check if reason is saved in backend as suggested by Siddharth
Rgds

Similar Messages

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,
Bruno

Clock 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

Is it possible to have Clock in and clock out times in weekly view

Hi,
We have Daily View and Weekly View in Record Working Time iview in ESS.We can set the Clock in and Clock out times in Daily view if we check the With Clock Times checkbox in Data Entry Profile.But we want to have same Clock in and Clock out in Weekly view without any developement.
If it not possible thru config how much will be the Development Effort
Thanks
Bala Duvvuri

Siddharth,
can you please elaborate this
Thanks
Bala Duvvuri

Is it possible to have clock in and clock out in weekly view

Hi,
We have Daily View and Weekly View in Record Working Time iview in ESS.We can set the Clock in and Clock out times in Daily view if we check the With Clock Times checkbox in Data Entry Profile.But we want to have same Clock in and Clock out in Weekly view without any developement.
If it not possible thru config how much will be the Development Effort
Thanks
Bala Duvvuri

Hi Bala
You can have clock in and clock out in a weekly view.
you have to change the data entry profile settings.
In general settings tab in data entry profile click the with clock times button and maintain the Period type to 02 in time settings tab.
And you can view the weekly entry in clock in and clock out.
Ravee
+91.99206.33669

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 chilama

Hi 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 more

Dear 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

No midi clock out on AMT8 ports 4-8

Hi, Logic 9, with daisy chained Emagic Unitor8's and AMT
Unitory8->Unitor8->Amt8
I"m getting midi clock out on all ports except the last 4. Does anyone have a suggestion on how to make this work or if it is even possible?
- Joel

Joel,
If you change the order... is it always the last 4 ports that aren't getting MIDI clock. If you use two devices Unitor8->Amt8, are you getting all 16?

Clock-in and Clock out timings in ESS

Hi,
My client want to display the Clock-in Clock-out timings recorded at the terminal (we are not using CATS) to be displayed in ESS portal.Pleae let me know where (in which node) and how to do this.
Thx
J

You can use Clock in clock out iview which is standard available in EHP5 too, It displays clock in events from Teven!
ie 2011 infotype
check here more
http://help.sap.com/erp2005_ehp_05/helpdata/en/25/340b0507434193adbfe3f8fc8896c7/frameset.htm
do the customisaiton in PTCOR trans code in backend!

Clock in and clock out issue

Hi All,
I am looking for a solution for the below issue. Please help me out
Clock in and clock out details from third party terminal are stored in SAP in IT2011.
My requirement is if the duration between first clock in and last clock out is less than 4 hours system should consider as LOP for that day.
can you please let me know if I should a PCR or any other way.
Regards
Vish

You can do as below:
Normally time type 0000 is used for normal attendance hrs in time schema PCR's like TP09, TP10, TP11.
Before CUMBT function, call a PCR using ACTIO to do as below:
If the daily value is time type 0000 < 4.00, insert a w/t for LOP absence hrs for the day. The hrs can be as per the business rules:
a)from IT 7 - provided IT 7 has the correct data from WSR and WSR is correct.
HRS=IDAHRS           daily hrs
or
HRS=IWEHRS HRS/5    weekly hrs/5
or
b)from the DWS for that day
HRS=S        -DWS hrs including any substitution
See example below assuming 0000 time type for normal attendance hrs, 8001 time w/t for LOP hrs.
             D   HRS=D0000    HRS?4
<                HRS=IDAHRS ADDZL8001
In payroll,
- Time w/t's from time eval are imported by ZLIT function (usually in XT00 sub schema).
- PCR XPPF and its sub PCRs this w/t hrs can be used to reduce the partial pay factors e.g. /801 used to reduce the payments like basic pay, etc.
- PCR XVAL uses these factor w/t's to reduce the payments.

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
Bruno

Hi 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.

Clock in , clock out and absence issue

Hi friends,
In our company, planned working time is 7:00 to 16:00.
I have an approved absence request from 8:00 to 10:00, but instead of 8:00 I left company at 8:20.
So my time events are as below:
clock in = 7:00
clock out = 8:20 (instead of 8:00)
clock in = 10:00
clock out = 16:00
approved absence request = 8:00 to 10:00
my expectation from system:
delimit my absence from 8:20 to 10:00.
Which customization are necessary in which table or PCR or Schema?
I really appreciate any help you can provide.
Best Regards,
Leila

Hi Leila,
In your positive time schema, you will have to ensure that functions P2011 and P2001 don't have any parameters maintained. First call in function P2011, then function P2001 and then the custom function. The function P2002 will come in after P2001.
The input and output of your custom function will be Table TIP. You should ask your ABAPer to compare time pairs of pair type 1 (IT2011) with time pairs of pair type 2 (IT2001) in Table TIP.
Whenever there is an overlap between time pairs of IT2011 and IT2001, it means that the absence record would need to be adjusted. You should determine whether the start time or end time of the absence needs to be adjusted.
Based on that, you should pass an entry in a staging table with the details of the absence type to be replaced.
In your case, you will pass an entry in your staging table to adjust your absence type from 8:00 - 10:00 to 8:20 - 10:00. We are using the staging table because during time evaluation run, master data is locked and the custom function won't be able to update IT2001.
You also need to create a posting program which will read data from staging table and update IT2001. You should schedule this posting program as a background job at 1 hour frequency to update IT2001. In some cases, master data will be locked and hence, the posting program will leave the record in staging table. Once the record is successfully posted in IT2001, it should delete the record from staging table.
You can keep an option that the program should try to post a max of 10 times and if it is unable to post in 10 attempts, it should an email notification to the HR team regarding this.
I hope this information is helpful for you and will help you design the solution.
Thanks and regards,
Vivek Barnwal

Clock-in & clock-out in cources

hello
I want to check clock-in and clock-out pepole for each business event type
how to check it?

Hi Mas,
If you are using clock-in/out for each session of any trining you should look the data in time management module if you are using it. Go into PA30 and look at infotype 2011.
Regards,
Omid

Clock in & Clock out in ESS

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 advance

Hi 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

Clock in Clock Out

Hi,
After running the time evaluation the clock in and clock out corrections is not appearing on the portal.
We are using CATS for service provider to enter the clock in and clock out. Is there any back ground jobs which have to be run for the data to flow into the portal or is it any configuration settings.
Request help on the matter.
-shobha

Hi,
Technical Data
Runtime Technology
Web Dynpro Java iView
Technical Name of iView
com.sap.pct.erp.ess.timecorrection
Technical Name of Web Dynpro Application
sap.com/ess~wtcor/WTimeCor
Service Key
EMPLOYEE_WORKTIME_TIMECORRECTION05
Available as of
SAP NetWeaver 2004s
Data Source
SAP ECC 5.0 and higher
RFC function modules called:
PTCOR_SEARCH_NEXT_PROCESSOR
PTCOR_UIA_CUSTOMIZING_GET
PTCOR_UIA_EVALMESSAGES
PTCOR_UIA_FORM_ACCEPT
PTCOR_UIA_FORM_DELEGATE
PTCOR_UIA_FORM_PREPARE
PTCOR_UIA_TIME_ACCOUNTS
PTCOR_UIA_WEEKLY_CALENDAR
Software Component
EA-HR 500 and higher
Support
PT_RC_UI_XS
Support Languages
All languages supported by SAP
Use
Employees can use this Web application to correct, in a weekly overview graphic, errors that originated due to incorrect entries at the time recording terminal. For example, they can correct duplicate clock-ins or enter missing entries and account assignment data. An optional monitoring function and approval procedure enable the entries changed, deleted, and created manually to be checked and approved.
Kind Regards,
Saisree.s

Clock-in/clock-out reason column

Similar Messages

Maybe you are looking for