BANK_OBJ_WORKL_MODIFY_BUFFER SAP Function module

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

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

Pattern for FM BANK_OBJ_WORKL_MODIFY_BUFFER - BANK OBJ WORKL MODIFY BUFFER

CALL FUNCTION 'BANK_OBJ_WORKL_MODIFY_BUFFER' "
  EXPORTING
    i_tab_modify =              " bank_tab_pp_status_change  Transfer Data for Status Change of Objects
    i_flg_perform_db_changes =   " xfeld
    i_ref_logger =              " if_bank_pp_logger
  IMPORTING
    e_tab_success =             " bank_tab_pp_status_change
  EXCEPTIONS
    NO_CURRENT_WORKLIST = 1     "
    INTERNAL_ERROR = 2          "
    .  "  BANK_OBJ_WORKL_MODIFY_BUFFER

ABAP code example for Function Module BANK_OBJ_WORKL_MODIFY_BUFFER

The ABAP code below is a full code listing to execute function module BANK_OBJ_WORKL_MODIFY_BUFFER 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_tab_success  
 
 TYPE BANK_TAB_PP_STATUS_CHANGE
.


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

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

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

CALL FUNCTION 'BANK_OBJ_WORKL_MODIFY_BUFFER'
  EXPORTING
    i_tab_modify =               ld_i_tab_modify
    i_flg_perform_db_changes =    ld_i_flg_perform_db_changes
    i_ref_logger =               ld_i_ref_logger
  IMPORTING
    e_tab_success =              ld_e_tab_success
  EXCEPTIONS
    NO_CURRENT_WORKLIST =        1
    INTERNAL_ERROR =             2
    .  "  BANK_OBJ_WORKL_MODIFY_BUFFER

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
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_tab_success
 
 TYPE BANK_TAB_PP_STATUS_CHANGE ,
ld_i_tab_modify
 
 TYPE BANK_TAB_PP_STATUS_CHANGE ,
ld_i_flg_perform_db_changes
 
 TYPE XFELD ,
ld_i_ref_logger
 
 TYPE IF_BANK_PP_LOGGER .


ld_i_tab_modify = 'Check type of data required'.
ld_i_flg_perform_db_changes = 'Check type of data required'.
ld_i_ref_logger = 'Check type of data required'.