23 apr

UDF (SAP Business One)

Versino Financial Suite

UDF (Abbreviation)

UDF stands for User Defined Field, in German Custom Field. It refers to additional attributes that are attached to standard objects in SAP Business One, such as items, business partners, journal entries, or document rows, without the need for add-on development or a change release. UDFs are the central instrument for adapting B1 to industry- or company-specific requirements.

Context

User-defined functions are created using Extras → Customisation Tools → Custom Fields - Management. For each field, the name, description, data type (alphanumeric, numeric, date, checkbox) and length are defined; valid values, default values, and a Link to a UDT. Technically, UDFs are stored as additional columns with the prefix U inserted into the respective database table — for example OITM.U_VPS_DTV_ACCT for a DATEV account override on the item or OCRD.U_VPS_DTV_ACCT for the DATEV debtor account at the business partner. The name is limited to 18 characters and must follow the SAP namespace convention (max. 3 characters prefix, SAP-approved) to avoid collisions between add-ons. Over Custom Values (Formatted Search) field contents can be automatically determined by mathematical or logical formulas and database references. UDFs automatically appear in the service layer metadata model and can therefore be addressed by integrations via REST.

Demarcation

A UDF extends an existing object with additional fields – it does not create a new object. If a new standalone table is needed, a UDT to use (User Defined Table); if this table is to function like a genuine business object with its own interface, event control, and document behaviour, then a UDO (User Defined Object) necessary. UDFs are also not UDQ- Queries or Formatted Searches themselves — they are data containers that can be populated by Formatted Searches.


AI in everyday work: Person starts with their own task instead of the learning pile

AI in everyday work: Here's how to find the right start

Anyone who wants to use AI in their daily work is familiar with this: You read an article about prompts. A new model appears in it ...
AI-SHOP

AI assistant meets SAP Business One: Two paths out of the Versino AI shop

AI assistants like Claude or Copilot write emails, compile documents, and explain technical terms. But when you ask them about the open-source code...
SPRINT & SWIRL

Sprint and Swirl: How an AI agent divides work and learns from trials

This series deals with artificial intelligence in conjunction with SAP Business One. It takes a close look at fundamental AI principles...
LATS

LATS: Considering several paths simultaneously with AI — and the availability check in SAP B1

This series focuses on artificial intelligence in conjunction with SAP Business One. Not as a collection of product announcements, but as...
ReAct and RLEF

ReAct and RLEF: How Artificial Intelligence Learns from Real Mistakes — and What Automated Bank Reconciliation in SAP Business One Has to Do with It

This is the fourth instalment in a series on this blog dealing with AI fundamentals in conjunction with SAP Business One...
Service Layer AI as a transactional layer

SAP B1 10.0 FP2608: Service Layer AI as a transactional layer

The SAP Business One Service Layer has previously served predominantly as a passive data provider: applications requested data via OData, each ...
Wird geladen …