Business Object (RAP BO)
What it is
In RAP, the self-contained transactional entity: a root CDS entity (optionally with child entities via compositions) plus its behavior. It owns its data, behavior, draft state and authorisation as one unit.
Why it matters for Clean Core
Thinking in business objects instead of tables is the mental shift RAP demands. The BO is the consistency boundary — you change data through its behavior (EML / actions), never by writing to the underlying tables.
Common pitfall
Modelling a BO as a thin wrapper over a single table and then still UPDATE-ing the table directly elsewhere. Once it's a BO, the BO is the only writer. Side writes corrupt draft state and skip your validations.