Clock in /clock out posting problem

Hi,
I am facing a problem in clock in / clock out correction posting. For this we have scheduled program RPTCORPOST in backgroud. For some employees the posting is not happening in R/3 even though the status in PTREQ_HEADER table is showing posted.
Which area should i concentrate for solving this problem.
Regards,
Mohammadi

Hi Mohammadi,
Am also facing the same problem. Did u get any solution for this? If yes, please do share with us.
Thanks in advance,
RSS.

Similar Messages

  • 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 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 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 error

    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
    Reshma

    Hi 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

  • Clockin/clock-out Approvals in 4.7

    Hi,
    We are investigating the option of manager's approving the clock in clock-out times on the 4.7 landscapes. I am looking for similar reports as below that exist in the ECC 6.0 system. Anyideas how clock in / clock-out can be approved in teh 4.7 syste, or wuld this have to be a complete customd development?
           RPTCORTMAIL (Clock-In/Out Corrections: Request Correction of Errors)
    ·        RPTCOREMAIL (Clock-In/Out Corrections: E-Mails to Involved Persons)
    ·        RPTCORPOST (Clock-In/Out Corrections: Post)
    ·        RPTCORSTOPWF (Clock-In/Out Corrections: End Open Processes)
    ·        RPTCORLIST (Clock-In/Out Corrections: Check Corrections)
    ·        RPTCORAPP (Clock-In/Out Corrections: Approve Documents)
    ·        RPTCORERR (Clock-In/Out Corrections: Process Errors in Entries)
    regards
    Raj

    Hi Judith Karunaha,
    I am again lost as is the case with other suggestions or comments you have pasted for my other queries.
    Can you explain what this means
    if you are sure, these are met through version 4.7 , they are available in ECC
    Please dont stress ur self if you have to here as I have devised the strategy here. Just curious what u meant here though

  • 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 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

Maybe you are looking for

  • Extended Withholding Tax  (India)

    While testing TDS calculation at the time of payment posting I am facing a problem. TDS is not being calculated. System is asking Tax Code of TAXINN tax procedure such as input tax, output tax etc. I have done the settings of W/H type, code,recipient

  • I just got myself a macbook how do I back it up

    I just got myself a macbook and learning how to use it not sure how back it up I'd switched it on but when I close it's off again  I manage to put my printers drive inside the window can anyone help I have time machine I hear you guys talk about boot

  • Iphone 4 not turning on

    my phone stop working.  need help

  • Black Up-Date for Lumia 810

    I live in US ( for just about 2 years) so i got the 810 from T-Mobile last year. Now I see that Lumia Black update is listed as "Not available" for my phone. I saw on the Nokia site that the update it's avaible for all the Lumias so I gues the  T-Mob

  • Can I upgrade OSX from 10.5.8 to snow leopard?

    Can anyone help by telling me if I can upgrade to 10.6 snow leopard?