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

Similar Messages

  • 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

  • Java.lang.NullPointerException in the record working time iview

    Hello,
      I am getting java.lang.NullPointerException when I try to access the record working time iView. Below is the full exception chain.
    Please help me out in fixing the issue.
    java.lang.NullPointerException
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.getEmployeenumber(FcEmployeeServicesInterface.java:115)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.getEmployeenumber(InternalFcEmployeeServicesInterface.java:175)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.getEmployeenumber(InternalFcEmployeeServicesInterface.java:235)
         at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:791)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:248)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:344)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:234)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:484)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:192)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1351)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:550)
         at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
         at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:192)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

    Hi,
    All the parameters are maintained in the SU01 but we are in strange situation here only for one test user id we are getting null pointer exception with the time sheet. We compared with the user id which is working there is no difference in the parameters
    maintained. Please tell me why this behavior between two user ids.
        These two are manager user ids. For employee user ids time sheet is working fine.

  • Changing the default tab in Record Working Time iview of ESS

    Dear experts,
    How can we change the Default tab from WEEKLY to DAYLY in Record Working Time iview of ESS .

    We have been told by SAP this is not possible to do.
    There may be some changes to this in Ehp 5, but I am not sure.
    /Kirsten

  • Enabling "Daily View" on Record Working Time iView

    My company uses ESS Portal - Record working Time screen.
    We only see Weekly view tab... is there a way to enable the Daily view tab...
    how do I go about changing the iView for Daily View... any help is appreciated... I am new to portals so I need expert advise on this..
    Thanks a lot

    HI,
    You need to implement BADI for this ..
    BADI name : "PT_ABS_REQ"
    In the BADI "PT_ABS_REQ" interface "IF_EX_PT_ABS_REQ" you can find the method
    "SET_CALENDAR_COLOR" in that you can set the colure for the Absent type ......
    Adjust Colors of Calendar and Team Calendar
    Functionality
    You can use this method to change the colors in the team calendar.
    In the standard system, the different statuses for requests have different colors. You can use this method to differentiate the colors of requests depending on the following aspects:
    Status of requests (status)
    Action that an employee has executed: new request, delete, change (UIA operation)
    Subtype of absence (SUBTY)
    Full-day or partial-day absence (BEGMT, where BEGMT = 0 signifies a full-day absence)
    Application mode ( mode). You specify the application mode in the Select Employees for the Team Calendar IMG activity.
    Color Display of Status of Leave Requests(COLORS_ACTIVE). You specify this status in the Specify How Leave Is Displayed and Default Values IMG activity.
    Available Colors
    You have a choice of 16 colors. The 16 colors are hard coded, that is, you cannot change them or add other ones.
    The available colors are stored with their RGB value as constants of the CL_PT_REQ_CONST class. Use these constants if you want to change the colors.
    Notes
    If you change the colors in the team calendar, you should also adapt the legend accordingly. You can use the Adjust Legend for Calendar and Team Calendar method to do so.
    Hope this work!!!

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

  • Enhance legend in Record Working Time IView

    Hi,
    I am working on SAP NetWeaver Portal 7.0(Service Pack 4). New NetWeaver functionality in Record Working Time section(of ESS>Working time ) allows employees to enter their working times for different attendance/absence types showing different colours in calendar for Rejected and Not Released statuses. Now the requirement is to include one more colour to show the approved times in the calendar. Ie, Currently legend has two colors with text,  like  (  <Red box> Rejected           <Light Red box>  Not Released), now i have to add   ' <Green box>  Approve '  beside   'Not Released' text,    and if manager approves the time sheet then those dates will be displayed in green color.
    If any body worked on the similar type of requirement or having knowledge....please let me know how to achieve this req.
    Thanks in advance.

    HI,
    You need to implement BADI for this ..
    BADI name : "PT_ABS_REQ"
    In the BADI "PT_ABS_REQ" interface "IF_EX_PT_ABS_REQ" you can find the method
    "SET_CALENDAR_COLOR" in that you can set the colure for the Absent type ......
    Adjust Colors of Calendar and Team Calendar
    Functionality
    You can use this method to change the colors in the team calendar.
    In the standard system, the different statuses for requests have different colors. You can use this method to differentiate the colors of requests depending on the following aspects:
    Status of requests (status)
    Action that an employee has executed: new request, delete, change (UIA operation)
    Subtype of absence (SUBTY)
    Full-day or partial-day absence (BEGMT, where BEGMT = 0 signifies a full-day absence)
    Application mode ( mode). You specify the application mode in the Select Employees for the Team Calendar IMG activity.
    Color Display of Status of Leave Requests(COLORS_ACTIVE). You specify this status in the Specify How Leave Is Displayed and Default Values IMG activity.
    Available Colors
    You have a choice of 16 colors. The 16 colors are hard coded, that is, you cannot change them or add other ones.
    The available colors are stored with their RGB value as constants of the CL_PT_REQ_CONST class. Use these constants if you want to change the colors.
    Notes
    If you change the colors in the team calendar, you should also adapt the legend accordingly. You can use the Adjust Legend for Calendar and Team Calendar method to do so.
    Hope this work!!!

  • Null pointer exception with the Record working time iView

    I am facing a strange situation over here, I am testing with three user ids and with only one manager user id I am getting below java runtime error. Please help me out in finding a solution for this. When I log in with the other two test ids I am able to open the iView and submit my time sheet with out any exceptions but only with one user id I am getting this kind of error.
    Detailed Error Information Detailed Exception Chain java.lang.NullPointerException at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.getEmployeenumber(FcEmployeeServicesInterface.java:115) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.getEmployeenumber(InternalFcEmployeeServicesInterface.java:175) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.getEmployeenumber(InternalFcEmployeeServicesInterface.java:235) at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:791) at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:248) at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:344) at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:234) at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:484) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251) at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194) at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162) at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146) at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438) at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196) at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108) at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215) at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303) at com.sap.tc.webdynpro.clientserver.session.ClientSession.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)

    Hi,
    This runtime error occurs when the application fails to resolve the pernr of the logged in user in the backend. Could you please check if the user has correct assignment in IT0105. If you are using CE, kindly check if the CE settings are properly checked. Also check if the IT0105 is correctly shared across all the CE assignments.
    Hope this helps
    Regards,
    Roy

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

  • Record working Time link in General Related Activities iView

    Hello Gurus,
        In the MSS Related Activities iView we have a link to navigate to Record Working TIme iView, but when I click on that link it is pointing to the production portal but I am testing in the development environment.
       So please any one help he me out whether do we have to maintain any URL.
       When I click Timesheet I can see the list of employees in employee search area and information in general section but when I click on the record working time link in the related activities area portal redirects me to the production portal URL and displays the production portal login screen. Please help me out in resolving the issue.

    Hmm this is interesting. Guess that's reason even when i am trying to call pdc location of iview  "Record Working Time" it is unable to load fpm application based changes and some of personalizations.
    Wondering if there is any way to generate or find absolute path to run these application, as they are running on Portal(it works just fine when i launch from my ESS role).
    http watch was not great help..
    Cheers,
    Sudhir

  • To unhide the columns of " Record Working Time " table

    hi experts ,
    Can any one suggest me how to unhide some columns of the table "Record Working Time" .
    Actually I have tried the following procedure : content admin -> portal content -> iview -> Rclickctrlalt and check the property of the table and displayed all the columns . It shows all the columns perfectly .
    Finally , when I checked the table in Employee self service -> Working time -> Record working time , I can not see some columns which are visible in content admin "Record Working Time " iview .
    It is a standard webdynpro java application "CatDataRecord" .

    hi gorlisrinu  ,
    Thanks for your reply .
    I have all the administration right . When  I  check the iview in 'Content Admin' I can see all the columns , but when I check the same iview under  'ESS role' i can not see some of the columns  of "Record Working Table ". That is my problem . Can you tell me what is the reason behind it  ? I always save  all the changes after any modification .
    Regards ,
    Sumana
    Edited by: sumana05 on Nov 18, 2011 7:39 AM

  • Record Working Time - Approve Status

    Hi,
    How can an Employee checks whether his Time has been approved or not? I am in "Record Working Time" iView in Portal, i wasn't able to see any status on previous timesheets/weeks whether the time has been approved by the manager or not.
    Please advice.
    Thanks
    Vijay

    We can see on Daily View by clicking on DETAILS link on each line.

  • ESS - working time - record working time - blank site

    Hi,
    if i follow the link <u>record working time</u> in the working time overview i get a blank site.
    Has somebody an idea why?

    Hi Prabhakar,
    I looked into the Portal Content directory. Where do i find the Record Working Time iView?
    I only see the iViews from the package:
    - benefits and payment (x2)
    - career and job (x2)
    - career & job
    - employee search (x2)
    - overview
    - personal information (x2)
    - purchasing (x2)
    - travel and expenses (x2)
    - work environment (x2)
    - working time (x2)
    x2 = one ist "area" and one is "serv"
    regards
    Sleepy_head

  • Record working time in ESS window collapsed

    Dear all,
    after we implemented EHP6 in our environment we have a strange issue with the Record working time window in ESS portal.
    When a user log in to the portal and go the Record working time the record working time window initial state is collapsed. He need to expand the window manually (see the screenshot).
    Does anyone of you have / had same issue? Are you aware of any SAP notes we can consider to solve the issue?
    Everything is standard , nothing customized.
    Thank you
    Vladimir
    BR

    This is because end users do personalization in that page. In this case when they logon next time always it will display the based on his personalization in previous logon.
    You can clear all personalization's for users in System Administration tab
    Clear all personalization for users from System Administration in portal.
    System Administration -> Support
    -> PCD Tools
         -> Personalization Data Cleanup
    Here Remove personalization data of all users for all portal objects or specific to user / specific to portal object

Maybe you are looking for

  • Dock missing images

    I have just bought a brand new iMac (2.8GHz Duo, 2GB Ram) and I'm getting weird images missing on the Dock now and then. I don't fully understand. I've never seen this before with my MacBook pro or anything. When i hit the downloads folder, i saw the

  • Track as intruder ??

    What does this function actually do ???

  • What system would you recommend for CS5 Master Collection?

    Hi All, Hoping to get input on a recommended system configuration for having a computer that has enough under the hood to handle CS 5 in full. I have been searching around and it seems like Adobe has links to three different suppliers: Dell HP Lenovo

  • Runtime error when creating Sessions - help

    Hi , I tried creating a session under Collaboration ->MySessions I get the following runtime error at the end: <b> An exception occurred while processing a request for : iView : pcd:portal_content/specialist/Collaboration/com.sap.netweaver.coll.Colla

  • Why would I have duplicate Sent mail messages

    I use Mail to retrieve my Outlook.com mail and every message I send shows up twice in the Sent mailbox for this account.  It hasn't always done this, so I'm not sure what got changed?