Epicor UD Table Design Worksheet
UD tables are the standard way to add custom data to Epicor without changing the base schema. Plan them on paper first, because keys and data types are hard to change once data is loaded.
| UD table | Column label | Data type | Role | Length or size | Required (1 or 0) | Business purpose | |
|---|---|---|---|---|---|---|---|
UD tables in Epicor have standard columns like Key1 to Key5 and numbered Character, Number, Date and CheckBox fields, plus user defined labels. Names and counts vary by release and by table, so confirm what UD Table maintenance offers in your system before building. Plan keys first, since changing a key later is hard.
Review your custom data model
Optional: talk through how an assistant could document your UD tables and their usage.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add one row per column you intend to use. Pick the UD table, give the column a clear label and the business purpose, and mark whether it is a key, a data column, a lookup or a flag. Record the data type and size. The summary shows how many columns you plan and what share is required. Export to Excel and review it with the business owner before anyone touches the UD maintenance screen.
- Define keys before data columns
- Describe every column in business terms
- Mark required columns explicitly
- Review with the business owner
Designing keys
A UD table identifies each record through its key columns, so the keys decide what makes a row unique. Choose keys that are stable and meaningful, such as customer number and rule type, rather than free text that users may mistype. Avoid using a description as a key. If a record might need two rows for the same customer and rule at different dates, include the date or a sequence in the key.
Data types and sizing
Use the narrowest type that fits: logical for yes or no, integer for counts, decimal for amounts, date for dates and character for text. Keep character sizes realistic, since oversized fields invite free text that is hard to report on. Where users choose from a list, plan a lookup source or a validated value list so reports stay consistent.
When not to use a UD table
If the data is a single extra attribute on a standard record, a UD field on that record may be simpler. If you need heavy reporting, many relationships or high volumes, a UD table can become awkward and a separate database or integration may be better. Also consider how UD data flows into BAQs, reports, REST and upgrades before you commit.
- One extra attribute usually fits a UD field
- High volume or many relations may need another store
- Plan how reports and REST will read it
- Document the table in your inventory
Frequently Asked Questions
What is a UD table in Epicor?
A user defined table is a standard Epicor table such as UD01 or UD100 that you can configure with your own key labels and data columns. It stores custom data that does not fit in the standard schema.
How many UD tables are available?
Epicor ships a set of numbered UD tables, and the exact list depends on your release. Check UD Table maintenance in your system. Some are reserved for standard use, so confirm availability before planning.
Can I change a UD table key later?
It is difficult once data exists, because existing rows, BAQs, reports and code depend on the key. Treat keys as final during design, and test the table with sample data before using it in production.
Should I use a UD table or a UD field?
Use a UD field when you only need extra attributes on an existing record such as a part or customer. Use a UD table when you need a separate set of records with their own keys, such as rules or lookups.
If you want to review your UD tables and customizations against live data without writing queries by hand, Netray can discuss a read-only assistant for your Epicor environment.
Related Tools
Epicor Table Reference: Erp.Part, Erp.JobHead, Erp.OrderHed
Searchable list of frequently used columns in three core Epicor tables, with type and usage notes for BAQs, reports and REST queries.
EpicorEpicor Application Studio Layer Checklist
A checklist for Kinetic Application Studio layers covering naming, scope, events, rules, security, testing and upgrade impact.
EpicorEpicor Function Library Design Template
A design document for an Epicor function: signature, inputs, outputs, logic notes, security, test cases and sign off.
EpicorEpicor BAQ Calculated Field Examples Reference
A searchable cheat sheet of BAQ calculated field expressions you can copy into the Query Builder, grouped by dates, quantities, pricing and text.
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