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

Similar Messages

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

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

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

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

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.

Number of rows in Record Working Time.

Hello Guru's,
IN ESS- Record Working Time - the number of rows visible are set to 8 in the Web Dynpro Java Code.
I had a look at the Note:
Note 957741 - Few lines in the data entry grid of the timesheet webdynpro
The question I had is to have more than 8 rows visible, is it Java Code modification or any other alternative to change the number of Visible Row....
Please reply back asap.
Thanks in advance for your time.
Best Regards,
Pramod

Hi Siddharth,
Thanks for the reply.
Looks like if need to change the no of rows need to do the WDJ code modifications.
Interesting to know the other details in the message.
But in the reply the interface you mentioned what for that is used,
Since when checked the where used list of the attribute it calls ADD_INITIAL_LINES_TO_TIMESHEET even in the debug it is not allowing to do the changes to value which is 6 by default.
Since the value is constant it cannot be changed.
what was your intention when you gave that reply, curious to know how would it solve the issue.
And one other questions In the Java Code
ListViewerSlim listViewer =
                    new ListViewerSlim(
                         view,
                         wdThis.getRFC_FieldList_Timesheet(),
                         "TimesheetData",
               //               listViewer.destroyAllColumnHeaders();   //XZQ110505
               theTable = listViewer.getTableControl();
               theTable.setVisibleRowCount(8); //Note SOW_957741
               //               theTable.setHeader(null);      //XZQ110505
it is set to 8 why is it different in both the cases.
Since, when we login to the Portal it shows no of rows visible as 8 not 6 as it is in the interface?
any thoughts on this.
Kind Regards,
Pramod

ESS - add a new column to Record Working Time table

Hello all,
My client would like to add a column to the Record Working Time table in ESS. They would like to add a column for Activity Name next to Activity Number. Can anyone tell me where this can be congured? Or would this be something I would need to hard-code in the ess~cat source code?
Thanks,
-Kevin

I have figured out the 2 step process needed for this, involving Modifiable and Influencing. So I am able to add new fields. The only issue I am running into now appears to be dependant on the field name.
I can add CATSD-VORNR
But I cant add CATSDB-LTXA1
I have tried a few variations and it seems i can add fields from CATSD but not from CATSDB?
Has anyone else seen this or know what steps must be taken to display CATSDB-LTXA1?
Thanks,
-Kevin

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

How to implement Manager Selfservice - Recording Working Time - BP

Hi!
I would like to have a stepby step approach to implement business package for recording working time.
What I need is the following information?
1. Pre-requisites
2. How to create the iview ?
3. What R3 configurations need?
you can email if you have good documentation on this to [email protected]
Thank you
Ramesh

The primary limitation you will encounter when trying to do high speed
digital I/O using your E-Series hardware is that the digital lines are
all software timed. This means that for each and every digital
read it is necessary for your software to issue a command to your
hardware, read a single point, then receive the response from the
board. This prevents you from performing digital operations at
very high speed. In general, I would say that 100 microseconds is
a very good response using software-timed digital I/O on a Windows
computer.
It is difficult to make a good recommendation without more detail about
what you are trying to do. You may need to consider switching to
a Real-Time operating system, or upgrading your DAQ hardware to a board
that will allow you to time your digital acquisitions on the board
itself. These devices, such as the m-Series DAQ or the PCI-653x
series, would allow you to use hardware triggers for your digital
acquisitions, change detection, and buffered data acquisitions to
reduce the software overhead involved in a rapid acquisition.

ESS Timesheet - Record Working Time application partially 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

Any Clue?
JCO's have "en"
browser has "en" still the issue remains.
--Vishal

Record Working Time

Hi Experts,
In standard ess/mss under working time message is coming Your recorded times have been approved up to &DATE&.", instead of date it is showing &DATE&, what i have to do for the same?
-Rajneesh Gupta

Hi Rajneesh,
We are facing the same problem, in ESS-Working Time Page under Record Working Time the text is displaying as Your recorded times have been approved up to &DATE&.
The place holder &DATE& is not getting populated with the required date.
Is this issue which you were facing earlier is resolved , if so, please give your inputs to resolve this.
Thanks in advance..
regards,
Thirun.

Record working Time link in General Related Activities iView

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

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

Record Working Time(WDJ) error

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

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

Record working time 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 issue

Similar Messages

Maybe you are looking for