SAP Function Modules

FM17_ACTIVITY_ALLOWED_GET SAP Function module







FM17_ACTIVITY_ALLOWED_GET 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 FM17_ACTIVITY_ALLOWED_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FM17
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FM17_ACTIVITY_ALLOWED_GET - FM17 ACTIVITY ALLOWED GET





CALL FUNCTION 'FM17_ACTIVITY_ALLOWED_GET' "
  EXPORTING
    i_fikrs =                   " fmbudvers-fikrs
*   i_gjahr =                   " fmbudvers-gjahr
*   i_geber = SPACE             " fmbudvers-geber
*   i_versn =                   " fmbudvers-versn
*   i_activity =                " bpbu_act_allowed-activity
*   i_flg_com_bud =             "
*   i_flg_pay_bud =             "
* TABLES
*   t_act_tab =                 " bpbu_t_act_allowed
  EXCEPTIONS
    NOT_ALLOWED = 1             "
    .  "  FM17_ACTIVITY_ALLOWED_GET

ABAP code example for Function Module FM17_ACTIVITY_ALLOWED_GET





The ABAP code below is a full code listing to execute function module FM17_ACTIVITY_ALLOWED_GET 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:
it_t_act_tab  TYPE STANDARD TABLE OF BPBU_T_ACT_ALLOWED,"TABLES PARAM
wa_t_act_tab  LIKE LINE OF it_t_act_tab .


SELECT single FIKRS
FROM FMBUDVERS
INTO @DATA(ld_i_fikrs).


SELECT single GJAHR
FROM FMBUDVERS
INTO @DATA(ld_i_gjahr).


SELECT single GEBER
FROM FMBUDVERS
INTO @DATA(ld_i_geber).


SELECT single VERSN
FROM FMBUDVERS
INTO @DATA(ld_i_versn).


DATA(ld_i_activity) = some text here
DATA(ld_i_flg_com_bud) = 'some text here'.
DATA(ld_i_flg_pay_bud) = 'some text here'.

"populate fields of struture and append to itab
append wa_t_act_tab to it_t_act_tab. . CALL FUNCTION 'FM17_ACTIVITY_ALLOWED_GET' EXPORTING i_fikrs = ld_i_fikrs * i_gjahr = ld_i_gjahr * i_geber = ld_i_geber * i_versn = ld_i_versn * i_activity = ld_i_activity * i_flg_com_bud = ld_i_flg_com_bud * i_flg_pay_bud = ld_i_flg_pay_bud * TABLES * t_act_tab = it_t_act_tab EXCEPTIONS NOT_ALLOWED = 1 . " FM17_ACTIVITY_ALLOWED_GET
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "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_i_fikrs  TYPE FMBUDVERS-FIKRS ,
it_t_act_tab  TYPE STANDARD TABLE OF BPBU_T_ACT_ALLOWED ,
wa_t_act_tab  LIKE LINE OF it_t_act_tab,
ld_i_gjahr  TYPE FMBUDVERS-GJAHR ,
ld_i_geber  TYPE FMBUDVERS-GEBER ,
ld_i_versn  TYPE FMBUDVERS-VERSN ,
ld_i_activity  TYPE BPBU_ACT_ALLOWED-ACTIVITY ,
ld_i_flg_com_bud  TYPE STRING ,
ld_i_flg_pay_bud  TYPE STRING .


SELECT single FIKRS
FROM FMBUDVERS
INTO ld_i_fikrs.


"populate fields of struture and append to itab
append wa_t_act_tab to it_t_act_tab.

SELECT single GJAHR
FROM FMBUDVERS
INTO ld_i_gjahr.


SELECT single GEBER
FROM FMBUDVERS
INTO ld_i_geber.


SELECT single VERSN
FROM FMBUDVERS
INTO ld_i_versn.


ld_i_activity = some text here
ld_i_flg_com_bud = 'some text here'.
ld_i_flg_pay_bud = 'some text here'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FM17_ACTIVITY_ALLOWED_GET or its description.