2863045 - App Status Audit Trail - Time In Status shows 0:0:0 for Not Skipped status - Recruiting Management

In the App Status Audit Trail report, the 'Time In Status (days:hours:minutes)' column shows '0:0:0' while the 'Skipped Status' column is 'Not Skipped'.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP SuccessFactors Recruiting Management

The time spent in the application status is less than one minute.

‘Time in Status(days:hours:minutes)’ is calculated as the time the applicant entered the status to the time the applicant left the status.

It formats the time up to the ‘days’ and down to the ‘minutes’. For example, ‘0:0:3’ means ‘three minutes’.

Because it doesn't show the time in the 'days:hours:minutes:seconds' format, if the time spent in the status is less than one minute, it will show ‘0:0:0’.

Q&A

1. How to differentiate between candidates who completely skipped a status vs candidate who spend less than one minute in a status?
   We can utilize the "App Status Audit Trail - Skipped Status" column as a filter.
   
   If the report shows – a certain status is “Not Skipped” & its corresponding time in status is “0:0:0” -> it determines that the time spent in that status is less than a minute
   If the report shows – a certain status is “skipped by user” & its corresponding time in status is “0:0:0” -> it determines that the status is skipped by the user
   
   
2. How can we know if the time spent in the status is less than one minute?
   We can use the "App Status Audit Trail - Created Date" column to compare the timestamps the applicant entered the Application Statuses.
   Example report:
   

2685059 - Behavior of 'Time in Status' and 'Days in Status' in adhoc Report for Hired Candidates

Time in Status, App Status Audit Trail, Recruiting V2, job application , KBA , LOD-SF-RCM-REP , Reporting & Analytics, Data Imports & Exports , LOD-SF-RCM-APP , Applicants and Job Applications , Problem