Working Time in Portal

Hi Experts,
In Record Working Time and Release Working Time application there is a "Cancel" and "Exit" button respectively.When I click these buttons in portal it shows "Collaboration Detailed Navigation" stating "Page not found or not available".
The applications are working fine.But problem is when I click these buttons.Please suggest.
Thanks,
Rajani

Hi,
hope you checked all.
check whether everyone role with end user permission assigned to the Portal Content.
Since Super Admin have owner permission to all the folders so they can see the content, but that is not the case with other users who don't have Super Admin role.
Check the process by Super Admin user

Similar Messages

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

Unable to save data in record working time

Hi All,
I am working on ESS portal , when I try to record & save working time in portal , it throw an error message as 'Unable to save data'.
Can you plz assist me on this.
Usefull answers will be awarded.
Thanks,
Nilima

Hi ALL,
I'm too facing the same problem....usefull answers will be awarded.

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

Can we approve working time in UWL without MSS web appl?

Hello Friends,
I have a doubt thats bugging me for the past one week, I have a requirement where an employee enters working time through portal and the manager should approve through the portal.
I have configured ESS and also the backend, thus when an employee enters his working time and releases , a workitem is created in the managers inbox at the backend.
I am using the approval reports RCATSB01 for approving working time in the backend.
I am planning to do the UWL config so that managers can access workitems through portal, <b>Can i use this approval report to approve working time in UWL or is it mandatory to use "Approve working Time" web application from MSS</b>.
Regards
Sriram

Hello Ashutosh,
I have given the visualization parameters for task TS31000007
APPLICATION : CatManagerApprove
PACKAGE : sap.com/msscatapproval in SWFVISU
Then followed the UWL config guide and did minimal configration
Created a sytem in system landscape (alias UWL_SYSTEM) and registered in UWL
registered all item types for the system.
Now i can able to see the workitems in the UWL but when i click on the work item Approve working time i get an error
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapWebDynproLaunch
Component Name : com.sap.portal.appintegrator.sap.WebDynpro
Exception in SAP Application Integrator occured: Application URL ':///webdynpro/dispatcher/sap.com/msscatapproval/CatManagerApprove;jsessionid=(J2EE17580000)ID0079084450DB21042082377319897423End' is not valid! Please check the protocol and host entries for system 'UWL_SYSTEM'..
Exception id: 03:13_24/07/07_0037_17580050
See the details for the exception ID in the log file
There is already system file com.sap.pct.erp.mss.001 . do i need to do any changes to the config files.
Regards
Sriram

Approve/Reject Working Time through the Enterprise Portal Workflow

Hey Everyone,
We are currently working on a project to rollout a number new portal services. I was wondering if anyone in ECC or Portal has experience with enhancing the Time Entry Approval process. Is it possible to trigger an email notification when a manager rejects an employees time for any of the configured reasons. I would like an email back to the email to let them know they should change their hours or that their overtime was rejected. I have been spoiled by the deeper config options available for Leave Request.
In the standard workflow task the Item does turn red when rejected, but if employees aren't reviewing their entries they may never know it was rejected before they check their pay stubs.
I would be pretty surprised if the BADI or workflow task would be unable to know there was a rejection because it clearly asks you for a rejection reason and changes the colour of the request in the Record Working Time screen.
Thank you in advance,
Doug

Sid,
I believe we are or have looked into RSWUWFML2, but I will confirm.
After trying a number of different options we are currently looking at using the Rejection check-box and determine if BASIS can redirect the messages to the employee's IT0105 subtype 0010 email address.
Here are some of the notes we have looked at.
http://forums.sdn.sap.com/thread.jspa?threadID=1725144 (Email Forwarding)
http://forums.sdn.sap.com/thread.jspa?threadID=1397351 (SO16 Forwarding)
http://forums.sdn.sap.com/thread.jspa?threadID=2084622 (SO16 Forwarding)
http://forums.sdn.sap.com/thread.jspa?threadID=1947223 (SO16 Forwarding)
http://forums.sdn.sap.com/thread.jspa?threadID=1686788 (SO16 Forwarding)
http://forums.sdn.sap.com/thread.jspa?threadID=2093332 (Rejection to External Email - opened by our team)
http://help.sap.com/saphelp_nw70/helpdata/en/6c/69c30f418d11d1896e0000e8322d00/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/2b/d926324b8a11d1894c0000e8323c4f/frameset.htm
Our Version: EP 7 EHP 3
I wish Record Working Time had similar config to Leave Request. If you have additional input please let me know.
Doug
Edited by: Doug Robbins on Dec 7, 2011 5:30 PM

Switch to activate change working time in HCM processes and forms in portal

Hi,
I am tring to change the working time of an employee from 100 percent to 80 in ESS,using adobe forms,but the value is not getting changed.Please let me know whether we have to enable switch to make abobe form active in portal.
Regards,
Ramesh

