SAP RM_GAP_EVAL Function Module for IS-B: RM Gap Analysis
RM_GAP_EVAL is a standard rm gap eval SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-B: RM Gap Analysis 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 rm gap eval FM, simply by entering the name RM_GAP_EVAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMG12
Program Name: SAPLRMG12
Main Program: SAPLRMG12
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_GAP_EVAL 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 'RM_GAP_EVAL'"IS-B: RM Gap Analysis.
CHANGING
IS_JBRGAPPARAMETER = "Input Parameter
TABLES
* I_CRIT_SELTAB = "Selection table
* E_JBRPHAMORTRES = "
* I_REP_DIM_T = "
* I_SF_TAB = "Table of fields required (drill down)
E_JBRREPGAP = "Results Structure for Gap Analysis for Drilldown
* E_JBRPHBAUM = "Tree Structure for Portfolio Hierarch
* E_HTEXT_TAB = "
* E_ZUORD = "
* I_REP_SELTAB = "
* I_BSTD = "
* I_SIMLF = "
* I_JBRSZTAB = "
EXCEPTIONS
ERROR_FOUND = 1
CHANGING Parameters details for RM_GAP_EVAL
IS_JBRGAPPARAMETER - Input Parameter
Data type: JBRGAPPARAMETEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RM_GAP_EVAL
I_CRIT_SELTAB - Selection table
Data type: CEDSTOptional: Yes
Call by Reference: No ( called with pass by value option)
E_JBRPHAMORTRES -
Data type: JBRPHAMORTRESOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REP_DIM_T -
Data type: JBRSIMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SF_TAB - Table of fields required (drill down)
Data type: CFBSF01Optional: Yes
Call by Reference: Yes
E_JBRREPGAP - Results Structure for Gap Analysis for Drilldown
Data type: JBRREPGAPOptional: No
Call by Reference: No ( called with pass by value option)
E_JBRPHBAUM - Tree Structure for Portfolio Hierarch
Data type: JBRPHBAUMOptional: Yes
Call by Reference: No ( called with pass by value option)
E_HTEXT_TAB -
Data type: JBRNAMEDATOptional: Yes
Call by Reference: No ( called with pass by value option)
E_ZUORD -
Data type: JBRZUORDNOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REP_SELTAB -
Data type: CEDSTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BSTD -
Data type: JBRBSTDRANOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SIMLF -
Data type: JBRSIMLFRANOptional: Yes
Call by Reference: No ( called with pass by value option)
I_JBRSZTAB -
Data type: JBRSZTABOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_FOUND - Error in the input structure
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_GAP_EVAL 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_error_found | TYPE STRING, " | |||
| lt_i_crit_seltab | TYPE STANDARD TABLE OF CEDST, " | |||
| lv_is_jbrgapparameter | TYPE JBRGAPPARAMETER, " | |||
| lt_e_jbrphamortres | TYPE STANDARD TABLE OF JBRPHAMORTRES, " | |||
| lt_i_rep_dim_t | TYPE STANDARD TABLE OF JBRSIM, " | |||
| lt_i_sf_tab | TYPE STANDARD TABLE OF CFBSF01, " | |||
| lt_e_jbrrepgap | TYPE STANDARD TABLE OF JBRREPGAP, " | |||
| lt_e_jbrphbaum | TYPE STANDARD TABLE OF JBRPHBAUM, " | |||
| lt_e_htext_tab | TYPE STANDARD TABLE OF JBRNAMEDAT, " | |||
| lt_e_zuord | TYPE STANDARD TABLE OF JBRZUORDN, " | |||
| lt_i_rep_seltab | TYPE STANDARD TABLE OF CEDST, " | |||
| lt_i_bstd | TYPE STANDARD TABLE OF JBRBSTDRAN, " | |||
| lt_i_simlf | TYPE STANDARD TABLE OF JBRSIMLFRAN, " | |||
| lt_i_jbrsztab | TYPE STANDARD TABLE OF JBRSZTAB. " |
|   CALL FUNCTION 'RM_GAP_EVAL' "IS-B: RM Gap Analysis |
| CHANGING | ||
| IS_JBRGAPPARAMETER | = lv_is_jbrgapparameter | |
| TABLES | ||
| I_CRIT_SELTAB | = lt_i_crit_seltab | |
| E_JBRPHAMORTRES | = lt_e_jbrphamortres | |
| I_REP_DIM_T | = lt_i_rep_dim_t | |
| I_SF_TAB | = lt_i_sf_tab | |
| E_JBRREPGAP | = lt_e_jbrrepgap | |
| E_JBRPHBAUM | = lt_e_jbrphbaum | |
| E_HTEXT_TAB | = lt_e_htext_tab | |
| E_ZUORD | = lt_e_zuord | |
| I_REP_SELTAB | = lt_i_rep_seltab | |
| I_BSTD | = lt_i_bstd | |
| I_SIMLF | = lt_i_simlf | |
| I_JBRSZTAB | = lt_i_jbrsztab | |
| EXCEPTIONS | ||
| ERROR_FOUND = 1 | ||
| . " RM_GAP_EVAL | ||
ABAP code using 7.40 inline data declarations to call FM RM_GAP_EVAL
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.Search for further information about these or an SAP related objects