Epicor Customization Change Request Template
Most Epicor problems after an upgrade trace back to a small change nobody documented. A short change request that records the need, alternatives and impact makes customization a managed decision instead of a favour.
Fill in
Epicor Customization Change Request Template
Change Request CR-0142
Company: Acme Precision Ltd Requested by: Plant manager Date: 2026-10-20 Area: Production management Type: UD field or table Priority: Medium
Business need
Shop supervisors need to record the fixture ID used on each job operation so repeat issues can be traced.
Alternatives considered
Standard job notes were tested but cannot be filtered or reported on.
Impact and dependencies
Job entry and shop traveler report. No integration impact. Needs a new job operation UD field and one report change.
Estimated effort
3 days build, 2 days test
Test plan
| Test | Environment | Tester | Result |
|---|---|---|---|
| Functional test of new behaviour | Pilot | ||
| Regression of related screens | Pilot | ||
| Report output check | Pilot | ||
| User acceptance | Pilot |
Approvals
Always build and test in a pilot or test environment before promoting. Record the Epicor version and the date of promotion to live on the approved copy.
Customization inventory help
An optional review of your Epicor customizations and which ones to keep, retire or rebuild.
Optional. The tool and every export work without this. No spam.
How to use it
The requester fills the business need in plain language and the Epicor administrator completes the type, impact and effort. Capture whether a standard setting or an existing feature could solve it first. Export the form, attach it to your ticketing record, and collect the approval signatures before development starts.
- State the need, not the solution
- Always list alternatives
- Name affected screens and reports
- Get approval before building
Choosing the change type
Configuration only changes such as new codes or security settings are the cheapest and upgrade safest. UD fields and screen customizations are moderate. BPM directives and custom code carry the most behavioural risk because they run inside transactions. Choosing the lightest type that meets the need keeps the upgrade path simple.
Impact analysis
List screens, reports, directives and integrations that touch the same objects. A new required field can break DMT loads and EDI imports. A report change can affect printed paperwork used by customers. Ask who else uses the process and add them to the test plan so regression coverage reflects actual use.
Common mistakes
Skipping alternatives, approving without a test plan and promoting directly to live are the three most frequent failures. Another is losing the request after delivery. Keep the approved form with the object names it created, so an upgrade team can find out why something exists.
Frequently Asked Questions
Why use a change request for small Epicor changes?
Small changes accumulate. A field here and a directive there become the upgrade risk you cannot explain later. A one page form takes minutes and leaves a record of purpose, owner and test evidence, which pays off during audits and upgrades.
Who should approve an Epicor customization?
At least the process owner who needs it and the Epicor administrator or IT owner who maintains it. Larger changes may also need finance or quality sign off if they affect costing, compliance records or controlled documents.
Does this replace my ticketing system?
No. Attach the exported form to the ticket. The template standardises the content, and your ticketing system tracks status, assignment and history. Together they give you a complete change record.
What should be tested before promoting?
The new behaviour, related screens that share objects, reports that print the affected data, imports or integrations that write the same tables, and security for users with different roles. Record who tested and in which environment.
If you are planning an Epicor upgrade and want your customizations assessed, Netray can help classify and prioritise them.
Related Tools
Epicor BPM Directive Design Template
A fill-in design document for BPM method and data directives covering trigger, conditions, actions, testing and rollback.
EpicorEpicor Customization Code Review Checklist
A checklist for reviewing Epicor custom code, BPM directives and customizations before promotion to live.
EpicorEpicor UAT Test Script Worksheet
An editable UAT script for Epicor with expected results, tester, status and defect counts. Track pass rate and export to Excel.
EpicorEpicor User Defined Field Register Worksheet
A register of UD fields with table, column, label, owner and populated row counts. Spot unused fields and export to Excel.
More Epicor tools
See all- Epicor Kinetic Customization Change Request Form Template
- Epicor Kinetic Go-Live Cutover Plan Template
- Epicor Kinetic User Access Request Form Template
- Epicor Kinetic BPM Directive Inventory Worksheet
- Epicor Kinetic Scheduled Task Register Worksheet
- Epicor Kinetic Custom Report Inventory Worksheet
- Epicor Kinetic Data Migration Mapping Worksheet
- Epicor Kinetic Data Load Effort Calculator
- Epicor Business Object Services Reference