# SAP Business One User-Defined Fields and Tables Register > Source: https://netray.co/tools/sap-b1-udf-udt-register-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable register of every user-defined field and table in a Business One company, with owner, purpose and change status. ## Category sap ## Erp SAP Business One ## Audience - B1 administrator - B1 consultant - Developer - Auditor ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Table **Key:** table **Type:** select **Options:** - OITM - OCRD - ORDR - OQUT - ODLN - OINV - OPOR - OWOR - OWHS - UDT (custom) #### Field name **Key:** field **Type:** text #### Title **Key:** title **Type:** text #### Type **Key:** ftype **Type:** select **Options:** - Alphanumeric - Numeric - Date/Time - Units and Totals - Memo #### Size **Key:** size **Type:** number #### Mandatory **Key:** mandatory **Type:** select **Options:** - Yes - No #### Purpose **Key:** purpose **Type:** text #### Business owner **Key:** owner **Type:** text #### Status **Key:** status **Type:** select **Options:** - Proposed - Approved - In use - Retire **Rows:** #### Drawing revision **Table:** OITM **Field:** U_DrawingRev **Ftype:** Alphanumeric **Size:** 10 **Mandatory:** Yes **Purpose:** Engineering revision of the drawing **Owner:** Engineering **Status:** In use #### Approved until **Table:** OCRD **Field:** U_ApprovedUntil **Ftype:** Date/Time **Size:** 0 **Mandatory:** No **Purpose:** Supplier approval expiry for quality **Owner:** Quality **Status:** In use #### Customer PO reference **Table:** ORDR **Field:** U_CustPONo **Ftype:** Alphanumeric **Size:** 30 **Mandatory:** No **Purpose:** Reference for customer invoices **Owner:** Sales **Status:** Approved #### Lead operator **Table:** OWOR **Field:** U_Operator **Ftype:** Alphanumeric **Size:** 20 **Mandatory:** No **Purpose:** Shift lead on the production order **Owner:** Production **Status:** Proposed #### Inspection plan code **Table:** UDT (custom) **Field:** U_Code **Ftype:** Alphanumeric **Size:** 20 **Mandatory:** Yes **Purpose:** Key of a user table for inspection plans **Owner:** Quality **Status:** Approved **Totals:** #### Fields registered **Key:** field **Agg:** count **Format:** integer #### Average field size **Key:** size **Agg:** avg **Format:** decimal **Notes:** Business One user-defined field names start with U_ in the database and are added through the user-defined fields management screen under customisation tools. Record the table, because a UDF belongs to one table only. Include user-defined tables, which appear with an at sign prefix in the database. ## Content **Intro:** User-defined fields are the easiest way to extend Business One and the easiest to lose track of. A register of every field, its owner and its purpose keeps upgrades, queries and audits predictable. **Sections:** #### How to use the register **Body:** Add one row for each user-defined field or table. Record the table it belongs to, the exact field name, type and size, whether it is mandatory, why it exists and who owns it. Set the status as the field moves from proposal to approval to use and finally retirement. Export to Excel for audit evidence or for the partner before an upgrade. #### Why it matters **Body:** Business One lets key users add fields to master data and marketing documents, which then appear in screens, print layouts, queries and add-ons. Without a register, nobody knows which fields reports depend on, and removing or renaming one can break a query or an integration. Field names also carry a U_ prefix in the database, so developers need the exact name, not just the screen title. **Bullets:** - One owner per field - State the report or process that depends on it - Record valid values for coded fields #### Design guidance **Body:** Prefer a linked user table with valid values for coded fields over free text. Keep sizes realistic, because changing a type later is restricted once data exists. Use mandatory sparingly, since mandatory fields on documents can block imports and integrations that do not supply them. Check that a standard field does not already cover the need before adding a new one. #### Common mistakes **Body:** Adding fields in production without testing, duplicating a standard field under another name, and leaving abandoned fields on screens. Include a retire status so cleanup is a planned step and not a one-off scare. **Cta:** If you need to find where custom fields are used across queries, layouts and add-ons, Netray can help build that inventory from your system. **Faq:** #### How do I list existing UDFs in Business One? **Answer:** Use the user-defined fields management screen under customisation tools, or query the system dictionary tables for field definitions. The exact table names and columns can vary by version and database, so confirm in your own system. #### Can I change a field's type later? **Answer:** Limited changes are possible, such as increasing size, but changing the basic type after data exists is restricted. Plan types carefully, and test changes in a copy of the company first. #### Should every field be mandatory? **Answer:** No. Mandatory fields can break imports, integrations and add-ons that do not populate them. Use mandatory only where the business truly cannot proceed without the value. #### Do UDFs affect upgrades? **Answer:** They are generally retained, but screens, layouts and add-ons that reference them need testing. The register tells your partner what to test. Always upgrade a copy first. ## Search terms sap business one user defined fields, sap b1 udf list, sap b1 udt documentation, udf register template, sap business one customization documentation, sap b1 custom fields spreadsheet, erp custom field register --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json