S_FOBU_METHOD_ACCESS_CALL SAP Function module

S_FOBU_METHOD_ACCESS_CALL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name S_FOBU_METHOD_ACCESS_CALL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: S_FOBU_METHODS_DB
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM S_FOBU_METHOD_ACCESS_CALL - S FOBU METHOD ACCESS CALL

CALL FUNCTION 'S_FOBU_METHOD_ACCESS_CALL' "
  EXPORTING
    class_name =                " seoclsname    Object Type Name
*   interface_name = SPACE      " seoitfname    Interface Name
    method_name =               " seocmpname    Component Name
*   extension = SPACE           " sfbmextens    Key Enhancement for Formula Builder Methods
    mode = '03'                 " activ_auth
* CHANGING
*   transport_request =         " trkorr        Request/Task
  EXCEPTIONS
    NOT_FOUND = 1               "
    ALREADY_EXISTS = 2          "
    NO_ACCESS = 3               "
    SHOW_ONLY = 4               "
    .  "  S_FOBU_METHOD_ACCESS_CALL

ABAP code example for Function Module S_FOBU_METHOD_ACCESS_CALL

The ABAP code below is a full code listing to execute function module S_FOBU_METHOD_ACCESS_CALL including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA(ld_transport_request) = 'Check type of data required'.

DATA(ld_class_name) = 'Check type of data required'.

DATA(ld_interface_name) = 'Check type of data required'.

DATA(ld_method_name) = 'Check type of data required'.

DATA(ld_extension) = 'Check type of data required'.

DATA(ld_mode) = 'Check type of data required'.
.

CALL FUNCTION 'S_FOBU_METHOD_ACCESS_CALL'
  EXPORTING
    class_name =                 ld_class_name
*   interface_name =             ld_interface_name
    method_name =                ld_method_name
*   extension =                  ld_extension
    mode =                       ld_mode
* CHANGING
*   transport_request =          ld_transport_request
  EXCEPTIONS
    NOT_FOUND =                  1
    ALREADY_EXISTS =             2
    NO_ACCESS =                  3
    SHOW_ONLY =                  4
    .  "  S_FOBU_METHOD_ACCESS_CALL

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_transport_request
 
 TYPE TRKORR ,
ld_class_name
 
 TYPE SEOCLSNAME ,
ld_interface_name
 
 TYPE SEOITFNAME ,
ld_method_name
 
 TYPE SEOCMPNAME ,
ld_extension
 
 TYPE SFBMEXTENS ,
ld_mode
 
 TYPE ACTIV_AUTH .


ld_transport_request = 'Check type of data required'.
ld_class_name = 'Check type of data required'.
ld_interface_name = 'Check type of data required'.
ld_method_name = 'Check type of data required'.
ld_extension = 'Check type of data required'.
ld_mode = 'Check type of data required'.