SAP B1 UDF: User-Defined Fields and the Warehouse
Company-specific U_ fields in SAP B1 hold some of the most valuable and most fragile reporting data. How to find them, clean the values and move them to a warehouse.

A standard SAP B1 installation has no place for sales channel, return reason or project code. Companies put that information in their own fields. The data that would help reporting most is often in those fields, and they are also what causes the most trouble when moving data to a warehouse.
What a user-defined field is
In SAP Business One, user-defined fields (UDFs) are fields a company adds to standard tables. SAP's learning material says they are added to the database table of the respective object and can be quickly recognised there by the prefix U_. The developer documentation says the UserFieldsMD object manages these fields in user and system tables and names CUFD as its source table. Sources: SAP Learning and SDK Help, UserFieldsMD.
Why moving them is hard
- Every company differs. A
U_Kanalin one place is absent elsewhere or means something else. A ready-made report template cannot know. - Values are inconsistent. In a free-text field, 'Web', 'web' and 'WEB' count as three channels.
- History is empty. If the field was added later, older documents have no value; the report should show earlier periods as 'unknown', not as zero.
- Fields can change. If someone removes or renames a field, a load that selects columns by name fails the next day.
Steps for moving them
- Take an inventory. Which U_ fields exist in which table, and how many are filled? Moving an empty field is pointless.
- Write down the meaning. Get a one-sentence definition from the business owner: what is it, who fills it, and when?
- Map the name. Add a mapping layer such as
U_Kanal→sales_channelso the warehouse name does not depend on one company's accidental naming. - Normalise the values. Reduce spelling variants to one value and turn blanks explicitly into 'unknown'.
- Fail loudly when a field is gone. A load that silently skips produces an incomplete report.
Where Floemdata stands
Floemdata's SAP discovery step takes an inventory of user-defined fields in specific document and master tables (sales invoice and lines, credit note and lines, business partner, item, sales order and lines). The extraction layer can select requested U_ fields in the six components where the manifest permits UDFs; it validates the name and, if a requested field is missing from the table, stops the extraction with an error. The mock SAP database used in development carries the CUFD table plus two example fields (sales channel and return reason).
We did not find code that turns UDF values into a named, cleaned, reportable field in the Silver or Gold layer, so no ready-made report breaks figures down by UDF today. That it works with a real customer's UDFs is not verified. The steps in this article are an implementation guide, not a finished result the product delivers.
To begin, list the CUFD table with your SAP query tool and write next to each field: which report will use this information? Questions are welcome at info@floemdata.com or via Floemdata.