Record Working Time 500 Error

We just upgraded to ECC 6.0, Netweaver 2004s, Portals v 7.0 sp 09. When stress testing we started receiving a 500 error in Record Working Time. This is the only service that we receive the error. When one or two users enter time, we never get the error. Has anybody else seen this error. I including the error message we received -
com.sap.tc.webdynpro.progmodel.context.ContextException: NodeElement(VcCatTableWeek.TimesheetHeader.0): unknown attribute POSID_H_Value
at com.sap.tc.webdynpro.progmodel.context.NodeElement.wdGetAttributeInfo(NodeElement.java:374)
at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeValue(NodeElement.java:868)
at com.sap.xss.hr.cat.record.vac.entry.VcCatTableWeek.addFixHeaderLines(VcCatTableWeek.java:581)
at com.sap.xss.hr.cat.record.vac.entry.wdp.InternalVcCatTableWeek.addFixHeaderLines(InternalVcCatTableWeek.java:133)
at com.sap.xss.hr.cat.record.vac.entry.VcCatTableWeek.wdDoModifyView(VcCatTableWeek.java:510)
at com.sap.xss.hr.cat.record.vac.entry.wdp.InternalVcCatTableWeek.wdDoModifyView(InternalVcCatTableWeek.java:193)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:487)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
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:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
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:879)
at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1291)
at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:831)
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:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
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:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Our cut over to the new release was Dec. 18th, 2006.  We discovered the problem on the 11th during a stress testing.  We immediately created an OSS note for SAP.  They did not really engage in the note for 3-4 weeks.  After several discussions with our Sales Rep, they finally elevated the issue to High Priority.  As of today, they have identified the problem and are working on the resolution.  As soon as we get the fix and have tested it, I’ll update this message with the results.

