BRF_MAINTAIN_ACTIONS SAP Function module

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

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

Pattern for FM BRF_MAINTAIN_ACTIONS - BRF MAINTAIN ACTIONS

CALL FUNCTION 'BRF_MAINTAIN_ACTIONS' "
* EXPORTING
*   iv_edit_mode = 3            " brf_edit_mode  BRF: Processing Type (Display, Change, Create ...)
*   iv_applclass =              " brf_applclass  BRF: Application Class
*   iv_action =                 " brf_action    BRF: Action
*   iv_import_status = 'A'      " brf_import_status  BRF: Import Status
*   iv_version = 0              " brf_version   BRF: Version
*   iv_langu = SY-LANGU         " sylangu       SAP R/3 System, Current Language
*   iv_obj_group = SPACE        " brf_obj_group  BRF: Grouping of BRF Objects
*   iv_skip_entry_screen = SPACE  " brf_boole_d  Skip Initial Screen if Possible
*   iv_return_if_error = SPACE  " brf_boole_d   Change/Display: Cancel Processing if Nothing Found
*   iv_wb_mode = '~'            " brf_boole_d   Called in Workbench Mode
*   iv_called_from_wb = SPACE   " brf_boole_d   Call from Workbench
*   iv_hide4delete_entry_screen =   " brf_boole_d  BRF: Space = False, 'X' = True
* TABLES
*   et_message =                " brf_message   BRF: Message
  EXCEPTIONS
    MESSAGE_OCCURED = 1         "               Message Occurred in Processing
    .  "  BRF_MAINTAIN_ACTIONS

ABAP code example for Function Module BRF_MAINTAIN_ACTIONS

The ABAP code below is a full code listing to execute function module BRF_MAINTAIN_ACTIONS 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_et_message  
 
 TYPE STANDARD TABLE OF BRF_MESSAGE,"TABLES PARAM
wa_et_message
 
 LIKE LINE OF it_et_message
.


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

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

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

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

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

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

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

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

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

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

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

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

"populate fields of struture and append to itab
append wa_et_message to it_et_message.
.

CALL FUNCTION 'BRF_MAINTAIN_ACTIONS'
* EXPORTING
*   iv_edit_mode =               ld_iv_edit_mode
*   iv_applclass =               ld_iv_applclass
*   iv_action =                  ld_iv_action
*   iv_import_status =           ld_iv_import_status
*   iv_version =                 ld_iv_version
*   iv_langu =                   ld_iv_langu
*   iv_obj_group =               ld_iv_obj_group
*   iv_skip_entry_screen =       ld_iv_skip_entry_screen
*   iv_return_if_error =         ld_iv_return_if_error
*   iv_wb_mode =                 ld_iv_wb_mode
*   iv_called_from_wb =          ld_iv_called_from_wb
*   iv_hide4delete_entry_screen =    ld_iv_hide4delete_entry_screen
* TABLES
*   et_message =                 it_et_message
  EXCEPTIONS
    MESSAGE_OCCURED =            1
    .  "  BRF_MAINTAIN_ACTIONS

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_iv_edit_mode
 
 TYPE BRF_EDIT_MODE ,
it_et_message
 
 TYPE STANDARD TABLE OF BRF_MESSAGE ,
wa_et_message
 
 LIKE LINE OF it_et_message,
ld_iv_applclass
 
 TYPE BRF_APPLCLASS ,
ld_iv_action
 
 TYPE BRF_ACTION ,
ld_iv_import_status
 
 TYPE BRF_IMPORT_STATUS ,
ld_iv_version
 
 TYPE BRF_VERSION ,
ld_iv_langu
 
 TYPE SYLANGU ,
ld_iv_obj_group
 
 TYPE BRF_OBJ_GROUP ,
ld_iv_skip_entry_screen
 
 TYPE BRF_BOOLE_D ,
ld_iv_return_if_error
 
 TYPE BRF_BOOLE_D ,
ld_iv_wb_mode
 
 TYPE BRF_BOOLE_D ,
ld_iv_called_from_wb
 
 TYPE BRF_BOOLE_D ,
ld_iv_hide4delete_entry_screen
 
 TYPE BRF_BOOLE_D .


ld_iv_edit_mode = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_message to it_et_message.
ld_iv_applclass = 'Check type of data required'.
ld_iv_action = 'Check type of data required'.
ld_iv_import_status = 'Check type of data required'.
ld_iv_version = 'Check type of data required'.
ld_iv_langu = 'Check type of data required'.
ld_iv_obj_group = 'Check type of data required'.
ld_iv_skip_entry_screen = 'Check type of data required'.
ld_iv_return_if_error = 'Check type of data required'.
ld_iv_wb_mode = 'Check type of data required'.
ld_iv_called_from_wb = 'Check type of data required'.
ld_iv_hide4delete_entry_screen = 'Check type of data required'.