A Businessobjekt is the entity for things your ERP manages: customer, article, order, quote, delivery address. On Nuclos 5 this is not a database table you maintain beside the system. It is metadata: attributes, types, required fields, defaults, and references belong to the model. Masks, subforms, state models, and rules hang on it. For decision-makers: the Businessobjekt is the anchor where process and data meet.

What a Businessobjekt delivers in business terms

Without clear entities, ERP falls apart into lists and spreadsheet side worlds. The Businessobjekt makes the business subject explicit. An order is not “a row somewhere”, but an object with attributes, relationships, and a lifecycle. From that come masks for entry, overviews for control, and workflows for status change.

That fits process structure instead of module structure: you model the subject of the flow, not a license package. Platform depth: Nuclos 5 as a platform. The Businessobjekt lives in the Nuclet, which keeps your business application separate from the core.

Attributes, types, and references

Every Businessobjekt carries attributes. Typical are type (text, number, date, boolean, and more), required flag, default values, and references to other Businessobjekte. That builds the relationship net: order references customer, line references article. This is low-code data modelling: changes stay maintainable and documentable in the metadata model.

For IT and configuration: references are to be steered, not patched later by script. For business units: required and default reduce misuse before rules fire. Anyone who leaves attributes and relationships unclear digitalises chaos. Anyone who fixes them early keeps scope and mask building plannable.

Menu path and visibility

The menu path controls where the Businessobjekt appears in the application. Without a sensible path the entity is technically there but invisible or mis-sorted for users. Menu structure is part of process guidance: what is used often must be reachable quickly. What is rare does not belong on the first navigation level.

Together with mask and layout and subform that yields the work surface: object, fields, related lists, navigation.

Nuclosian and Businessobjekte

Nuclosian creates and extends Businessobjekte. In config mode you describe in business language what should be managed. Nuclosian writes attributes, references, and settings directly into the instance. There is no diff for that. That does not replace process clarification. It shortens the path from business statement to model. Entry points and names: Nuclosian: first steps.

Technical reference: Businessobjekt in the Nuclos wiki. Configuration detail lives there. Here the buyer answer: the Businessobjekt is the entity your individual ERP hangs on.

What a Businessobjekt is not

A Businessobjekt is not a report, not an Excel import, and not a free-floating form without a model. It is also not a substitute for state model or rules engine. Lifecycle sits on the state model. Special logic that mask and state do not cover sits in rules. The Businessobjekt remains the shared anchor. Anyone who only displays data does not need a full model. Anyone who steers processes does.