Record working times with CATS

Hello experts,
I am a beginner and I really need your help regarding this point. we want to start recording working times in our PPM system. In our system we have the integration of our ERP system with CATS. We can easily registrate in ERP working time on each personnel number, on a specific cost center for cProjects, on activity type special defined for each role. We also transfer this costs with resources to controlling - so, in ERP system everything works fine.
But, when I go to PPM system - I'm lost. all that I maintained on ERP system is available on Accounting Tab in Detail Data -which is good. But, I am not able to see the confirmed work on task level, tab "Dates and work" (see screenshot attached). Do I miss some customizing? or how should I proceed in order that this field "confirmed work" to be filled with the data registrated on ERP?
Thanks a lot!
Best regards,
Ruxandra P.

Hello Cassoké,
have you enabled CATS-integration with cProjects in customizing?
1) Customizing CATS-Integration for your project type in PPM
Checkbox "Time/Travel Expenses Rec. CATS/SRM/FIN". Setting up "Accounting Integration".
2) Customizing CATS-Integration from CATS-profile-customizing
For your CATS Data Entry Profil you have to select the Checkbox "From Project Assignment" to get your worklist populated from cProjects (task is released, person assigned to task, etc...)
3) Only entries with status '30' from CATSDB will be transferred to DPR_CONF_LI by the report "DPR_CATS_CPR_TRANSF"
4) And of course, don't forget to uncheck "Test" :-) when running "DPR_CATS_CPR_TRANSF".
regards,
Peter

Similar Messages

Difference in Record Working Time in ESS

Hello,
We are implementing ESS on EP7.0 and when I go into the Record Working Time with one user I see the "Profit Segment" field and not for the other user....I feel it's in the Data entry profile of the users but when I compare the profiles I don't find any difference .....
Any help would be highly appreciated.

Anil,
Did you do IMG step Define Field Selection under Record Working Time? Select Data Entry Section then the Influencing button, and you'll be able to entry the profile name so that you can hide or unhide specific fields.
Hope that helps.
Brenda

ESS & MSS - CATS regular/Record Working Time (Web Dynpro)

