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