BANK_OBJ_PP_SET_RUN_LOCK SAP Function module

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

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

Pattern for FM BANK_OBJ_PP_SET_RUN_LOCK - BANK OBJ PP SET RUN LOCK

CALL FUNCTION 'BANK_OBJ_PP_SET_RUN_LOCK' "
  EXPORTING
    i_progn =                   " bank_dte_pp_progn
    i_progdate =                " bank_dte_pp_progdate
    i_progno =                  " bank_dte_pp_progno
*   i_flg_cumulative =          " boolean
*   i_flg_wait =                " boolean
*   i_cnt_max_attempts =        " i
*   i_flg_remove_after_commit =   " boolean
  EXCEPTIONS
    NOT_QUALIFIED = 1           "
    FOREIGN_LOCK = 2            "
    SYSTEM_FAILURE = 3          "
    .  "  BANK_OBJ_PP_SET_RUN_LOCK

ABAP code example for Function Module BANK_OBJ_PP_SET_RUN_LOCK

The ABAP code below is a full code listing to execute function module BANK_OBJ_PP_SET_RUN_LOCK 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_i_progn) = 'Check type of data required'.

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

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

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

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

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

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

CALL FUNCTION 'BANK_OBJ_PP_SET_RUN_LOCK'
  EXPORTING
    i_progn =                    ld_i_progn
    i_progdate =                 ld_i_progdate
    i_progno =                   ld_i_progno
*   i_flg_cumulative =           ld_i_flg_cumulative
*   i_flg_wait =                 ld_i_flg_wait
*   i_cnt_max_attempts =         ld_i_cnt_max_attempts
*   i_flg_remove_after_commit =    ld_i_flg_remove_after_commit
  EXCEPTIONS
    NOT_QUALIFIED =              1
    FOREIGN_LOCK =               2
    SYSTEM_FAILURE =             3
    .  "  BANK_OBJ_PP_SET_RUN_LOCK

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
ELSEIF SY-SUBRC EQ 3. "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_progn
 
 TYPE BANK_DTE_PP_PROGN ,
ld_i_progdate
 
 TYPE BANK_DTE_PP_PROGDATE ,
ld_i_progno
 
 TYPE BANK_DTE_PP_PROGNO ,
ld_i_flg_cumulative
 
 TYPE BOOLEAN ,
ld_i_flg_wait
 
 TYPE BOOLEAN ,
ld_i_cnt_max_attempts
 
 TYPE I ,
ld_i_flg_remove_after_commit
 
 TYPE BOOLEAN .


ld_i_progn = 'Check type of data required'.
ld_i_progdate = 'Check type of data required'.
ld_i_progno = 'Check type of data required'.
ld_i_flg_cumulative = 'Check type of data required'.
ld_i_flg_wait = 'Check type of data required'.
ld_i_cnt_max_attempts = 'Check type of data required'.
ld_i_flg_remove_after_commit = 'Check type of data required'.