ID629 - Parts Required on Incomplete Call Overview & Sample

This alert will provide you a regular report showing all the parts that techs were missing in their car stocks and were therefore forced to reschedule (considers all rescheduled calls regardless of whether PO linked to call or not). The alert can look to see exactly what parts the tech had in stock at the time (s)he rescheduled the call and report only those parts that the tech was missing at that time, so you get a read on exactly which parts are causing you problems. The automated alert will provide a monthly report, and a Custom Report is also available to run directly from eAutomate so you can change date ranges or focus in on specific techs or categories of part. The only thing we can't report is any (bad sync) parts the tech may have needed since that is just a text field and the part is entered later.

To further clarify:  The report looks to see what parts were in stock in their trunks at the time the call was rescheduled, not just the incomplete calls that have parts on them. So the list of parts from calls with an incomplete code will not match to what the report is showing you for that technician.


**Alert must be set to run monthly ONLY as it configured to only consider the previous month's activity.**

Alert and report will consider inactive technicians. This is necessary for historical purposes and would cause inaccurate numbers if we excluded inactive technicians. This also requires each technician be assigned their own warehouse (not Main Warehouse, for example). This is also required even after tech's leave, their warehouse would ideally be made inactive, not changed to another tech name/assignment. This is necessary to keep warehouse activity specific to tech. 

If you do not see the report in your custom reports console, please email and we will get it installed for you.

See also ID393 and ID628 for other alerts addressing this issue.




VariableW: The number of reschedules required before a part will trigger the alert. If you enter 2 then it will trigger when a part has caused MORE THAN 2 reschedules in the report's time frame (calendar month) This can be set to 0 to consider EVERY reschedule .

VariableY: Branch numbers you want the alert to trigger on. **Although you can limit which branches will trigger, the number on the output is for all branches. This will be changed once the report is converted to SSRS.


Available Custom Report Filters:


**Custom Report reports on all calls rescheduled for parts (unlike alert where you set how many reschedules via VariableW)

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk