BANK_MAP_PP_LOCKS_GET_RUN_MLT SAP Function module

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

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

Pattern for FM BANK_MAP_PP_LOCKS_GET_RUN_MLT - BANK MAP PP LOCKS GET RUN MLT

CALL FUNCTION 'BANK_MAP_PP_LOCKS_GET_RUN_MLT' "
  EXPORTING
    i_progn =                   " bank_dte_pp_progn  Name of the Program/Report on an Application Process
    i_progdate =                " bank_dte_pp_progdate  Date of Program Run
    i_progno =                  " bank_dte_pp_progno  Sequential Number of the Program Run
*   i_maxcount =                " bank_dte_pp_maxcount  Maximum Number of Data Records to Be Read
  IMPORTING
    e_tab_locked =              " bank_tab_objkey  List of locked objects
    e_rcd =                     " sy-subrc
    .  "  BANK_MAP_PP_LOCKS_GET_RUN_MLT

ABAP code example for Function Module BANK_MAP_PP_LOCKS_GET_RUN_MLT

The ABAP code below is a full code listing to execute function module BANK_MAP_PP_LOCKS_GET_RUN_MLT 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_locked  
 
 TYPE BANK_TAB_OBJKEY
,
ld_e_rcd  
 
 TYPE SY-SUBRC
.


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_maxcount) = 'Check type of data required'.
.

CALL FUNCTION 'BANK_MAP_PP_LOCKS_GET_RUN_MLT'
  EXPORTING
    i_progn =                    ld_i_progn
    i_progdate =                 ld_i_progdate
    i_progno =                   ld_i_progno
*   i_maxcount =                 ld_i_maxcount
  IMPORTING
    e_tab_locked =               ld_e_tab_locked
    e_rcd =                      ld_e_rcd
    .  "  BANK_MAP_PP_LOCKS_GET_RUN_MLT

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_tab_locked
 
 TYPE BANK_TAB_OBJKEY ,
ld_i_progn
 
 TYPE BANK_DTE_PP_PROGN ,
ld_e_rcd
 
 TYPE SY-SUBRC ,
ld_i_progdate
 
 TYPE BANK_DTE_PP_PROGDATE ,
ld_i_progno
 
 TYPE BANK_DTE_PP_PROGNO ,
ld_i_maxcount
 
 TYPE BANK_DTE_PP_MAXCOUNT .


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_maxcount = 'Check type of data required'.