You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Requisition Approval Cycle Time - Removing the "Saved as Open" event from calculation

Received Response
27
Views
1
Comments
edited Mar 3, 2017 8:11PM in Reporting and Analytics Taleo Enterprise 1 comment

Summary

Requisition Approval Cycle Time - Removing the "Saved as Open" event from calculation

Content

Hello - 

 

We're attempting to calculate our requisition approval cycle time using the formula below:  

 

AVG(TIMESTAMPDIFF(SQL_TSI_DAY, "Requisition First To Be Approved Date"."Req. First To Be Approved Date", "Requisition Latest Fully Approved Date"."Req. Latest Fully Approved Date"))

 

There are cases where we have a requisition initially approved and then a change in our business requires us to modify the requisition and re-route the requisition for formal approval.  This is the reason for us needing to use the "Latest Fully Approved Date" versus the "First Fully Approved Date".  However, there are also cases where our recruiters need to place a requisition on hold (after the requisition has been fully approved) and then bypass the requisition approval by using the "Saved as Open" function.  For some reason, our cycle time calculation (as listed above) is using the date and

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!