It is mandatory to provide at least one trigger condition within the curly brackets.

 

The following trigger conditions are supported:

Create;

Determination is executed when an instance is created.

 

Update;

Determination is executed when an instance is updated.

 

Delete;

Determination is executed when an instance is deleted.

 

Field<field1>, <field2>, …;

Determination is executed when the value of one of the specified fields is changed by a create or update operation.

 

Multiple trigger conditions can be combined.

 

The behavior definition in the example defines one determination. It is executed during the modify phase, and it is triggered by the create; operation alone. It is not triggered during update; operations on existing entity instances.

 

Determination Implementation

Creating the Determination Handler Method

 

If the behavior definition already contains the determination definition, the quick fix for creating the behavior pool will automatically create the determination implementation method in the local handler class.

 

If the behavior pool already exists when you add the determination definition, you can use a quick fix to add the missing method to the local handler class. To invoke the quick fix, place the cursor on the name of the determination and press Ctrl + 1.

 

Implementing the Determination Handler Method

 

The implementation of a determination is contained in a local handler class as part of the behavior pool. This local class inherits from the base handler class CL_ABAP_BEHAVIOR_HANDLER.

 

The signature of a determination method is typed using the keyword FOR DETERMINE followed by the chosen determination time and the import parameter. The type of the importing parameter is an internal table containing the keys of the instances the determination will be executed on.

 

Although not visible in the method definition, all determination handler methods have a response parameter reported which allows you to report messages in the determination implementation.

 

The actual changes to the node instances are performed using the EML statement MODIFY ENTITY or MODIFY ENTITIES, based on the keys in importing parameter keys.