# Epicor Kinetic Scheduled Task Register Worksheet > Source: https://netray.co/tools/epicor-kinetic-scheduled-task-register-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable register of recurring Epicor tasks (MRP, reports, integrations) with schedule, duration, owner and failure contact. ## Category epicor ## Erp Epicor Kinetic ## Audience - Epicor administrator - IT operations - Finance systems analyst ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Task **Key:** task **Type:** text #### Category **Key:** category **Type:** select **Options:** - Planning - Financial - Report - Integration - Maintenance - Other #### Frequency **Key:** frequency **Type:** select **Options:** - Hourly - Daily - Weekly - Monthly - Quarterly #### Runs per month **Key:** runs **Type:** number #### Start time **Key:** start **Type:** text #### Typical duration (min) **Key:** mins **Type:** number #### Monthly run minutes **Key:** load **Type:** number **Expr:** runs * mins **Format:** number #### Business owner **Key:** owner **Type:** text #### Failure contact **Key:** contact **Type:** text **Rows:** **Task:** Regeneration MRP **Category:** Planning **Frequency:** Daily **Runs:** 22 **Start:** 02:00 **Mins:** 45 **Owner:** Planning **Contact:** Epicor admin **Task:** Daily open order report **Category:** Report **Frequency:** Daily **Runs:** 22 **Start:** 06:30 **Mins:** 5 **Owner:** Sales ops **Contact:** Epicor admin **Task:** EDI inbound poll **Category:** Integration **Frequency:** Hourly **Runs:** 528 **Start:** Hourly **Mins:** 1 **Owner:** Customer service **Contact:** IT integration **Task:** Month-end GL transfer **Category:** Financial **Frequency:** Monthly **Runs:** 1 **Start:** Day 1, 20:00 **Mins:** 30 **Owner:** Controller **Contact:** Finance systems **Task:** Database maintenance **Category:** Maintenance **Frequency:** Weekly **Runs:** 4 **Start:** Sun 01:00 **Mins:** 90 **Owner:** IT **Contact:** DBA **Totals:** #### Total monthly run minutes **Key:** load **Agg:** sum **Format:** number #### Number of tasks **Key:** task **Agg:** count **Format:** integer **Summary:** #### Total monthly run hours **Key:** hours **Expr:** sum_load / 60 **Format:** decimal **Primary:** true **Notes:** Use the start time column to spot overlaps between heavy jobs such as MRP and integrations. Verify real durations in your own logs. ## Content **Intro:** When a nightly job fails, the first question is who owns it and what depends on it. This register keeps every recurring Epicor task, its timing and its owner in one place so overlaps and gaps are visible. **Sections:** #### How to use the register **Body:** List recurring processes you have configured in the system agent or scheduling tools, including reports, planning runs, integrations and maintenance. Enter runs per month and typical minutes. Monthly run minutes are calculated and totalled. Export to Excel for an operations handbook, and review it whenever someone adds a schedule. **Bullets:** - Include integrations that poll on an interval - Add a failure contact for each - Review after every upgrade #### Why timing matters **Body:** Heavy jobs fight for the same database and application resources. A regeneration planning run, a large report batch and an integration poll starting at the same minute can slow each other and the day shift. Sorting by start time exposes collisions. Move non-urgent reports away from the planning window, and keep a buffer so the planning result is ready before planners arrive. #### Reading the totals **Body:** Total monthly run minutes is a rough measure of scheduled load, not a capacity limit. Its value is in comparisons: if it doubles after a project, find out which new tasks contributed. High-frequency polling jobs add up quickly even when each run is a minute, so check whether the interval needs to be that short. #### Common mistakes **Body:** Schedules created under a personal login stop when the account is disabled. Others are recorded nowhere, so nobody knows a report is emailed to a former employee. Use service accounts where your policy allows and clear unused schedules each quarter. **Bullets:** - Schedules owned by individual users - No contact for failures - Reports sent to departed staff **Cta:** If you want failures from scheduled tasks summarised and routed automatically, we can help design a private monitoring assistant that works from your own logs. **Faq:** #### Does this create schedules in Epicor? **Answer:** No. It documents schedules you have set up elsewhere. The value is a single readable list you can review, hand over and compare after upgrades or server moves. #### How do I find all the schedules? **Answer:** Review the recurring or scheduled process screens in your system and any external schedulers such as SQL Agent or Windows Task Scheduler. Include integration jobs that run outside Epicor but depend on it. #### What duration should I record? **Answer:** Use a typical or recent average from your logs, and note a long case in the task name if it varies a lot. The register is for planning, so a realistic average is better than a best case. #### Can I add columns? **Answer:** Export to Excel and add what you need, for example dependency or escalation. The online worksheet keeps a compact set of columns that suit most registers. ## Search terms epicor system agent schedule, epicor scheduled tasks list, epicor recurring process register, epicor mrp schedule worksheet, epicor batch job documentation, epicor task agent schedule template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json