SAP BANK_API_MR_PROGRESS Function Module for Update Information Progress of a Mass Run and Counters









BANK_API_MR_PROGRESS is a standard bank api mr progress SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Information Progress of a Mass Run and Counters processing and below is the pattern details for this FM, 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 api mr progress FM, simply by entering the name BANK_API_MR_PROGRESS into the relevant SAP transaction such as SE37 or SE38.

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



Function BANK_API_MR_PROGRESS 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_API_MR_PROGRESS'"Update Information Progress of a Mass Run and Counters
EXPORTING
I_MASSRUN_ID = "Internal Identification for Mass Runs - Technical ID
* I_TAB_COUNTER = "Counter/Counter Category
* I_VBMODE = 'X' "Indicator: Database Save via Update Task

EXCEPTIONS
NOT_QUALIFIED = 1 FAILED = 2
.



IMPORTING Parameters details for BANK_API_MR_PROGRESS

I_MASSRUN_ID - Internal Identification for Mass Runs - Technical ID

Data type: BANK_DTE_MR_MASSRUN_ID
Optional: No
Call by Reference: No ( called with pass by value option)

I_TAB_COUNTER - Counter/Counter Category

Data type: BANK_TAB_MR_COUNTER
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VBMODE - Indicator: Database Save via Update Task

Data type: BANK_DTE_MR_VBMODE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_QUALIFIED -

Data type:
Optional: No
Call by Reference: Yes

FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BANK_API_MR_PROGRESS 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_massrun_id  TYPE BANK_DTE_MR_MASSRUN_ID, "   
lv_not_qualified  TYPE BANK_DTE_MR_MASSRUN_ID, "   
lv_failed  TYPE BANK_DTE_MR_MASSRUN_ID, "   
lv_i_tab_counter  TYPE BANK_TAB_MR_COUNTER, "   
lv_i_vbmode  TYPE BANK_DTE_MR_VBMODE. "   'X'

  CALL FUNCTION 'BANK_API_MR_PROGRESS'  "Update Information Progress of a Mass Run and Counters
    EXPORTING
         I_MASSRUN_ID = lv_i_massrun_id
         I_TAB_COUNTER = lv_i_tab_counter
         I_VBMODE = lv_i_vbmode
    EXCEPTIONS
        NOT_QUALIFIED = 1
        FAILED = 2
. " BANK_API_MR_PROGRESS




ABAP code using 7.40 inline data declarations to call FM BANK_API_MR_PROGRESS

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_vbmode) = '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!