# Epicor Kinetic UD Tables and UD Fields: Setup, Studio Binding, BAQ and Security > Source: https://netray.co/erp-help/epicor-kinetic-ud-table-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer UD tables (UD01, UD02 and so on) are Epicor's pre-built user-defined tables with a fixed set of key and data columns that you label and expose through a menu program. UD fields are extra columns on standard tables like OrderHed. Both are set up in system maintenance, shown in screens with Application Studio, and readable in BAQs. ## Kind how-to ## System epicor ## Erp Epicor Kinetic ## Module User Defined Tables and Fields ## Query epicor kinetic ud table ## Alternate Queries - epicor ud table setup - epicor ud fields application studio - epicor create ud table - epicor ud01 table baq ## Applies To Epicor Kinetic and 10.x. Menu names differ slightly between releases; use the menu search. ## Steps ### How to create and use a UD table **Items:** - Pick an unused UD table (for example UD05) and confirm nobody else uses it, because UD tables are shared per company and reused by customizations. - Open the UD table maintenance programs from the System Setup/Management menus (search for UD Column Maintenance and UD Table) and give the table and columns your own labels. - Set the key fields (Key1 to Key5) and mark which data columns you use, such as Character01, Number01, Date01, CheckBox01. - Add a menu item for the UD table's maintenance program in Menu Maintenance, then give the right security group access. - Open the screen in Application Studio, create a layer, and arrange the columns on a new grid or form. - Create a BAQ on the UD table to report on the data. - Test in a pilot company, then deploy the layer. ## Sections ### UD tables versus UD fields **Body:** A UD table is a whole table shipped empty: UD01 to UD05 and more, each with five key columns and a standard pool of character, number, date and checkbox columns. You decide what each means. A UD field is the same idea attached to a standard table, so OrderHed has Character01, Number01 and so on, where you store an extra item of data about the order. Choose a UD table when the data is its own list with its own key, such as a customer approval log or a tooling register. Choose a UD field when the data belongs to an existing record, such as an extra flag on a part. Newer releases also offer extended user-defined options through Application Studio, so check what your release provides before building around the older UD pattern. ### Showing it on a screen with Application Studio **Body:** Application Studio lets you add UD fields to a standard screen: open the screen, enter edit mode, pick the UD field from the data view, and drop it on the form. Set the label and the control type, such as a combo bound to a UD code list. Save the change in a customization layer, not in the base layer, so upgrades keep it. For a UD table, you can add a related grid on a standard screen by binding a data view to a BAQ or a service. The pattern varies by release, so build one small working example first. ### BAQ access and security **Body:** A UD table is available as a table in Query Builder like any other, with its columns under their original names such as Character01. Rename the display label in the BAQ so the report reads clearly. Join on the key fields and always include Company. Security has two layers: who can open the menu item, and what the Security Maintenance setting allows on the business object. Grant the least needed. If a UD table holds sensitive data, restrict both the program and any BAQ over it. **Code:** - -- Equivalent SQL for a BAQ on UD05 SELECT u.Key1, u.Character01, u.Number01 FROM Ice.UD05 u WHERE u.Company = 'EPIC06' ## Pitfalls - Two projects using the same UD table for different purposes, which corrupts data. - Changing the base layer in Application Studio instead of a custom layer. - Giving menu access without also checking the security on the business object. - Using a UD field when you need many rows per record. That needs a UD table. - Forgetting that UD column labels do not rename the database column in a BAQ. ## Ai Angle An assistant that can read the schema can show which UD tables and fields are already in use and what they hold, which is the question you need answered before reusing one. It can propose a layout for the new screen for a developer to review. With a private model, the schema stays inside your network. ## Faq ### How many UD tables does Epicor have? **Answer:** Epicor ships a numbered set of UD tables, UD01 and up. The exact set depends on the release. Check the table list in the maintenance program for your system. ### Can I rename a UD column? **Answer:** You can change the label shown on screens and in the maintenance program. The database column name stays as Character01 or Number01, so BAQs use that name with a friendly display label. ### Where do I put the UD field on a screen? **Answer:** In Application Studio, open the screen, enter edit mode, and add the field from the data view. Save it in your own layer so an upgrade does not remove it. ### Can I report on a UD table? **Answer:** Yes. Build a BAQ in Query Builder using the UD table, add Company and the key fields to the criteria, and publish it to a dashboard or report. ## Search terms epicor kinetic ud table, epicor ud fields, epicor ud table setup, epicor ud01, epicor application studio ud field, epicor ud column maintenance, epicor user defined table, epicor baq ud table --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json