What does it do? This topic gives an overview of the entity behavior characteristics that can be reused in a projection BDEF . It also explains which ones of the behavior characteristics from the projected BO are automatically reused or inherited. These characteristics does not need to be specified explicitly. Characteristics that must be specified explicitly, if required:
use etag An ETag field for optimistic concurrency control can be reused if it is specified in the base BO.
For details on optimistic concurrency control, see topic TITLE .
For details on reuse, see topic TITLE .
extensible To enable BDEF extensions, a declaration in the entity behavior definition header is required and the keyword extensible must also be declared in the entity behavior characteristics for each individual entity that allows BDEF extensions. In projection BDEFs, only the keyword extensible is possible, without any further additions. For details, see topic TITLE . Characteristic that can be specified explicitly or reused, depending on the context:
authorization
All authorization controls that are specified in the base BO is automatically and implicitly passed on to the projection BO. For details, see topic TITLE .
If new actions are specified in a projection BDEF, it is possible to specify authorization control for these new actions in the projection layer. For details, see topic TITLE . Automatic reuse and/or inheriting:
persistent table Implementation aspect that is reused automatically.
draft table Implementation aspect that is reused automatically.
saving options Implementation aspect that is reused automatically.
locking Implementation aspect that is reused automatically. Projection BOs inherit the lock master and lock dependent relations. On each modify operation on a projection BO instance, the method FOR LOCK is called and the respective entities are locked.
early numbering Implementation aspect that is reused automatically.
late numbering Implementation aspect that is reused automatically.