Hello,
SAP Library help (http://help.sap.com/saphelp_nw70/helpdata/en/ef/e18d3f7057eb0ce10000000a114084/frameset.htm) says the following:
Compared with CATS classic, the following constraints exist for this Web application:
Since CATS regular is an Employee Self-Service application, time administrators or data entry personnel cannot recording working time data.
Is there any workaround to solve it? I mean, we need to recording working time data centrally through ESS or MSS. That's possible? Any enhacement for that? No matter where to do it (ESS or MSS).
Thanks!
Miguel Angel.

Hi Jigar,
That's almost exactly the requirement we need to implement!
Basically we need:
a. The employees with computer will record their own working times via ESS
b. For the employees without computer, their working times will be recorded via MSS by:
1. their org unit superior OR
2. someone like a time administrator defined in a custom list containing "employees for the time administrator".
I mean, someone called "time administrator" will record working time for a determined numbers of employees, but this "time administrator" is not the org unit superior. It's possible?? This is the mostly case.
Other requirements:
- Default time sheets and target hours for employees (for each employee the corresponding time sheet and target hours)
Thanks!!
Miguel Angel.

Error with ESS-Record working Time

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

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

ESS Record Working Time .. Restrict Time Entry with Relative limit

Hi SDN Users,
We are using ERP 2005 and EP 7.0 with webdynpro java ESS applications for Time, Travel and Personal Information.
In the ESS Record Working Time application, a user can scroll to any date he wants in the past or in the future and record/edit working times. The application does not take into consideration the setting made in the time entry profile for relative limit.
Please suggest the best way I can include this in the webdynpro application for Record Working Time. (in other words I would like to restrict the users to NOT be able to scroll before and later than 1 week from the current week).
Can this be achieved by modifying any ABAP program / BADI / User Exit (OR)
Would this require Webdynpro Code changes ?
Please suggest some changes if any one has gone through a similar requirement.
Thank You,
Salome

Hello Salome ,
You can use the following way out for this :
Lets say you want to allow one week before Begda , rest entries not allowed .
1. VcCatRecordentry View - make a method called dateValid(); this would return true / flase
we can get begda and endda.
wdcontext.currentcontextelement.gettimesheetBegda();
wdcontext.currentcontextelement.gettimesheetendda();
Date sysDate = new Date(Calendar.getInstance().getTimeInMillis());
int sysDay = sysDate.getDay();
2. Instantiate the Calendar Calendar c1 = new GregorianCalendar();
3. c1.add(c1.DATE,-7);
Date dt_end = c1.getTime();
now compare the dt_end to begda if it return >0
then in on action navigation nxt - report exception
this would work , since I did the same and it worked absolutely well for me .
Regards
Sandeep Sharma
Edited by: Sandeep Sharma on Jul 8, 2009 7:41 PM

Show Target hours in Recording Working Time(CATS) ESS version

Hi All,
I am trying to find out, if I can show the planned target hours on the web side of the Record Working Times component like it is shown in CAT2 as the first entry in the table. Is this possible ? Cna it be done by customizing somehow ?
Regards,
Paulo Poinha -- Accenture

Hi Paulo
I think the only way here would be to modify the standard Web Dynpro application directly in a JDI system. Check note 872892 for more info on this.
-Mikko

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.

ESS Timesheet - Record Working Time application partialy in german

I initially deployed the ESS BP and the Time Entry -> Record Working Time application was comming completely in english.
Then I changed the JCO references of ess/cat DC to some other backend, still the app was english.
When I changed the JCO reference back again this time the Record Working Time application was half in german langauge.Text on tab strip, all buttons are in german.
I even changed ProjectProperties.wdproperties property masterLanguage="en", earlier this was masterLanguage="de"
Still half the app is in german. I even deployed the standard ess/cat DC again still no luck.
How do I make it english back and what is the reason for random behavior?
Regards,
Vishal

Make sure you have no language set up with Jco connection
it should be blank!
Normally no language should be maintained for the above mentioned JCO's
If you have maintained any language for the JCO's ,kindly put it
blank.
http://help.sap.
com/saphelp_nw04/helpdata/en/49/e607426338da6fe10000000a1550b0/
frameset.htm
Please have a look at the Note 947081
this is how language are set
the hierarchy of what locale a component will be shown in the portal,
will be :
1)component- if he have a locale define
2) portal mandatory locale -( that's what we suggest)
3)user locale
4)browser locale
5)Portal default locale
6) system locale

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

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

my requirement is in RECORD WORKING TIME dc.
under weekly view when i press F4 it will display advanced search. in that advance search there will be CO Area: Short ID: WBS Element: Description: areas.
now abaper have created two more fields for search as per requirement.
now i have to include those those fields in to that advance search view (this comes when f4 is clicked under weekly view) along with the other fields.
my doubt is whether i have to write any coding to include those fileds or just reimport the model?
if to reimport the model it is asking for host name system nuber router and etc..
which model i have to reimport? who will provide me these details? basis people??
and which model i have to reimport?
after reimporting the model if i want test it what i have to do like right click on project and rebuild and deploy ???
else
if i have to write code where i have write the code for adding those fields??
in which iview and in where??
below is what i have done so far...
i have selected the ess~cat DC and created project.
i have opened the vc cat record entry iview, here i can find the same iview.
please help me its very urgent.
thanks in advance.

go to cac2
Let me explain with an example
You will need to:
1. go to CAC2, choose "Data entry section" from the first screen,
click "Modifiable" at the top of the screen.
2. find field "CATSDB-LTXA1" and check the radio buttons, if it is set
to "Hide", change it to "Disp.", and save.
3. now go back to CAT2 and go for "Administrator", the tick-off action
shall be available.
Please note:
On the first screen of CAC2, button "Modifiable" is affecting the whole
client, while "Influencing" is affecting a single profile.
So, that tick in "Administrator" will not be returned on by system only
when: you have set the field as "Input"/"Disp" in both "Modifiable" and
"Influencing".
But those fields which are "Disp." in "Modifiable" (whole client) but
"Hide" in "Influencing" for some profiles, will not be shown for those
profiles. (similiar with the problem with CATSFILEDS-DISPTEXT1)

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

ESS Record working time error "Profile not initialised" TS31000007

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

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

Record working times with CATS

Similar Messages

Maybe you are looking for