Ansicht
Dokumentation
ABAPHANDLER_METH_PRECHECK - HANDLER METH PRECHECK
Fill RESBD Structure from EBP Component Structure TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
FOR PRECHECK
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$] $}$].
Variants:
1. ... CREATE bdef ...
2. ... CREATE bdef\_assoc ...
3. ... UPDATE ...
4. ... DELETE ...
5. ... ACTION bdef~action ...
Additions
1. ... REQUEST ...
2. ... CHANGING ...
Effect
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: CDS BDL - precheck.
Variant 1
... CREATE bdef ...
Effect
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:
- failed and reported are implicit changing parameters that return information. See the details in section ... CHANGING....
Variant 2
... CREATE bdef\_assoc ...
Effect
Handles the precheck for create-by-association 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\_assoc. The parameter can also be passed by reference (see REFERENCE).
- CHANGING parameters:
- failed and reported are implicit changing parameters that return information. See the details in section ... CHANGING....
Variant 3
... UPDATE bdef ...
Effect
Handles the precheck for update operations.
Method parameters:
- IMPORTING parameter:
- im_par_pre: Includes the entities to be updated. It is an internal table of type TYPE TABLE FOR UPDATE bdef. The parameter can also be passed by reference (see REFERENCE).
- CHANGING parameters:
- failed and reported are implicit changing parameters that return information. See the details in section ... CHANGING....
Variant 4
... DELETE bdef ...
Effect
Handles the precheck for delete operations.
Method parameters:
- IMPORTING parameter:
- im_par_pre: Includes the keys of the entities to be deleted. It is an internal table of type TYPE TABLE FOR DELETE bdef. The parameter can also be passed by reference (see REFERENCE).
- CHANGING parameters:
- failed and reported are implicit changing parameters that return information. See the details in section ... CHANGING....
Variant 5
... ACTION bdef~action ...
Effect
Handles the precheck for actions.
Method parameters:
- IMPORTING parameter:
- im_par_pre: Includes the keys of the entities for which the action should be processed. It is an internal table of type TYPE TABLE FOR ACTION IMPORT bdef~action. The parameter can also be passed by reference (see REFERENCE).
- CHANGING parameters:
- failed and reported are implicit changing parameters that return information. See the details in section ... CHANGING....
Addition 1
... REQUEST ...
Effect
The addition and the parameter req_act_pre are only available in the context of actions that are specified with a parameter in the BDEF.
req_act_pre is an importing parameter and specifies Request parameter on which the information
retrieval ... is based on. It is a structure of type TYPE STRUCTURE FOR ACTION REQUEST bdef.
Addition 2
... CHANGING ...
Effect
The CHANGING parameters failed
and reported are implicitly
available. They are used to return information on failures or messages respectively. It is possible
to specify the parameters with the predefined names failed and reported explicitly following
the ABAP word CHANGING. In this case, the generic type DATA
is used. At runtime, the typed parameters implicitly have the BDEF derived type TYPE RESPONSE FOR.
Example
Examples for RAP handler method definitions. Find demonstrations of method implementations in the executable examples further down.
METHODS precheck_create FOR PRECHECK
IMPORTING entities FOR CREATE bdef.
METHODS precheck_cba_assoc FOR PRECHECK
IMPORTING entities_cba FOR CREATE bdef\_assoc.
METHODS precheck_update FOR PRECHECK
IMPORTING entities FOR UPDATE bdef.
METHODS precheck_delete FOR PRECHECK
IMPORTING keys FOR DELETE bdef.
METHODS precheck_action FOR PRECHECK
IMPORTING entities FOR CREATE bdef~action.
Example for RAP Handler Methods: Demonstrates this RAP handler method for an action within a RAP handler class using a simple unmanaged RAP BO that is draft-enabled.
BAL Application Log Documentation Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 12107 Date: 20240419 Time: 021954 sap01-206 ( 170 ms )