Thanks Arpit,
WF-BATCH already has SAP_ALL. Do we need to assign some additional roles or profiles to this user?
Log says error reading Process Object
Thanks,
Jitesh

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

ESS portal: Hide additional info field in release working time screen

Hi,
I need to know how can i hide 'additional info' field in the release working time screen?
I know i would use personalization but don't know the way to do that.

it will be shown in header only in release application, let me explain
In the time recording application, when you enter a record and click
on review, the additional info columns shows the text. This works
because the data is entered by the user and the entered record is
mapped to additional info column.
In time release application, all the records from database are retrieved
and displayed. The user does not enter any data. Hence in this case it
is not possible to map the records to text in the additional info
column. The Error/Warning messages are displayed in the top of the list
with detailed information. We feel the information displayed is
sufficient for the user to take necessary action. Usually in the release
application, there would be lots of records. Displaying text in both
additional info column and also at the top of the list is not a feasible
solution.
Technically it would be difficult for us to change this behavior in the
standard application.
we have new application in EHP5.
Edited by: Siddharth Rajora on Mar 9, 2012 7:10 PM

Custom Search help in Record Working Time

Hi,
We have a requirement to add a custom field on RECORD Working Time ( ESS). This field has been added and custom search help is assigned to the data element of the field. The values in the F4 help should vary based on employees department.
The related code for this requirement is written in the serach help exit. The F4 help is working as expected from backend ( ECC) but not in Portal (ESS).
I have added the custom field in TCATS_SHLP_ITS. After maintaining this table all the values in F4 help are displaying , whereas it should only display the values under employees department in Record Working time.
I understand the class cl_xss_cat_value_help_general is responsible for the search help in ESS is there any user exit or enhancement available for this class in order to control the serach values on ESS.
Thanks in advance.
regards,
Pradeep

note that search help of CAT2 and record working time are different!
these are teh steps
please modify the following in the table TCATS_SHLP_ITS as follows:
1. Execute the T-Code SM31
2. Enter the table name TCATS_SHLP_ITS.
or check the class
CL_XSS_CAT_VALUE_HELP_GENERAL
or check
CL_XSS_CAT_VALUE_HELP*
take an example from Sap note 914125

Record Working Time task merging multiple employees into a single task

Hi Everyone,
I'm going to check our configuration again to see if this is standard behaviour, config, or a problem with EHP 3's version of record working time.
So if employee A submits to manager A 1 task is created. Then when employee B submits to manager A we were expecting 2 tasks. However, we've been noticing manager A is getting 1 task with several line times.
We are ok with it merging tasks for employee A over multiple weeks. That is ideal actually.
The problem is that employee B's task should be separate.
Is there a quick fix?
Thanks,
Doug Robbins

I did try 31000007 and noticed the same behavior. Are you saying I should use an older version of the task to get back to grouped by employee number and not merging everything?
Well this causing us issues for a few reasons. The main one we developed a work around because we had to make sure emails were not being sent to 1 person for all the employees with their data. That would cause obvious security concerns.
But when forward tasks out managers want to be able to forward a specific employee's requests and not all of them. If some customers want this it should be a configurable option. To allow companies that want 1 single task or companies that want 1 task/employee/week.
This is inconsistent with the other portal applications. It would be nice if Germany picked 1 way of doing things or provided more configuration options. I'm hoping that OSS gives us something because merging everything into a single task for all employees is not the behaviour we want or expected.
I always appreciate your input because you have been very helpful as I learn about portal.
Thanks,
Doug R
Thanks you

ESS Working Time - Start Time and End Time in Weekly View

Hello,
I'm having a problem with the business package ESS - functionality Working Time (cat2).
I need that information to Start Time and End Time appear in the Weekly View of the portal.
In Daily View that information are already visible, but In Weekly View that information does not appear.
Does anyone have any suggestions?
Thank you very much your attention.
Att,
Jair de Oliveira Junior

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

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

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.

Approve Working Time WDA

Hi.
We have just implemented Web Dynpro ABAP based Approve Working Time application (Collective Approval iView) replacing the Java based version.
A manager complains that now he has to go into each and every of his employees recordings to check their daily recording while he in the old Java based version could see everything in one view when he clicked the 'Review' button. Off course this is a setback in usability.
To my question:
Is there any way we can offer the same functionality in the ABAP version so that a manager with a single click can see all daily recordings by his employees?
We are running ECC 6 EhP6 and NW 7.31 SP11.
I appreciate all responses. Thanks in advance.
Thanks and regards
Søren Bessermann

Hi Samuli.
Thank you for quick reply!
I am in doubt though, is MSS add-on an ECC component or a portal component?
Regards
Søren

Working Time in Portal

Similar Messages

Maybe you are looking for