# Epicor Kinetic BPM Directive Inventory Worksheet > Source: https://netray.co/tools/epicor-kinetic-bpm-directive-inventory-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable register of your Epicor directives with owner, purpose, risk score and review date, exportable to Excel. ## Category epicor ## Erp Epicor Kinetic ## Audience - Epicor administrator - Epicor developer ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Directive name **Key:** name **Type:** text #### Type **Key:** kind **Type:** select **Options:** - Method - Data - Function #### Service or table **Key:** target **Type:** text #### Timing **Key:** timing **Type:** select **Options:** - Pre-processing - Base processing - Post-processing - In-transaction - Table trigger #### Owner **Key:** owner **Type:** text #### Purpose **Key:** purpose **Type:** text #### Impact (1-5) **Key:** impact **Type:** number #### Complexity (1-5) **Key:** complexity **Type:** number #### Risk score **Key:** risk **Type:** number **Expr:** impact * complexity **Format:** integer #### Next review **Key:** review **Type:** date **Rows:** #### JobEntry block unapproved rev **Kind:** Method **Target:** JobEntry.Update **Timing:** Pre-processing **Owner:** Production control **Purpose:** Stop release when revision unapproved **Impact:** 4 **Complexity:** 2 **Review:** 2027-03-01 #### PO line default buyer **Kind:** Data **Target:** PODetail **Timing:** Table trigger **Owner:** Purchasing **Purpose:** Default buyer from part class **Impact:** 2 **Complexity:** 1 **Review:** 2027-03-01 #### Ship note email **Kind:** Method **Target:** CustShip.Update **Timing:** Post-processing **Owner:** Logistics **Purpose:** Email customer on shipment **Impact:** 3 **Complexity:** 3 **Review:** 2027-06-01 #### Calc landed cost fn **Kind:** Function **Target:** Custom function library **Timing:** Base processing **Owner:** Finance **Purpose:** Allocate freight to receipts **Impact:** 5 **Complexity:** 4 **Review:** 2027-01-15 **Totals:** #### Total risk points **Key:** risk **Agg:** sum **Format:** integer **Summary:** #### Average risk score **Key:** avg_risk **Expr:** sum_risk / count **Format:** decimal **Primary:** true #### Highest single risk **Key:** top_risk **Expr:** max_risk **Format:** integer **Notes:** Impact is how bad it is if the directive fails; complexity is how hard it is to understand. Review anything scoring 15 or more before the next upgrade. ## Content **Intro:** Directives accumulate silently. A register with owner, purpose and a risk score tells you what to test before an upgrade and what to retire. This worksheet is a place to start that register without building a database. **Sections:** #### How to use the worksheet **Body:** List each directive from the directive maintenance screens, add the service or table it fires on, and write one line of purpose. Score impact and complexity from 1 to 5 and the risk score is calculated for you. Export to Excel to share with developers or to attach to an upgrade plan. Replace the example rows with your own. **Bullets:** - Capture the owner as a business role, not only an IT name - Write purpose in plain language - Set a review date for each row #### Types and timing **Body:** Method directives run when a service method such as an update is called, with pre-processing, base processing and post-processing points. Data directives fire on table changes, and in-transaction directives run inside the database transaction. Function directives call Epicor Functions. Recording the timing matters because the same logic behaves differently if it runs before or after the base processing. #### Reading the risk score **Body:** Impact times complexity gives a score from 1 to 25. A low-impact simple directive scores under 5 and can be reviewed yearly. A critical, complicated one scores above 15 and belongs on the upgrade regression test list, with a second person who understands it. The score is for prioritising your attention, not a standard metric. #### Common mistakes **Body:** People list directives once and never update them. Others forget directives that are disabled but still present, or ones written by consultants who left. Reconcile the register against the system every quarter and assign orphaned items to someone. **Bullets:** - No owner for consultant-built directives - Disabled directives left undocumented - No link to the change request **Cta:** If you have inherited hundreds of directives, we can help build a private assistant that reads exported definitions and summarises what each one does. **Faq:** #### Can I export the directive list from Epicor directly? **Answer:** Depending on version and tooling, you can often query directive metadata or export definitions. Check what your environment supports, then paste the names into this worksheet and add the business context that no export contains. #### Why score risk at all? **Answer:** To decide what to test first. Upgrades and cloud releases touch many objects, and you rarely have time to test everything. A simple score ranks the directives where a failure would hurt most. #### Does it work for Application Studio layers? **Answer:** Not directly, since those are client layers. You can still list them here using the Type column Method or add your own wording, or keep a separate register using the customization change request form. #### Is there a limit to rows? **Answer:** The worksheet is intended for working registers of a few dozen to a few hundred rows. For bigger inventories, export to Excel and continue there. ## Search terms epicor bpm inventory, epicor directive list excel, epicor method directive documentation, epicor customization inventory, epicor upgrade customization review, epicor bpm documentation template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json