FM_FUNC_AREA_CREATE_RFC SAP Function module - Create Functional Area

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

Associated Function Group: FM_FUNCTIONAL_AREA_RFC
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM FM_FUNC_AREA_CREATE_RFC - FM FUNC AREA CREATE RFC

CALL FUNCTION 'FM_FUNC_AREA_CREATE_RFC' "Create Functional Area
  EXPORTING
    i_func_area =               " fkber
    is_func_area_data =         " fmfa_tfkb_di
    is_func_area_text =         " fmfa_tfkbt_di
*   i_flg_testrun = 'X'         " testrun       Umschalten auf Simulations-Modus bei schreibenden BAPIs
*   i_flg_commit = ' '          " xflag         Commit durchführen ?
  IMPORTING
    et_messages =               " bapiret2_t
    .  "  FM_FUNC_AREA_CREATE_RFC

ABAP code example for Function Module FM_FUNC_AREA_CREATE_RFC

The ABAP code below is a full code listing to execute function module FM_FUNC_AREA_CREATE_RFC 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_et_messages  
 
 TYPE BAPIRET2_T
.


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

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

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

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

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

CALL FUNCTION 'FM_FUNC_AREA_CREATE_RFC'
  EXPORTING
    i_func_area =                ld_i_func_area
    is_func_area_data =          ld_is_func_area_data
    is_func_area_text =          ld_is_func_area_text
*   i_flg_testrun =              ld_i_flg_testrun
*   i_flg_commit =               ld_i_flg_commit
  IMPORTING
    et_messages =                ld_et_messages
    .  "  FM_FUNC_AREA_CREATE_RFC

IF SY-SUBRC EQ 0.
  "All OK
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_et_messages
 
 TYPE BAPIRET2_T ,
ld_i_func_area
 
 TYPE FKBER ,
ld_is_func_area_data
 
 TYPE FMFA_TFKB_DI ,
ld_is_func_area_text
 
 TYPE FMFA_TFKBT_DI ,
ld_i_flg_testrun
 
 TYPE TESTRUN ,
ld_i_flg_commit
 
 TYPE XFLAG .


ld_i_func_area = 'Check type of data required'.
ld_is_func_area_data = 'Check type of data required'.
ld_is_func_area_text = 'Check type of data required'.
ld_i_flg_testrun = 'Check type of data required'.
ld_i_flg_commit = 'Check type of data required'.