Model a business transition as an action

Approval is a named business operation, not just permission to set Status = 'APPROVED'. An action gives the BO a place to validate preconditions, record an approver, and report a meaningful result.

Declare the operation

action approve result [1] $self;

The declaration belongs in the BDEF body; the implementation is written in the behavior pool. A consumer invokes the action through EML and handles its result and response tables. The exact action parameter and result types must fit the business contract.

Use an action when the operation represents behavior beyond generic CRUD. Do not model every field assignment as a custom action; standard update may be clearer for a simple editable field. Authorization and feature control still need deliberate design.

Sources

• SAP Samples: RAP actions in EML and behavior definitions
• ABAP Keyword Documentation: RAP actions

action approve result [1] $self;