SAP HANDLER METH PRECHECK ABAP Statements

Get Example source ABAP code based on a different SAP table
  ABAP Statement

• FOR PRECHECK METHODS
• FOR CREATE FOR PRECHECK
• FOR UPDATE FOR PRECHECK
• FOR DELETE FOR PRECHECK
• FOR ACTION FOR PRECHECK
• REQUEST FOR PRECHECK

FOR PRECHECK, RAP Handler Method

ABAP_SYNTAX
Handler method definitions:
METHODS meth $[ FINAL$]
FOR PRECHECK
$[IMPORTING$] ${ REFERENCE(im_par_pre) $| im_par_pre $}
FOR ${ CREATE bdef $}
$| ${ CREATE bdef _assoc $}
$| ${ UPDATE bdef $}
$| ${ DELETE bdef $}
$| ${ ACTION bdef~action
$[REQUEST ${ REFERENCE (req_act_pre) $| req_act_pre $} $] $}
$[CHANGING ${ $[failed TYPE data$] $[reported TYPE data$] $}$].

ABAP_VARIANTS:
1 ... CREATE bdef ...
2 ... CREATE bdef _assoc ...
3 ... UPDATE ...
4 ... DELETE ...
5 ... ACTION bdef~action ...

ABAP Addition
1 ... REQUEST ...
2 ... CHANGING ...

What does it do?
Handler method that is used for the precheck. It must be defined and implemented in a handler class of an ABAP behavior pool. The method name meth can be chosen freely. bdef is the name or the alias of the BDEF, assoc the name of the association, and action the name of the action.
See the required BDEF notations in the following topic: RAP BDL - precheck.

ABAP_VARIANT_1 ... CREATE bdef ...

What does it do?
Handles the precheck for create operations.
Method parameters:

IMPORTING parameter:

im_par_pre: Includes the entities to be created. It is an internal table of type TYPE TABLE FOR CREATE bdef. The parameter can also be passed by reference (see REFERENCE).

CHANGING parameters: