SAP BANK_MAP_PP_CONFIRM_OBJECTS Function Module for









BANK_MAP_PP_CONFIRM_OBJECTS is a standard bank map pp confirm objects 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 confirm objects FM, simply by entering the name BANK_MAP_PP_CONFIRM_OBJECTS into the relevant SAP transaction such as SE37 or SE38.

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



Function BANK_MAP_PP_CONFIRM_OBJECTS 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_CONFIRM_OBJECTS'"
EXPORTING
I_PROGN = "Program Name
* I_FLG_USE_UPDATE_TASK = "
* I_REF_LOGGER = "
* I_FLG_DEFAULT_EMSG = '+' "
I_PROGDATE = "Date of Program Run
I_PROGNO = "Sequential Number of the Program Run
* I_TAB_OBJECTS_READY = "
* I_TAB_OBJECTS_RESTART = "
* I_TAB_OBJECTS_ASYNC = "
* I_TAB_OBJECTS_RETRY = "
* I_TAB_STATUS_CHANGE = "Transfer Data for Status Change of Objects
* I_FLG_UPD_RUN_STATUS = 'X' "

IMPORTING
E_TAB_OBJ_MODIFIED = "Object Key
E_RUNSTATUS = "

EXCEPTIONS
INTERNAL_ERROR = 1
.



IMPORTING Parameters details for BANK_MAP_PP_CONFIRM_OBJECTS

I_PROGN - Program Name

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

I_FLG_USE_UPDATE_TASK -

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

I_REF_LOGGER -

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

I_FLG_DEFAULT_EMSG -

Data type: EMSG_USAGE_FLAG
Default: '+'
Optional: Yes
Call by Reference: Yes

I_PROGDATE - Date of Program Run

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

I_PROGNO - Sequential Number of the Program Run

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

I_TAB_OBJECTS_READY -

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

I_TAB_OBJECTS_RESTART -

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

I_TAB_OBJECTS_ASYNC -

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

I_TAB_OBJECTS_RETRY -

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

I_TAB_STATUS_CHANGE - Transfer Data for Status Change of Objects

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

I_FLG_UPD_RUN_STATUS -

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

EXPORTING Parameters details for BANK_MAP_PP_CONFIRM_OBJECTS

E_TAB_OBJ_MODIFIED - Object Key

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

E_RUNSTATUS -

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

EXCEPTIONS details

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BANK_MAP_PP_CONFIRM_OBJECTS 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_internal_error  TYPE BANK_DTE_PP_PROGN, "   
lv_e_tab_obj_modified  TYPE BANK_TAB_OBJKEY, "   
lv_i_flg_use_update_task  TYPE XFELD, "   
lv_i_ref_logger  TYPE IF_BANK_PP_LOGGER, "   
lv_i_flg_default_emsg  TYPE EMSG_USAGE_FLAG, "   '+'
lv_i_progdate  TYPE BANK_DTE_PP_PROGDATE, "   
lv_e_runstatus  TYPE BANK_DTE_PP_RUNSTATUS, "   
lv_i_progno  TYPE BANK_DTE_PP_PROGNO, "   
lv_i_tab_objects_ready  TYPE BANK_TAB_OBJKEY, "   
lv_i_tab_objects_restart  TYPE BANK_TAB_OBJKEY, "   
lv_i_tab_objects_async  TYPE BANK_TAB_OBJKEY, "   
lv_i_tab_objects_retry  TYPE BANK_TAB_OBJKEY, "   
lv_i_tab_status_change  TYPE BANK_TAB_PP_STATUS_CHANGE, "   
lv_i_flg_upd_run_status  TYPE XFELD. "   'X'

  CALL FUNCTION 'BANK_MAP_PP_CONFIRM_OBJECTS'  "
    EXPORTING
         I_PROGN = lv_i_progn
         I_FLG_USE_UPDATE_TASK = lv_i_flg_use_update_task
         I_REF_LOGGER = lv_i_ref_logger
         I_FLG_DEFAULT_EMSG = lv_i_flg_default_emsg
         I_PROGDATE = lv_i_progdate
         I_PROGNO = lv_i_progno
         I_TAB_OBJECTS_READY = lv_i_tab_objects_ready
         I_TAB_OBJECTS_RESTART = lv_i_tab_objects_restart
         I_TAB_OBJECTS_ASYNC = lv_i_tab_objects_async
         I_TAB_OBJECTS_RETRY = lv_i_tab_objects_retry
         I_TAB_STATUS_CHANGE = lv_i_tab_status_change
         I_FLG_UPD_RUN_STATUS = lv_i_flg_upd_run_status
    IMPORTING
         E_TAB_OBJ_MODIFIED = lv_e_tab_obj_modified
         E_RUNSTATUS = lv_e_runstatus
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " BANK_MAP_PP_CONFIRM_OBJECTS




ABAP code using 7.40 inline data declarations to call FM BANK_MAP_PP_CONFIRM_OBJECTS

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_flg_default_emsg) = '+'.
 
 
 
 
 
 
 
 
 
DATA(ld_i_flg_upd_run_status) = '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!