SAP BANK_MAP_PP_GET_STATUS Function Module for









BANK_MAP_PP_GET_STATUS is a standard bank map pp get status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for bank map pp get status FM, simply by entering the name BANK_MAP_PP_GET_STATUS into the relevant SAP transaction such as SE37 or SE38.

Function Group: BANK_MAP_PP_CTRL
Program Name: SAPLBANK_MAP_PP_CTRL
Main Program: SAPLBANK_MAP_PP_CTRL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BANK_MAP_PP_GET_STATUS pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'BANK_MAP_PP_GET_STATUS'"
EXPORTING
* I_PROGN = "Name of the Program/Report on an Application Process
* I_PROGDATE = "Date of Program Run
* I_PROGNO = "Sequential Number of the Program Run
* I_TAB_RUNKEY = "List of Mass Run Keys
* I_APPLCATG = "Application Type in Parallel Processing
* I_TAB_RNG_APPLCATG = "
* I_XFORCE_DB_READ = 'X' "Checkbox Field
* I_FLG_CHECK_ACTIVE_RUNS = 'X' "

IMPORTING
E_TAB_STAT = "Status of Mass Runs
E_STR_STAT = "Status of a Mass Run
E_TAB_DETAILS = "Detail Data for Mass Runs
E_STR_DETAILS = "Details on Mass Run
.



IMPORTING Parameters details for BANK_MAP_PP_GET_STATUS

I_PROGN - Name of the Program/Report on an Application Process

Data type: BANK_DTE_PP_PROGN
Optional: Yes
Call by Reference: Yes

I_PROGDATE - Date of Program Run

Data type: BANK_DTE_PP_PROGDATE
Optional: Yes
Call by Reference: Yes

I_PROGNO - Sequential Number of the Program Run

Data type: BANK_DTE_PP_PROGNO
Optional: Yes
Call by Reference: Yes

I_TAB_RUNKEY - List of Mass Run Keys

Data type: BANK_TAB_RUNKEY
Optional: Yes
Call by Reference: Yes

I_APPLCATG - Application Type in Parallel Processing

Data type: BANK_DTE_PP_PAAPPLCATG
Optional: Yes
Call by Reference: Yes

I_TAB_RNG_APPLCATG -

Data type: BANK_TAB_RNG_APPLCATG
Optional: Yes
Call by Reference: Yes

I_XFORCE_DB_READ - Checkbox Field

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_FLG_CHECK_ACTIVE_RUNS -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BANK_MAP_PP_GET_STATUS

E_TAB_STAT - Status of Mass Runs

Data type: BANK_TAB_PP_RUN_STATUS
Optional: No
Call by Reference: Yes

E_STR_STAT - Status of a Mass Run

Data type: BANK_STR_PP_RUN_STATUS
Optional: No
Call by Reference: Yes

E_TAB_DETAILS - Detail Data for Mass Runs

Data type: BANK_TAB_PP_RUNDETAILS
Optional: No
Call by Reference: Yes

E_STR_DETAILS - Details on Mass Run

Data type: BANK_STR_PP_RUNDETAILS
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BANK_MAP_PP_GET_STATUS Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_i_progn  TYPE BANK_DTE_PP_PROGN, "   
lv_e_tab_stat  TYPE BANK_TAB_PP_RUN_STATUS, "   
lv_e_str_stat  TYPE BANK_STR_PP_RUN_STATUS, "   
lv_i_progdate  TYPE BANK_DTE_PP_PROGDATE, "   
lv_i_progno  TYPE BANK_DTE_PP_PROGNO, "   
lv_e_tab_details  TYPE BANK_TAB_PP_RUNDETAILS, "   
lv_i_tab_runkey  TYPE BANK_TAB_RUNKEY, "   
lv_e_str_details  TYPE BANK_STR_PP_RUNDETAILS, "   
lv_i_applcatg  TYPE BANK_DTE_PP_PAAPPLCATG, "   
lv_i_tab_rng_applcatg  TYPE BANK_TAB_RNG_APPLCATG, "   
lv_i_xforce_db_read  TYPE XFELD, "   'X'
lv_i_flg_check_active_runs  TYPE XFELD. "   'X'

  CALL FUNCTION 'BANK_MAP_PP_GET_STATUS'  "
    EXPORTING
         I_PROGN = lv_i_progn
         I_PROGDATE = lv_i_progdate
         I_PROGNO = lv_i_progno
         I_TAB_RUNKEY = lv_i_tab_runkey
         I_APPLCATG = lv_i_applcatg
         I_TAB_RNG_APPLCATG = lv_i_tab_rng_applcatg
         I_XFORCE_DB_READ = lv_i_xforce_db_read
         I_FLG_CHECK_ACTIVE_RUNS = lv_i_flg_check_active_runs
    IMPORTING
         E_TAB_STAT = lv_e_tab_stat
         E_STR_STAT = lv_e_str_stat
         E_TAB_DETAILS = lv_e_tab_details
         E_STR_DETAILS = lv_e_str_details
. " BANK_MAP_PP_GET_STATUS




ABAP code using 7.40 inline data declarations to call FM BANK_MAP_PP_GET_STATUS

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
DATA(ld_i_xforce_db_read) = 'X'.
 
DATA(ld_i_flg_check_active_runs) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!