Issue in Record Working Time WDA(HRESS_C_CATS) during the profile change

Hi Experts,
We are facing the issue in WDA--> HRESS_C_CATS
Steps to replicate the issue:
1. ESS --> Record Working Time
2. Click "Select Profile" --> Select any profile other than the CVR Paramaeter Profile.
3. Select on any date from the calendar(other than today), Click Apply --> work date shows in the date textbox.
4. Click "Previous Period" --> The work date shows today's date.
Require your guidance to resolve the above issue.
Best Regards,
Laxman Chittepu

Similar Messages

Issues in Recording working time

Hi experts!
I have a problem in Recording working time. It display "The attendance/absence type 99/0800 does not exist on 01.01.2009".
Help me!
Regards Huy!

Hi,
When you are applying att./absence in the master data, system is telling there is 0800 att/absence type with 99 psg .grouping.
Which one you are applying whether absence or attendance.
either it is absence , create one absence type 0800 with 99 psg. grouping
either it is attendance, create one attendance type 0800 with 99 psg. grouping .
After creation of 0800, assign the screen no, TC, couning rules.
Then your problem will resolve.
Regards
Devi

Record Working time issue

We are facing issue in Record working time where there are users who belong to Org unit "70001573u201D. The chief position of org unit 70001573 is not occupied.
70001573 Org units are belonging to Org unit 70001601 which is occupied by EMMA POWELL.
So now the user whose belongs to 70001573 org unit, when they raise the record working time and release the same, Since 70001573 is not occupied by any person the request should go to Org Unit 70001601.
Currently the system not functioning as per the said requirement.
The user whose belong to 70001573 org unit, when they raise the record working time and release the same , the request not going any manager for the approval which shout not be case .
We even though implement Note 595073 - Workflow behavior with vacant chief positions
But we still are facing the issue.

which TASK are you using for CATS? Also have you implemented the badi_cats_approval to check for this scenario ie vacant position etc or exit cats00008
also
The actual user to who's inbox the workitem should be routed to is only
determined in subsequent processing. Further, it is not mandatory that a
user is actually assigned. Please note that workitems in general may be
assigned to users, positions, work center etc. It is therefore by
intention that an error is not raised in the scenario under
consideration.
best option is BADI_CATS_APPROVAL

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, Ill update this message with the results.

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"

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

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: can't copy row from worklist for previous week

When copying a row from worklist to recorded work time for previous week the following error happen.
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Access with ZERO object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
    at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:102)
    at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:470)
    at com.sap.xss.hr.cat.record.blc.RfcManager.rfcCopyWorklist(RfcManager.java:378)
    at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.rfcCopyWorklist(InternalRfcManager.java:191)
    at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onCopyWorklist(FcCatRecordInterface.java:616)

If I recall correctly, the Windows clipboard system allows the developer to place different types of data in the clipboard, and convert between them. It is often possible, for example, to paste formatted text as plain text and so on. Large amounts of data are sometimes stored as "links" back to the producing program, so that it can transfer data directly.
Now this is just a guess, but when you select all with Ctrl+A, there's a chance that Skype in fact puts all the information about the whole message into the clipboard, including its metadata such as time, sender, etc. Dragging would just select the text.
If the receiving program cannot interpret the metadata, and the plain-text version is not also stored in the clipboard, then pasting would fail.
Again, as I say, this is just a guess. We would have to get confirmation from the Skype developers as to whether this is true.
Have you tried pasting into different programs? (Word, plain text editor, Powerpoint...) If one of them can accept the clipboard contents then we may get a further clue.
EDIT: I found this program which inspects clipboard contents directly - http://www.peterbuettner.de/develop/tools/clipview/ which may also be of use.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

No Default of Personnel Number and Name in Record Working Time

Hi,
In Record Working Time, I have done the necessary settings in CAC1 and CAC2. Every filed that I have selected is appearing except PERNR and Employee Name. Not only that, the fileds themselves are not appearing let alone a value for those. Is there something I am missing?

These fields dont appear in Record working time in ESS till EHP4, From EHP5 these can be seen
but these fields wont be shown
SO this is standard

Set Weekly View as default in Record Working time

Hi,
Please let me know in ESS (Time Management) how can I set Weekly View as default instead of Daily view under Record Working time in EHP5?
1> If Personalization could only be applied on JAVA Web Dynpro iVews, what can be done in case of WD4A?
2> Can the view changes be done in Content Administration or the changes could only be done in "Component configuration/enhancement" to achieve the requirement? If it could only be done using "Component configuration/enhancement" can you please help me with the same.
Thanks for your help!

Hi,
In R3, goto PM - PA - ESS - Service specific settings - Woring time - Record working time - Set up data entry profile - Select the data entry profile which is assigned to the employees in their CVR Parameters(ex.ess sf) - Maintain the PERIOD SETTING as 2 (which is the weekly view).
Regards
Priya

Customized Advanced Search ESS Record Working Time

Hello All,
Does anyone of you know if there is a possibility to adjust the u201CAdvanced Searchu201D (Search Help) for the ESS Record Working Time application? Currently the standard search only displays 5 results when searching for WBS Elements. We want to adjust this to 15 or more.
Does anyone of you have some experience with this?
Looking forward to your reply.
Kind regards,
Joost Christenhusz

if it is a webdynpro for java application we can do that, but i am not getting that where is screen location in the ess screen,
please can you explaint the navigation inn the portal, so we can find out the dc name, in which we need to de the changes,
Cheers,
Apparao

Recording Working Time issue

Hello Guru's,
We are working on Time Management and for this we are using Working Time iView in Employee Self-Service role.
We are using Record Working Time and in this we record the working times and in the WBS Element cell there is option like F4 which opens up a popup and we can search for Projects (or WBS element) I want to make changes to that screen.
Please guide me where to do the changes for that?
I looked into the code but couldn't find.
Thanks in Advance for your time.
Regards,
Pramod

Hi Pramod,
In order to modify the standard webdynpro record working time application , you have to do below steps.
Import source code ( XSS Components ) in NWDI
Create a track.
From Developer studio , connect to DTR and check out the source code .
Create the sap.com/ess~cat (DC') project in NWDS.
Modify the standard SAP code as per your needs .
Refer JDI Cookbook for ESS.doc for above tasks.
Thanks
Aravinda

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

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

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

Issue in Record Working Time WDA(HRESS_C_CATS) during the profile change

Similar Messages

Maybe you are looking for