What are custom objects and why should you use them?

User Defined Objects (UDO) in SAP Business One are special extensions that allow you to create unique data structures. These can be customised to meet the specific needs of your company. These functions allow you to effectively manage and utilise data that is not covered by the software's standard objects.

User-defined objects in SAP Business One - Advantages

The use of UDOs offers numerous advantages, including

  1. integrationUDOs allow the seamless integration of additional data into the SAP system, enabling centralised data storage. This not only makes it easier to access and manage data, but also improves data integrity.
  2. CustomisationYou can customise SAP Business One to specific business processes without having to resort to costly and time-consuming individual software developments.
  3. automationUDOs can be used to further automate business processes, resulting in more efficient data processing and utilisation.
  4. flexibilityUDOs make it possible to fulfil specific business requirements that go beyond the standard functions of SAP Business One.
  5. CentralisationAll user-defined data and processes remain within the SAP system, which ensures the integrity and security of the data.
  6. Increased efficiencyBy automating additional business processes, companies can organise their workflows more efficiently.

Types of user-defined objects in SAP Business One

In SAP Business One, you can create two main types of user-defined objects:

  • base data-Types (Master Data Type)These are ideal for managing data that does not change frequently, such as customer data, item information or settings.
  • Document types (Document Type)They are suitable for managing transactional data such as orders or sales data that is regularly updated or changed.

Practical examples and their use

Creation of a master data type

A master data type can be used to manage warehouse locations, for example. In SAP Business One, you could create a customised object that stores not only the location details, but also specific information such as measurement values or security levels.

Use of a document type

A document type could also be used to manage special sales processes. For example, you could create a UDO that includes special terms of sale, customer specifications or delivery terms that are not available in the standard sales documents.

    Example: Accessories

    A practical example of the use of UDO is the implementation of an accessory item system. This involves creating a relationship between items, such as between a computer and its accessories like a mouse and keyboard. This differs from the alternative items available in SAP Business One in that it defines a specific relationship between the products that meets the requirements of the business.

    Application example: Management of accessory items

    Two tables are required to manage accessory items - one for the main item and one for the accessory items. The main article is identified by the article number, while the accessory articles also specify the required quantity. This structure makes it possible to efficiently define and manage accessories for main products.

    Steps for creating a UDO in SAP Business One

    1. Definition of UDODefine which data the UDO should contain and decide whether it is a master data type or a document type.
    2. Use WizardSAP Business One offers a wizard for creating UDOs that guides you through the entire process and ensures that all necessary steps are covered.
    3. Assignment to menusAfter creating the UDO, you can integrate it into the main menu of SAP Business One to make it easier to access and use.
    4. data managementOnce the UDO has been created, you can start entering data and using the new object in your business processes.
    UDO - SAP Business One

    The object orientation of SAP Business One

    SAP Business One works object-orientated. Although all data is stored in a database, which in turn has table structures, the individual processes are divided into objects. An object is, for example, a quotation, an order or an article master data record. An object is hidden behind almost every main menu entry (except for the administration menu). The object is a kind of logical structure of the underlying data tables. In the simplest case, the information for an object is contained in just one table, but a large number of tables can also belong to a more complex object.

    Services in properties

    In addition to the data tables, an object also has predefined functions. These are referred to as services in SAP Business One. Classic examples of these services are Add Update Delete Search This allows an object to work completely independently in SAP Business One, as it has its unique data storage locations (tables) and its functions (services). A user-defined object inherits this behaviour (of the SAP Business One standard objects). It therefore behaves exactly like an existing object. It therefore extends the functionality of SAP Business One with the help of the existing services.
    Classic examples of these services are

    • Add
    • Update
    • Delete
    • Search