Auto-populating STAT holiday into Timesheet

[Anon Anon]

Is there a way to auto-populate a "Other Time"  category (such as statutory holidays)  into all timesheets?

[Anon Anon]

Statutory holidays I would just mark as "non-working days" in the relevant base calendar.... so the resource is just not expected to book time on that day?  --  You can "almost" do it the other way though, set up a project plan, allocate EVERYONE to it, create a TASK of a single days duration, assign EVERYONE to it, make sure timesheet auto-populate is on and at least then when they open their timesheet for tha week, the task will be there.Don't know how to auto-populate the hours/type code on the time-entry though.  (So I like the non-working day method much better!)  Dave.

[Anon Anon]

Hi,  Admin level for all users-->  Not possible unlesswhen there is no assignments in any projects for any resources.(Don't ask me then whey there is projects,tasks.That' what we can do in this version)  It can be done for the next timesheets alone:  In case if you set in Admin-->timesheet settings-->Populate time range as 7 days before time period startand the same as 7 days after the time period finish then it will displaywhatever you have selected in the first week,if it is fully In-direct Time (Vacation,Sickness) then it will be the same for next week.when u click the populate it will be the same.   Once the Timesheet becomes an Object we can try that.   Kb Article about  Question:
What is the algorithm for Clarity timesheet population?Answer:
The timesheet 'Populate' button populates the timesheet with assignments that the resource is currently working on for a certain range of dates around the time period.

The range is determined by the system admin in Administration Tools > Project Management > Timesheet Options > Default Time Entry Options field 'Populate time Range'.

The default values are 7 days before and 7 days after.

The following rules explain the logic used to determine if an assignment (a task as it is seen by the user) will be populated onto a timesheet.

An assignment is populated onto a timesheet if:

(It's start and end date range falls within the open time periods) OR
(it has a proposed estimate that has been specified AND its finish date is before the oldest open time period)

AND

It is not a milestone

AND

It's assignment status is not complete.

More Information:
Proposed Estimate: The proposed estimate (or sometimes referred to as the pending estimate, as it would be seen in Open Workbench) is specified by entering a value into the ETC field on a timesheet. Once a value is entered, the value will be bold and highlighted. This value overrides the project plan ?s estimate to complete. On subsequent timesheets where actuals are entered this value is decremented until it reaches zero.  Cheers,Sundar

Attachment(s)

If the previous timesheet is Indirect time entries.zip   295 KB 1 version

[Anon Anon]

Hi,  May be(sure) i have mis-understood the topic.If there is an assignment then that is Direct time (project) entries,if there is no assignment then time entries are considered as "In direct Time".  I thought clesine was asking for "In Direct" time in Auto poplulate Logic.  For holidays even though you mark the calendar as Non working day,the resource can enter his time entries on that day,as there is no validation can be done.   The reason iam saying this is our users mistakenly enter the effort on a Public Holiday and when we generate the reports that they have entered more than their availability they used to fight with usand will ask us one thing why can't the timesheets calcaulating the effort entered in an Non work day,it should not consider that . why not the system is handling that(Really Good Question)
And then  we need to explain the story of Blob's & slices that the resource calendar will be considering that day as Holiday(Availabilitywill be zero) but the timesheet is weekly based,it will take the consolidated one and store in the timeentry Tables.Then an brave job called slice  will jump and crack the Blob in to slices and finally actuals can be arrived on a Day basis.  Cheers,Sundar

[Deactivated User]

If you want to autopopulate statutory holidays (out of the blue) you would have to make them tasks in a project and assign everybody to those.That way they would autopopulate on the timesheets, however it would almost work ad Dave points out- as Sundar explains those tasks would come 7 days before and remain 7 days (if there is ETC remaining) after that date- what the autopopulate does is, puts it on the task list and bring the ETC, but not the timeentery on that particular day.Hours can be populated only from the previous timesheet with the proper autopopulate option.   That is not feasible because staturoty holidays are one time events and not recurring weekly.  If you chose to use Holiday charge code that should be specified to the task and the it would be the default for any timeenty on that task.If you chose to Holiday input type code that should be the defaul for the resource so that it would be the default for any timeentry for that resource. Not feasible.Othervise the resource entering the time   can change those from the drop downs if the fields are on the timesheet.  If the holidays are on the calendar then they would be recognized as no-avalalability when calculating the capacity and in schedulingBut there is nothing to stop resources entering time on those days.  You could try to modify the timeentry approval process   to return the timesheet if time is entered on a holiday. I don't know how feasible that is.  The sure fire way to prevent any resource to enter time on a statutory holiday is to exclude those from the timeentry periods /time reporting periods.Say you have weekly timeperiods then you would split each week with a statutory holiday and leave a gap for the holiday.(Some people do that even for the weekends)  Martti K.  

[Anon Anon]

Hi,    In our organisation we have users across countries so their country public holiday will fall on different days so making an sepearte timesheet for "Public holidays" willwon't work for us as now timeperiods are Global.  It would be vrey nice if we create timeperiods for an location / country basics.Iam sure i will  raise an ERQ for this.Timeperiods should not  be an global one particulary for companies having offices across globe.Weekly timesheet cut off is on Friday for all users but Middle East countriesare not working on Friday  so difficult to maintain cut off time.  Cheers,Sundar

[Anon Anon]

^   you don't need timeperiods set up for different "locale"s - you can do that with different base calendars.  I work in a multi-country Clarity instance, I have a UK calendar with UK public holidays, my colleagues in other countries have their statutory holidays in their calendars.  In the timesheet we are not prevented from entering time on the non-working days (nor should we be, some of us might work overtime) - but the non-working days is a different colour on screen (as with the weekend days).  And we have a global consistant weekly timeperiod (like you would expect).  Dave.  

[Anon Anon]

Dave,  Thanks for ur reply.  That's what we are doing in our company,we have seperate calendar for each country and the public holidays are marked as Non working day and those respective country calendars are tagged to thecountry resources there so the availability of the resources will be based on that country calendar.  Our issue we want to close the weekly timeperiods as on friday (Cut off time) except MESA countries as they will not be working but as that is not possible as it is an  common one.For MESA we want to close on Sunday.And also for some audit purpose if we want to view one particular unit timesheets we can't open as it will open for all.Technology  is also thinking that if every one is using timesheets & running the reports on a last day the CPU utilization is high so can we keep the cut off day for some region on Monday,but timebeing i saidit is not possible as Timeperiods are common.  Cheers,Sundar

[Deactivated User]

You make it sound that it is important to have the non working days at the beginning of the timeperiod and having them somewhere else eg in the middle is not feasible.Is there a reason for that and is there a real benefit from that?  If you just want to view timesheets with timeentry approve right you can also view the timesheets for the closed periods.  Martti K.

[Anon Anon]

Marrti,    We have an PMO Team who have the "Time sheet Global" approval rights,they can view the closed timesheets and they help in audit.    The core issue for us is (As i stated earlier) we can't close / open timeperiods based on a particular Location.  The main benefit for making Timeperiods linking to an particular OBS or Location or Cost centreis that we can close / open timeperiods based on the Location  and we can have   the Timesheet cut off   based on the calendar which is different for each locations.  Cheers,Sundar