behaviour definition – SAP EWM Help

Why strict ( 2 ) is used in Behaviour definition

DPM125 — Thu, 07 Aug 2025 08:55:20 +0000

In SAP RAP (RESTful Application Programming Model), the strict ( 2 ) keyword in a behavior definition plays a crucial role in enforcing stricter syntax and semantics for RAP BO development.

define behavior for ZI_MY_VIEW
strict ( 2 )
…

strict ( 2 ) activates the strict mode version 2, which enforces stronger design-time checks and stricter rules to help ensure the RAP application is upgrade-stable, future-proof, and consistent.

What strict ( 2 ) Does

Here are the key restrictions/enforcements introduced by strict ( 2 ):

1. No Implicit Features

You must explicitly declare everything. RAP will not assume default behavior.

E.g., actions, fields, operations must be explicitly defined.

2. Field Control Must Be Explicit

Fields must be explicitly declared for update, mandatory, readonly, etc.

field ( update ) my_field;

3. No Implicit Save

There is no automatic save of changes — save logic must be handled explicitly in the implementation class.

4. Cleaner Contract

The behavior is more predictable, meaning the framework won’t “guess” developer intent. This leads to better maintainability.

5. Future Compatibility

SAP intends to make strict ( 2 ) the standard mode going forward. Using it now ensures you’re aligned with the long-term RAP roadmap.

Behaviour Definition in SAP RAP

DPM125 — Tue, 05 Aug 2025 19:08:06 +0000

It is a file (with .behavior extension) that specifies the business behavior of an entity (CDS view), and it controls:

Which operations are allowed
Which fields are modifiable
Which validations or determinations are triggered
Custom logic, like actions

Key Purposes of Behavior Definition

Function	Description
Enable CRUD operations	Define if `create`, `update`, `delete` are allowed
Locking	Prevent data conflicts in multi-user scenarios
Draft Support	Support for draft-enabled objects (save without activation)
Field Control	Mark fields as read-only, mandatory, etc.
Validation/Determination	Attach logic to auto-fill or validate fields
Actions	Define custom operations like `Submit`, `Approve`, etc.

unmanaged implementation in class ZBP_SalesOrder unique;

define behavior for ZI_SalesOrder
persistent table zsalesorder
lock master
{
  create;
  update;
  delete;

  field ( readonly ) CreatedBy, CreatedAt;
  field ( mandatory ) CustomerID;

  action SubmitOrder result [1] $self;
}

Types of Implementation

Type	Description
Managed	SAP manages most logic automatically
Unmanaged	You write full logic in ABAP classes

Early Numbering in RAP

DPM125 — Thu, 31 Jul 2025 15:51:21 +0000

In SAP RAP (RESTful ABAP Programming Model), Early Numbering refers to assigning the key (e.g., ID or number) of a new business object at creation time, before the record is persisted to the database.

Follow the below code to implement early numbering.

Output after clicking the save button.