Just curious to find out how often folks are running their Clarity Time Slice jobs?
We are having some issues with time data not showing up in our portlets and suspect it has to do with how often we are running our time slice.
2) Much less often - once overnight perhaps?
I subscribe to #1 - so mine is scheduled to run every minute, 7am to Midnight and then a couple of extra runs just after midnight to handle weekly/monthly rollover.
We're in the 'all the time' school. We run every 5 minutes. Here's the crontab.
Once a minute on the outset that the job completes under one minute, if not then once in two or once in five minutes.
Thanks for the information everyone (I work with April).
We have been able to figure out that the issue is with our time slice job running at 12AM. We have overseas contractors who submit timesheets around this time and their data is not getting into the time slice. We don't have any Clarity jobs scheduled any where near 12AM. Would there be Clarity system jobs that could be impacting the time slicing job at this time? We are thinking of rescheduling the time slicing job to run every 5 minutes between 1AM and 11PM, do you think this would take care of the issue?
When you say "their data is not getting into the time slice", what is it that you're looking for? I'm going to assume you're interested in their Actuals and getting the data into the schedules and the Clarity UI. If Actuals, the first thing you'll want to review is your business process for getting the time approved then your Clarity Post Timesheets job. The Post Timesheets job turns the time into Actuals that are then ready to be 'picked up' by the time slicing job and applied as appropriate. Just like Dave mentioned on time slicing, there are a couple schools of thought on this based upon your need. Some organizations post time often to ensure they keep getting actuals in. Some organizations post once per period in order to leverage the value of Pending Actuals. You'll need to decide what posting process is right for you.
Updates the task assignments and the Transaction Import table with the actuals on the timesheets.
Advances Estimate To Complete (ETC) past the time period for the posted timesheets on all task assignments of the corresponding resources.
This job processes all configured time slices and updates discrete transactional data for task assignment actuals, Estimate To Complete (ETC) and baselines, time sheet actuals, team and assignment data from a scenario, resource allocations to projects and resource availability.
This job updates the ETCSUM and EACSUM fields for investments based on the resources allocated to the investment. It calculates the sum of the ETC values for all the investment's assignments and stores the value in the ETCSUM field, and calculates the sum of the EAC values for all the investment's assignments and stores the value in the EACSUM field.
This job flattens the percentage allocations between the investments in the hierarchy. Run this job when there have been multiple changes in the investment hierarchy.
Of course, there are other jobs but these are the big ones for keeping the data 'fresh' in the Clarity UI. Is this the information you're looking for?
FYI all, while we're on this topic, I found this out in the Knowledge Base the other day - please review your incompatible jobs configurations: TEC528729 - Configuring and Scheduling Some of the Main Clarity Jobs.
Would there be anything in the definition above that could be a problem? From digging into the time entry tables we really think that there may be an issue with this slice running at midnight. Maybe because it is setup for daily and it rolls over daily at midnight??
Sorry if my questions are basic, I just haven't really grasped the concept of time slices fully yet.
If I understand correctly, you have a portlet where you're expecting to see the data but are not and you think it might have something to do with when you have your slicing scheduled.
1) confirm that timesheet is in and posted.
2) confirm that the data you're expecting to see from this timesheet is not in your portlet.
3) Manually run your Time Slicing job.
If the data is there, then yes, you're fix is probably to up the frequency of when your slicing is running. If not, we'll need to dig deeper.
Give this a go and let us know your results. Any other ideas anyone?
So (@april/christie) you could implement something similar, i.e. something that checked the data integrity ahead of you 'interface' running, flagged any reslicing that was required and then reran the timeslice to mend the data.
I would still recommend running the time slice "all the time" since this is going to greatly reduce the "chances" of hitting the problem - since it gives far more scope for a non-rollover timelsice run to process the updated data in its own run of timeslicng. (of course all that is really supposing there is some sort of rollover/slicing contention going on).
As far as I understand it there are no "system jobs", but all jobs can be seen in the scheduled jobs.
If you are using the info for tracking billing then your portlet is likely to take the posted timeentries and posting of the timesheets is required.
Though the timeentries slices should include also the data from unposted timesheets.
So to add to Rob's list is verify that the timesheets are posted.
How often do you run Posting of Timesheets?
You need those timesheets posted before you can slice them.
If the data on the portlet is OK after that you could figure how frequently you should run those two jobs.
If not that was not the cause and the problem is somewhere else.
Every ten mins for us.
Did the posted suggestions resolve your issue? If so please make Solution Accepted.
Yes, these suggestions were very helpful, we are going to monitor the situation a few more weeks but so far we think it is resolved. We will make the solution accepted.
We run it every 10 minutes 24 x 7. No issues or problems.