Similar Messages

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

    What 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

  • Record Working Time(WDJ) error

    Hi,
    I keep getting this "TARGET_HOURS_ERROR" error, when I access the ESS
    page in my Portal.. but if I fill the buffer by executing the
    READ_TARGET_HOURS Method of the Class CL_XSS_CAT_EMPLOYEE in the
    backend (in Test Mode) & then access the Record Working Time iView,
    the error is gone.. I'm not sure why the buffer isn't getting filled
    when I access the iView directly.The following is our system configuration..
    SAP_ABA - SAPKA70012
    SAP_BASIS - SAPKB70012
    PI_BASIS - SAPKIPYM01
    SAP_HR - SAPKE60018
    EA-HR - SAPKGPHD18
    SAPEP - NW04s SP13
    ESS - ERP1.0
    Any suggestions/experiences on this error pl?
    ~Suresh

    the WDJ appalication expects a months time when reading the Target Hours.. We had a User Exit to populate the time for only 14 days.. this was causing an exception in the backend whie reading the Target Hours.. Once the User Exit was deactivated, the iView came up as expected..
    Thanks to Sireesh ( SAP Development ) for identifying the issue..
    ~Suresh

  • Record Working Time  iView Error in Portal

    Hi
    In Record Working Time ivIew in SAP Portal when we are selcting the date from  the Calendar
    we are getting the below Error as 
    The initial exception that caused the request to fail, was:
       java.lang.IllegalArgumentException
        at java.sql.Date.valueOf(Date.java:138)
        at com.sap.tc.webdynpro.clientserver.uielib.standard.uradapter.DateNavigatorAdapter.onDATENAVIGATORDAYCLICK(DateNavigatorAdapter.java:438)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        ... 43 more
    For certain dates  in  Calendar Year 2010, I am not getting the Error .But  whichever date I am selecting from Year  2011 I am getting the above error.
    Can any one please let me know about this issue 
    Regards
    Alexi

    Alexi,
    check this link
    http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES and see if there is any compatibility issue.
    check for some notes in service market place
    Thanks
    Bala Duvvuri

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

  • Reg: Record Working Time Daily View

    Hello Guru's
    We are facing an issue in Record Working Time Daily View,
    When clicked on the details link in Daily view it is dumping. If there is any data in one of the row then the details link is working fine but when data is not there then it is giving the dump as below:
    I also checked the Note 1312238, 1371294 which is not applicable in our scenario.
      Record Working Time   
      500   Internal Server Error
      SAP NetWeaver Application Server 7.00/Java AS 7.00 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.pcuigp.xssfpm.java.FPMRuntimeException: An unknown error has occurred in the system.
        at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
        at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:480)
        at com.sap.xss.hr.cat.record.blc.RfcManager.rfcJumpToDetail(RfcManager.java:515)
        at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.rfcJumpToDetail(InternalRfcManager.java:240)
        at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onJumpToDetail(FcCatRecordInterface.java:928)
        ... 53 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Hot Lingo 2.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
    Version null
    DOM version null
    Client Type msie7
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0020.20091014050424.0000 (release=NW04S_20_REL, buildtime=2009-10-14:03:30:40[UTC], changelist=67920, host=pwdfm114), build date: Tue Nov 03 14:44:56 MET 2009
    J2EE Engine 7.00 PatchLevel 65302.450
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_20-rev-b04, vendor: Sun Microsystems Inc.
    Operating system SunOS, version: 5.10, architecture: sparcv9
    Session & Other
    Session Locale en_GB
    Time of Failure Tue Dec 29 00:06:07 MET 2009 (Java Time: 1262041567864)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0019.20060802152219.0000 (release=645_SP_REL, buildtime=2009-03-30:14:54:41[UTC], changelist=413172, host=PWDFM093.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0019.20060802152219.0000 (release=645_SP_REL, buildtime=2009-03-30:14:54:47[UTC], changelist=413172, host=PWDFM093.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0019.20060518081436.0000 (release=645_SP_REL, buildtime=2009-03-30:14:47:06[UTC], changelist=403550, host=PWDFM093.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0019.20080917125552.0000 (release=645_SP_REL, buildtime=2009-03-30:14:59:47[UTC], changelist=501499, host=PWDFM093.wdf.sap.corp)
    SapMetamodelCommon 7.0019.20090211122608.0000 (release=645_SP_REL, buildtime=2009-03-30:14:47:47[UTC], changelist=516631, host=PWDFM093.wdf.sap.corp)
    SapMetamodelCore 7.0019.20090211122608.0000 (release=645_SP_REL, buildtime=2009-03-30:14:47:42[UTC], changelist=516631, host=PWDFM093.wdf.sap.corp)
    SapMetamodelDictionary 7.0019.20060518081418.0000 (release=645_SP_REL, buildtime=2009-03-30:14:52:36[UTC], changelist=403548, host=PWDFM093.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0019.20080730122929.0000 (release=645_SP_REL, buildtime=2009-03-30:14:57:02[UTC], changelist=494915, host=PWDFM093.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0019.20090325154034.0000 (release=645_SP_REL, buildtime=2009-03-30:15:07:12[UTC], changelist=520916, host=pwdfm093)
    SapWebDynproGenerationCore 7.0019.20080917125552.0000 (release=645_SP_REL, buildtime=2009-03-30:14:59:52[UTC], changelist=501499, host=PWDFM093.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0019.20090325154034.0000 (release=645_SP_REL, buildtime=2009-03-30:15:07:12[UTC], changelist=520916, host=pwdfm093)
    sap.com/tcwddispwda
    No information available null
    sap.com/pb_api
    SapDictionaryGenerationCore 7.0018.20081020084244.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:11:27[UTC], changelist=49368, host=PWDFM114.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0018.20081020084244.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:11:33[UTC], changelist=49368, host=PWDFM114.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0018.20081020084310.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:00:07[UTC], changelist=49373, host=PWDFM114.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0018.20081020084840.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:17:27[UTC], changelist=49426, host=PWDFM114.wdf.sap.corp)
    SapMetamodelCommon 7.0018.20081020084443.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:00:58[UTC], changelist=49392, host=PWDFM114.wdf.sap.corp)
    SapMetamodelCore 7.0018.20081020084443.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:00:53[UTC], changelist=49392, host=PWDFM114.wdf.sap.corp)
    SapMetamodelDictionary 7.0018.20081020084251.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:08:56[UTC], changelist=49369, host=PWDFM114.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0018.20081020084854.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:14:16[UTC], changelist=49427, host=PWDFM114.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0018.20090128140814.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:26:55[UTC], changelist=53714, host=pwdfm114)
    SapWebDynproGenerationCore 7.0018.20081020084840.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:17:33[UTC], changelist=49426, host=PWDFM114.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0018.20090128140814.0000 (release=NW04S_18_REL, buildtime=2009-01-31:21:26:55[UTC], changelist=53714, host=pwdfm114)
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.pcuigp.xssfpm.java.FPMRuntimeException: An unknown error has occurred in the system.
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
         at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:480)
         at com.sap.xss.hr.cat.record.blc.RfcManager.rfcJumpToDetail(RfcManager.java:515)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.rfcJumpToDetail(InternalRfcManager.java:240)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onJumpToDetail(FcCatRecordInterface.java:928)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onJumpToDetail(InternalFcCatRecordInterface.java:308)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onJumpToDetail(InternalFcCatRecordInterface.java:582)
         at com.sap.xss.hr.cat.record.vac.entry.VcCatRecordEntry.fireEvent(VcCatRecordEntry.java:367)
         at com.sap.xss.hr.cat.record.vac.entry.wdp.InternalVcCatRecordEntry.fireEvent(InternalVcCatRecordEntry.java:182)
         at com.sap.xss.hr.cat.record.vac.entry.VcCatRecordEntryInterface.blcEvent(VcCatRecordEntryInterface.java:175)
         at com.sap.xss.hr.cat.record.vac.entry.wdp.InternalVcCatRecordEntryInterface.blcEvent(InternalVcCatRecordEntryInterface.java:161)
         at com.sap.xss.hr.cat.record.vac.entry.VcCatTableDay.onActionDisplayDetails(VcCatTableDay.java:685)
         at com.sap.xss.hr.cat.record.vac.entry.wdp.InternalVcCatTableDay.wdInvokeEventHandler(InternalVcCatTableDay.java:172)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         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:332)
         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: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:869)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1356)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869)
         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:332)
         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: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: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)
    Kindly help me in solving the issue.
    Thanks & Regards,
    Pramod
    Edited by: Suresh Datti on Dec 29, 2009 11:52 PM

    Hi Pramod,
    Did you try this note
    Note 1307629 - CATS WD: Dump while clicking on 'Details' link in Daily view
    Thanks
    Bala Duvvuri

  • Record Working Time Error

    Hello Gurus,
    When I click on Record Working Time in ESS, I'm getting an error Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE. Please adice
    Regards
    Francis.

    Hello Francis,
    We also have a new note 1428947 which handles this issue.
    Please have a look at
    https://wiki.sdn.sap.com/wiki/display/ERPHCM/ChecksforthePROFILE_NOT_INITIALIZEDissue.
    Regards,
    Bentow.

  • Error in record working time ESS application for an user

    Hi ,
    We are getting the below error for a specific user when he is accessing the ESS Record working time application.
    Please find the below error.
    12:06_28/02/11_0009_1265450
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Problem creating the Application Integrator, please look for a previous exception during onNodeReady()
    at com.sap.portal.wdintegrator.WebDynproIntegrator.doContent(WebDynproIntegrator.java:59)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.doRefresh(AbstractPortalComponent.java:355)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:188)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    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)
    Thanks and Regards,
    Rajesh

    Hi,
    I am facing similar issue. Did you get solution for this?
    Regards,
    Apurva

  • Error in Record Working Time

    Hi,
    Whenever an user clicks on the link "Record Working Time", it gives an error The profile in use has      65 columns. A maximum of 40 columns are allowed.
    The CVR parameter is maintained and also the Profile is maintained.
    Can anyone please help me with this?
    Thanks and Regards,
    Pinki

    Hi pinki,
    Using tcode cac2 you can hide certain columns which you do not need. So that you do exceed limit.
    Hope that it will be helpful.
    thanks
    arun

  • Error with ESS-Record working Time

    While trying to create record for timesheet thorugh CATS on ESS > Record working time I get the following error : Could any one guide me the same please.
    08.07.2013: Counting rule 1/07/030 does not exist
    Erroneous records exist. Navigation is not possible
    Regards,
    Ayesha

    Hi,
    Some more issues .
    1: I am not able to view any Attendance type/Absence type in Timesheet page , though i have selected it as an input field.
    2: I needed an additional field with free text, so selected additional field as an input but not getting this also in ESS.
    3: I got these fields  Project and Project subobject, but these are disabled ones, with no LOV or free text option. I want to know how do i get values here , is there any PA or OM infotypes ,where i can assign Project details and then fetch it here ?
    4: Task Type , Level and Component.
    Type
    Level
    Component
    1
    A
    A1
    A2
    2
    B
    B1
    B2
    This appears correctly, but my issue is when I select type 1 , in Level I can view A and B, also all the component are appearing, if you select level A.
    I want to restrict this. When I select type 1, I should be able to view only Level A. Is this possible in Stanndard ? Same for Level and component asignment.
    Regards,
    Ayesha

  • ESS Record working time error "Profile not initialised" TS31000007

    Hi,
    This is with reference to approvals of Times in ESS . I have copied the task TS31000004  to my custom task. I have made a custom rule to determine the superior in the Z task i have created.
    Wehn i try to assign the Z task created  to the Data entry profile in the "with approval" section( *** use sap business workflow *** ) , it gives me an error "Profile not initialised" . If i remove the check box for "Use SAP Business workflow" and do not enter any task there, the record working time screen is shown in ESS.
    Any idea why it is giving the "Profile not initalised" when i assign the workflow in data entry profile.
    Your help is apprecaited.
    Regards
    PN
    Message was edited by:
            Portal Newbie

    Hi Haydn,
    I have check the wokflow through CAT2 in SAP R3. When i save the CATS record, it send a workflow task to the superiror identified through by custom rule.
    If i try it through front end ESS, the same is not working and is throwing "PROFILE_NOT_INITIALIZED" error.
    I have down the following
    1) Copy the standard task TS31000004 to ZTS31000004
    2) Assigned it as general task, assigned the custom rule in Default rules for agen determination
    3) Assigned the Task in Data entry profile, checked the box "Use SAP Business workflow" in data entry profile.
    4) In Portal i have registered the UWL system, note i am not getting the ZTS31000004 in UWL xml file.
    Do i need to ADD the new ZTS31000004 in SWFVISU and delete the standard TS31000004 provided and re-register system ?
    also do i need to create the events in SWETYPV for this Tasks as they are not present there?
    Your help is appreciated.
    Regards
    PN
    Message was edited by:
            Portal Newbie

  • ESS - Record Working Time Error Display and Approved Time in Calendar doesn't update color

    Hi Experts,
    We are using EHP7/NWBC. On ESS under Record Working Time when an employee enter time, system error message displayed on screen. Even through the message appears, employee able to submit time and manager can approve it.
    We would like to know, how to remove this error message. We tried through clearing error log but when employee logs back in, it again appears.
    And also, when Manager approves time, for the approved data Calendar doesn't get updated and employee don't have details that manager approved or not.
    Appreciate your response to resolve these two issues.
    Error Message Screenshot:
    Thanks,
    Ashish

    http://scn.sap.com/thread/3346594 http://scn.sap.com/thread/2135503

  • Authorizations for Record Working Time

    hi experts,
    I assigned the copied role Z_SAP_EMPLOYEE_ERP to a ESS user on R/3 side. The user is trying to access Record Working Time web dynpro application on Portal. He gets an error "there is no authorization to this activity". Does the standard role SAP_EMPLOYEE_ROLE not have the required authorizations?
    If not, what authroization is needed for accessing CATS Web Dynpro on portal?
    I appreciate your help.
    Regards

    Hi
    Also check these:
    1. In IT105 create a record assigning the user id to the personnel number in subtype 0001.
    2. Ensure that the profile you have provided in CVR parameter and the profile you have customized are one and the same. Else, SAP will default 'ESS' profile to the employee on Portal.
    3. If the above doesn't work out, create a new user in HRUSER - tcode, assign proper R/3 & ESS roles, parameter and then test.
    If this helps, pl do reward.
    Thanks
    Narasimha

  • Time Constraints on ESS - Record Working Time and Leave Request

    Hi All,
    I have configured Time Constraints and their reaction in V_T554Y.
    When I record the appropriate combination of Attendances and Absences in back-end, I can see the reactions as specified... However, when I try to do the same in ESS - Recording Working Time and Leave Request, I do not see that Time Constraints taking effect on the front end.
    Here is what I have done:
    I have two attendance - P001 and P002. P001 is configured to be recorded on Leave Request where as P002 is configured to be recorded via Record Working Time (CATS) link.
    I record the attendance P001 in Leave Request and also post that into infotypes. After this, I try to record P002 in the Record Working Time Screen and I still get errors (Errors are from: HRTIM00REC E/207 and LR E/335)
    If I try to replicate the same in the back-end in IT20002, then there is no issues.
    Can anyone help and let me know how we can implement the same Time constraints reactions on the front-end and the back-end.
    Thanks a bunch
    - Harshal

    Note that Time constraints are not valid for Leave request and Working time ie in ESS
    it only comes via PA30
    in CATS too, we dont follow much HR related collisions checks these are taken into consideration during CAT6
    and in leave request via Rptarqpost
    so its not gonna work, Its intended and correct! go for a user exit cats0003 or check cac1 profile customisation

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

Maybe you are looking for