23 apr

UDO (SAP Business One)


E-invoicing in Germany: How to implement the obligation with SAP Business One

UDO stands for User Defined Object, in German Custom object. A UDO lifts a UDT (User-defined table) to the level of a fully-fledged business object: with its own interface, standard functions such as search/create/change, registration in menu structures, authorisation system, events and integration with DI API as well as Service Layer.

Context

When defining a UDO, the developer chooses between the two object types udo_MasterData (Master Data, like a master data record – Type 1) and udo_Document (documents, as a document with header and lines — Type 3). The UDO includes a master table (Master-Data: single UDT; Document: UDT + line UDT) and optionally a linked number series. In the UI API, there are dedicated default forms and the UDOEvent- An object that is triggered, for example, when opening a new UDO form with a header-line layout. In practice, the UDO concept is used by many add-ons — Versino Financial Suite, Coresuite extensions, or MariProject encapsulate industry-specific documents (e.g. DATEV export configurations, travel expense reports, project documents) via this, which act like native SAP B1 documents but carry their own logic.

Demarcation

An UDO is not identical to a UDT: The UDT is the storage layer, the UDO adds behaviour., UI, events, and API visibility. It's also not the same as simply extending a standard object via UDFs – UDFs attach to existing objects, UDOs are standalone objects. Compared to a classic add on- Forms with self-contained tables offer the UDO the advantage of automatically utilising standard SAP B1 mechanisms (authorisations, approval process, document flow, Service Layer endpoint); the disadvantage is a stronger dependency on the B1 framework and its limitations, such as in the UI freedom of the forms.


Process Reward Model

Process Reward Models: Why a correct result does not yet prove a correct method

This series continuously examines individual AI basic terms and methods such as the Process Reward Model. The previous episode has ...
Test-Time-Compute-Scaling

Test-Time Compute Scaling: Why a Smaller AI Model Can End Up Winning — and What Supplier Comparison in SAP Business One Has to Do With It

This is a continuation of the series on this blog, which deals with Artificial Intelligence in combination with SAP Business One...
RLHF

RLHF and reward models: The reality behind the AI hype — and what the approval process in SAP Business One has to do with it

Key takeaways: The article covers the application of artificial intelligence in the context of SAP Business One and fundamental AI topics. Thanks to ...
AI Webinar

AI – Answers from SAP Business One – without SQL, without IT ticket

Live webinar on 30 July 2026, 14:00–14:30 | Live demo via Microsoft Teams | Duration: 30 minutes „How were the sales...".
Generative AI in ERP

AI in ERP – but under control: What Versino AI means for SAP Business One users

AI can do a lot today – but without control, it often creates more problems than it solves. Versino AI connects AI models...
Humans and AI

SAP KI Vision: The Autonomous Enterprise

Hardly a week goes by without the announcement of more intelligent language models, new co-pilots or more powerful AI agents. Nevertheless, SAP CEO Christian Klein states in...
Wird geladen …