What does it do? Exactly one static factory action per RAP BO entity can be defined as default static factory action using the syntax addition default. The same rules apply as for factory actions, see topic TITLE . The addition default is evaluated by consuming frameworks, such as OData. These frameworks use the default factory action as standard action in certain scenarios. Possible RAP BO operation additions to default factory actions:
internal
features:global
precheck
authorization:none
ABAP Addition
InputParameter
ABAP_AVAILABILITY
Managed RAP BO
Unmanaged RAP BO
For projection BOs, the following rules apply:
The default factory action from the base BDEF can be reused. For details on reuse, see topic TITLE .
It is also possible to specify a new default factory action in the projection layer.
If the default factory action from the base BO is reused, and at the same time, a new default factory action is defined in the projection BDEF, the default factory from the projection is considered to be the default. It overwrites the default factory action from the base BDEF.
Further details on actions and functions in projection BDEFs are described in topic RAP BDL - Actions and Functions. ABAP_AVAILABILITY_END
ABAP_RESTRICTION The specification of default factory actions in a BDEF extension is not allowed. ABAP_RESTR_END
ABAP_EXAMPLE_VX5 The following example shows a managed BDEF which defines a static default factory action: BDEF DEMO_RAP_DEFAULT_FACTORY_A The projection BDEF reuses the static default factory action from the base BDEF and specifies a new static default factory action. Consuming frameworks consider the static default factory action from the projection BDEF as default. BDEF DEMO_RAP_DFA_PV ABAP_EXAMPLE_END
