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

[Deepak Ingale1]

Can you try with setting a filter in report condition

Created on Last Month?

That should give you what you require.

[john_duchock]

meh...i have users that create time cards that they "forgot" last month, so created_date and updated_date are not valuable.

[Mike Allen]

In a past working environment, we had to totally rework time cards because we had requirements akin to yours.   We reworked it into our own time card system that took daily measurements of time so that we could run reports on a month or a specific period of time (last 14 days, etc.).   Good luck with your own endeavors.

[bernyalvarado]

Indeed, and I believe this could be solved through a process aspect. On the week that fall within 2 months you could establish a process where 2 time cards are submitted for that week; one for each month. That way you could then keep a different accounting for each month and still leverage the OOB functionality.

Thanks,

Berny