Get Example source ABAP code based on a different SAP table
• FOR INSTANCE FEATURES METHODS • FOR FEATURES METHODS • REQUEST FOR FEATURES • RESULT FOR FEATURES
FOR INSTANCE FEATURES, FEATURES>, RAP Handler Method
ABAP_SYNTAX Handler method definition:> METHODS> meth $[ FINAL>$] FOR $[INSTANCE$] FEATURES $[IMPORTING>>$] ${ REFERENCE>> (im_par_feat) $| im_par_feat $} REQUEST ${ REFERENCE>>(req_feat) $| req_feat $} FOR bdef RESULT ${ REFERENCE>> (res_feat) $| res_feat $} $[CHANGING>> ${ $[failed> TYPE data>>$] $[reported> TYPE data>>$] $}$] .>
What does it do? Handler method > that is used for the instance-based feature control>. 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>. The ABAP word INSTANCE> is optional.
Method Parameters
IMPORTING> > parameters:
im_par_feat>: Internal table of type TYPE TABLE FOR INSTANCE FEATURES KEY>>.
The importing parameter can also be passed by reference (see REFERENCE>>). The use of the ABAP word IMPORTING > is optional.
req_feat>: Request parameter on which the information retrieval for instance-based feature control is based on. It is a structure of type TYPE STRUCTURE FOR INSTANCE FEATURES REQUEST>>. The parameter can also be passed by reference.
CHANGING>> parameters:
res_feat>: Used to store the result of the information retrieval. It is an internal table of type TYPE TABLE FOR INSTANCE FEATURES RESULT>>. The parameter can also be passed by reference.