- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2020 08:31 AM
It was brought to my attention that the time tracked against a project in ServiceNow did not match the actual time worked. Below are screen shots and an example to be reviewed.
The project is PRJ0044828. The resource plan RPLN0007272 was set for 11/11/2019 – 3/11/2020 with 45 hours allocated.
The resource plan shows 49.02 actual hours.
The timecard shows a total of 83.05 hours tracked. The yellow highlights are what I am questioning as to why they did not track against the resource plan. The first three dates were outside of the resource plan.
Week starts on |
Description |
User |
Manager |
Number |
Task |
Resource plan |
Sunday |
Monday |
Tuesday |
Wednesday |
Thursday |
Friday |
Saturday |
Total |
10/27/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
0.00 |
0.00 |
1.00 |
0.02 |
0.00 |
0.00 |
0.00 |
1.02 | ||
11/03/2019 |
Username |
Username2 |
PRJ0044828 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 | |||
11/03/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
0.00 |
0.17 |
0.00 |
0.17 |
0.00 |
0.17 |
0.00 |
0.51 | ||
11/10/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
RPLN0007272 |
0.00 |
0.00 |
1.00 |
0.50 |
1.00 |
0.25 |
0.00 |
2.75 | |
11/17/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088788 |
RPLN0007272 |
0.00 |
1.00 |
0.00 |
0.00 |
0.50 |
0.00 |
0.00 |
1.50 | |
11/17/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
RPLN0007272 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
2.00 |
0.00 |
2.00 | |
11/24/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
RPLN0007272 |
0.00 |
2.75 |
0.50 |
2.50 |
0.00 |
0.00 |
0.00 |
5.75 | |
12/01/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
RPLN0007272 |
0.00 |
3.75 |
6.00 |
3.50 |
5.00 |
2.50 |
0.00 |
20.75 | |
12/08/2019 |
Username |
Username2 |
PRJ0044828 |
RPLN0007272 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 | ||
12/08/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
RPLN0007272 |
0.00 |
2.50 |
1.00 |
4.50 |
2.00 |
2.00 |
0.00 |
12.00 | |
12/15/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
MISSING DATA |
0.00 |
3.00 |
2.00 |
4.00 |
0.00 |
2.00 |
0.00 |
11.00 | |
12/22/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
MISSING DATA |
0.00 |
3.00 |
0.00 |
0.00 |
1.75 |
0.00 |
0.00 |
4.75 | |
12/22/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
MISSING DATA |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
2.00 |
0.00 |
2.00 | |
12/29/2019 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
MISSING DATA |
0.00 |
0.00 |
0.00 |
0.00 |
2.50 |
2.00 |
0.00 |
4.50 | |
01/05/2020 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
MISSING DATA |
0.00 |
2.75 |
1.50 |
1.50 |
0.00 |
0.50 |
0.00 |
6.25 | |
01/12/2020 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
MISSING DATA |
0.00 |
0.02 |
0.00 |
0.00 |
0.50 |
1.50 |
0.00 |
2.02 | |
01/12/2020 |
Username |
Username2 |
PRJ0044828 |
RPLN0007272 |
0.00 |
0.25 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.25 | ||
01/19/2020 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
MISSING DATA |
0.00 |
0.00 |
1.50 |
0.00 |
0.50 |
0.00 |
0.00 |
2.00 | |
01/19/2020 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
MISSING DATA |
0.00 |
0.00 |
0.00 |
2.50 |
0.00 |
0.00 |
0.00 |
2.50 | |
01/19/2020 |
Username |
Username2 |
PRJ0044828 |
PRJTASK0088785 |
MISSING DATA |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
1.50 |
0.00 |
1.50 | |
01/19/2020 |
Username |
Username2 |
PRJ0044828 |
RPLN0007272 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 |
0.00 | ||
83.05 |
Solved! Go to Solution.
- Labels:
-
Customer Service Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2020 01:26 PM
Hello
This is the expected behavior as of New York and is even reproducible Out of the Box.
Pretend that you have a single Project with 1 Project Task under it. You have 1 Resource Plan for the main Project.
When you create a Time Card for the Project, it will populate with the Resource Plan but will not if you create a Time Card on the Project Task.
This was confirmed by our Development Team as an intentional change for the following business case:
Problem Statement: If the Project has more than one Resource Plan, then the system defaults to one of the valid Resource Plans (any of the Resource Plans associated with the respective Top Task) to the Time Card logged against any of the Project Tasks or Project. This way the actual hours get logged against some random Resource Plan.
Solution: The Resource Plan defaulting is restricted to Resource Plan directly associated with the Project Task or Project against which the Time Card is being logged. This makes sure that the actual hours get logged against the appropriate Resource Plan.
In addition to this, the Time Sheet Portal has been enhanced so that the Time Card User can select Resource Plan for the submitted Time Card if there are more than one Resource Plans are associated with the Task (directly) against which the Time Card is being logged.
This behavior is defined by these related Scripts and Methods if you wish to customize this to go back to the previous behavior:
"Populate Resource Plan" Business Rule
"ResourceActuals" Script Include
"getResourcePlanForTimeCard" Method
"getResourcePlanForTimeCardHelper" Method
"_getAllocationWithinDateRanges" Method
Hope that helps!
If it did, please mark as Helpful and consider setting the reply as the Correct Answer to the question, thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2020 01:26 PM
Hello
This is the expected behavior as of New York and is even reproducible Out of the Box.
Pretend that you have a single Project with 1 Project Task under it. You have 1 Resource Plan for the main Project.
When you create a Time Card for the Project, it will populate with the Resource Plan but will not if you create a Time Card on the Project Task.
This was confirmed by our Development Team as an intentional change for the following business case:
Problem Statement: If the Project has more than one Resource Plan, then the system defaults to one of the valid Resource Plans (any of the Resource Plans associated with the respective Top Task) to the Time Card logged against any of the Project Tasks or Project. This way the actual hours get logged against some random Resource Plan.
Solution: The Resource Plan defaulting is restricted to Resource Plan directly associated with the Project Task or Project against which the Time Card is being logged. This makes sure that the actual hours get logged against the appropriate Resource Plan.
In addition to this, the Time Sheet Portal has been enhanced so that the Time Card User can select Resource Plan for the submitted Time Card if there are more than one Resource Plans are associated with the Task (directly) against which the Time Card is being logged.
This behavior is defined by these related Scripts and Methods if you wish to customize this to go back to the previous behavior:
"Populate Resource Plan" Business Rule
"ResourceActuals" Script Include
"getResourcePlanForTimeCard" Method
"getResourcePlanForTimeCardHelper" Method
"_getAllocationWithinDateRanges" Method
Hope that helps!
If it did, please mark as Helpful and consider setting the reply as the Correct Answer to the question, thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2020 12:45 PM
How do I learn more about "getResourcePlanForTimeCard"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2022 10:31 AM
I am not sure I understand the explanation as we are currently experiencing the same discrepancy between the actual hours versus what the total timecard hours show for a user. The user is pulling in the same resource plan on their timecard, but the actual hours on their resource plan is less than what the total hours show on the timecard report that uses the same resource plan.
We are currently using the Rome version of SN, but noticed the discrepancy starting in Quebec.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2020 09:18 PM