FMFA_DI_MAINTAIN SAP Function module - FMFA: Functional Area Direct Input

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

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

Pattern for FM FMFA_DI_MAINTAIN - FMFA DI MAINTAIN

CALL FUNCTION 'FMFA_DI_MAINTAIN' "FMFA: Functional Area Direct Input
  EXPORTING
    i_fmfa_di =                 " fmfa_all_di_t  Functional Area. Direct Input All Data
*   i_xupdtask = SPACE          " boole-boole   In update task??
*   i_xcommit = 'X'             " boole-boole   Commit?
*   i_xbapi = SPACE             " boole-boole   Called from  BAPI?
*   i_xtest = SPACE             " boole-boole   Testrun (don't save)?
  IMPORTING
    e_xerror =                  " char1          error occured
    t_data =                    " fmmd_tab_bussdi  Tabellentyp: Direct Input Data
    t_message =                 " bus0msg1_t    Table Category for BUS0MSG1
    t_keyvalue =                " fmmd_tab_busskeyval  Tabellentyp: Schlüsselfeldwerte (Direct Input)
    .  "  FMFA_DI_MAINTAIN

ABAP code example for Function Module FMFA_DI_MAINTAIN

The ABAP code below is a full code listing to execute function module FMFA_DI_MAINTAIN 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_e_xerror  
 
 TYPE CHAR1
,
ld_t_data  
 
 TYPE FMMD_TAB_BUSSDI
,
ld_t_message  
 
 TYPE BUS0MSG1_T
,
ld_t_keyvalue  
 
 TYPE FMMD_TAB_BUSSKEYVAL
.


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


DATA(ld_i_xupdtask) = some text here


DATA(ld_i_xcommit) = some text here


DATA(ld_i_xbapi) = some text here


DATA(ld_i_xtest) = some text here
.

CALL FUNCTION 'FMFA_DI_MAINTAIN'
  EXPORTING
    i_fmfa_di =                  ld_i_fmfa_di
*   i_xupdtask =                 ld_i_xupdtask
*   i_xcommit =                  ld_i_xcommit
*   i_xbapi =                    ld_i_xbapi
*   i_xtest =                    ld_i_xtest
  IMPORTING
    e_xerror =                   ld_e_xerror
    t_data =                     ld_t_data
    t_message =                  ld_t_message
    t_keyvalue =                 ld_t_keyvalue
    .  "  FMFA_DI_MAINTAIN

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_e_xerror
 
 TYPE CHAR1 ,
ld_i_fmfa_di
 
 TYPE FMFA_ALL_DI_T ,
ld_t_data
 
 TYPE FMMD_TAB_BUSSDI ,
ld_i_xupdtask
 
 TYPE BOOLE-BOOLE ,
ld_t_message
 
 TYPE BUS0MSG1_T ,
ld_i_xcommit
 
 TYPE BOOLE-BOOLE ,
ld_t_keyvalue
 
 TYPE FMMD_TAB_BUSSKEYVAL ,
ld_i_xbapi
 
 TYPE BOOLE-BOOLE ,
ld_i_xtest
 
 TYPE BOOLE-BOOLE .


ld_i_fmfa_di = 'Check type of data required'.

ld_i_xupdtask = some text here

ld_i_xcommit = some text here

ld_i_xbapi = some text here

ld_i_xtest = some text here