Time-card monthly reporting

[pbatt]

Hi everybody,

We have recently implemented the module Demand & Project Portfolio Management on Service Now and we're really excited about it. Anyway, we'd like to share with you on some specific issues concerning the Time-Card Module.

THE ISSUE

The Time-carding in Snow has a level of granularity that it's weekly and it's based on the field week start on.

This kind of partition for weeks is not very useful for "time-card monthly reporting" . In fact, for the weeks that fall within two months, it's not possible to figure out how many hours the resources have worked per month (previous month or the next one). For example, I'd like to have a monthly (obviously, a monthly calendar) report concerning my resources time-card (sum of total hours worked).

Has anyone ever had this kind of problem? Any suggestion?

Thanks a lot,

Pierluigi

[JFolsom]

Curious if there is anything new on this inquiry. My company is pulling resource allocations based on a monthly basis (1/1/20-1/31/20) but cannot compare that to the same date range actuals. We are attempting to evaluate our accurateness of estimates but when the date ranges are different it makes it challenging. I was looking to see if there is a way to pull a timecard report that shows me the actual date (rather than week starts on) and hours worked in that given day.

Thanks.

[Andrew Bettcher]

Nada. I've spent a lot of time looking at this issue since I posted originally (wow!! was it really...) 2 years ago and had a lot of conversations with a lot of people regarding the issue. I'm always surprised at how surprised some people are when they learn of this issue. Surely it's major? Why have a time accounting system that doesn't know that if the first day of the week is the 7th then the 2nd day of the week is the 8th??

Numerous possible solutions have been proposed along the way but nothing I was able to actually implement.

Now, all of our time sheet data is scraped into QlikView which slices and dices it BUT we still have the restriction imposed by the "week starts on" date.

Meanwhile, look at all of the new features in the latest versions. A lot of work had been put in to getting them over the line but no work has been put in to resolve the glaring problems with long established applications.

[Philip1]

Any updates or insights here? I have the same dilemma and need inspiration to solve this! 

[Andrew Bettcher]

Hi Philip,

What version are you on? From Paris onwards there is a table called time_card_daily that stores each time card entry against a proper date (see here).

We switched our reporting to this table and can full calendar month time reports without using any post-report processing.

[Philip1]

Great! I will take a look at that table. We are currently on Orlando, but we are upgrading to Paris within 8 weeks.