Timesheet recall functionality

[Shyna1]

Hi ,

Can someone help me understanding how does recall timesheet/timecard works.

What changes are made and how does it reflect in the timecard.

Thanks in advance!

[Namita Mishra · Accepted solution]

Hi @Shyna ,

Timesheet recall capability allows the timesheet approver to recall an incorrect time sheet (in Approved or Processed state) & return it to the time sheet submitter.

Timesheet recall:

• Impact on State: Changes the state of the time sheet and associated time cards to 'Recalled'.
• Impact on Demand / Project Actual Effort: Reverts the actual effort and resource hours in a project or demand created when time cards that have task types were approved.
• Impact on Expense Lines: Creates negative expense lines to zero out the corresponding expense lines created when the time sheet was approved.

NOTE:

1. Timesheet recall functionality works if 'Allow recall' option is selected in the associated timesheet policy. By default this option is checked.

2. Out of the box, timesheet / time card can be recalled within 30 days. Admin can configure this duration. They can decrease or increase the number of days using 'Recall period allowed (days)' property present in the timesheet policy.

Feel free to mark this as a correct answer if I was able to solve the query.

Thanks,

Namita Mishra

[Dave Carlin]

Why do the reverted hours not show a negative amount (like the Expense Line dollars)?  This causes problems when running reports from the Timecard_to_Expense_Line table.  A 40 hour timecard that was Recalled will show $0, but 80 hours...rather than $0, and 0 hours.  Is there a work-around for this?

[Namita Mishra]

Hi @Dave Carlin ,

Statement "A 40 hour timecard that was Recalled will show $0, but 80 hours...rather than $0, and 0 hours" doesn't seem to be correct.

Actually, recall with revert the cost and it is as good as time card has not submitted. It should not double the hours.

Is 'Timecard_to_Expense_Line',  OOTB table \ view? Can you please clarify.

Thanks,

Namita Mishra

[Dave Carlin]

Hi Namita,

Our SNOW administrator confirmed that we are using OOTB tables, and creating a Database View of 4 tables: fm_expense_line, time_card, pm_project_task, and fm_rate_card.

The issue RECALL is creating is that is deletes the details from the fm_expense_line table, while the details are retained with the time_card table.

My understanding is that SNOW is a transactional tool, so it should keep historical details on all transactions...specifically, the fm_expense_line table details of the original & the RECALL-ed transaction.

Please advise,

Dave