SAP MRM_LIMIT_CHECK Function Module for check limit of blanket PO
MRM_LIMIT_CHECK is a standard mrm limit check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for check limit of blanket PO 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 mrm limit check FM, simply by entering the name MRM_LIMIT_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: MRMC
Program Name: SAPLMRMC
Main Program: SAPLMRMC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MRM_LIMIT_CHECK 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 'MRM_LIMIT_CHECK'"check limit of blanket PO.
EXPORTING
I_ACTVALUE = "
I_SUMLIMIT = "
I_BUKRS = "
* I_HSWAE = ' ' "Currency Key
* I_WAERS = ' ' "Currency Key
* I_KURSF = 0 "Exchange Rate
* I_WWERT = ' ' "Translation Date
IMPORTING
E_DIFFWERT = "
E_RC = "
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLMRMC_001 Customer Exit: Change Tolerance Check - Logistics Invoice Verification
EXIT_SAPLMRMC_002 Customer Exit: Change Criteria for Parked Document Release for Posting
IMPORTING Parameters details for MRM_LIMIT_CHECK
I_ACTVALUE -
Data type: ESUH-ACTVALUEOptional: No
Call by Reference: No ( called with pass by value option)
I_SUMLIMIT -
Data type: ESUH-SUMLIMITOptional: No
Call by Reference: No ( called with pass by value option)
I_BUKRS -
Data type: T169G-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_HSWAE - Currency Key
Data type: T001-WAERSDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_WAERS - Currency Key
Data type: BKPF-WAERSDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KURSF - Exchange Rate
Data type: BKPF-KURSFOptional: Yes
Call by Reference: No ( called with pass by value option)
I_WWERT - Translation Date
Data type: BKPF-WWERTDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MRM_LIMIT_CHECK
E_DIFFWERT -
Data type: ESUH-ACTVALUEOptional: No
Call by Reference: No ( called with pass by value option)
E_RC -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MRM_LIMIT_CHECK 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_e_diffwert | TYPE ESUH-ACTVALUE, " | |||
| lv_i_actvalue | TYPE ESUH-ACTVALUE, " | |||
| lv_e_rc | TYPE SY-SUBRC, " | |||
| lv_i_sumlimit | TYPE ESUH-SUMLIMIT, " | |||
| lv_i_bukrs | TYPE T169G-BUKRS, " | |||
| lv_i_hswae | TYPE T001-WAERS, " ' ' | |||
| lv_i_waers | TYPE BKPF-WAERS, " ' ' | |||
| lv_i_kursf | TYPE BKPF-KURSF, " 0 | |||
| lv_i_wwert | TYPE BKPF-WWERT. " ' ' |
|   CALL FUNCTION 'MRM_LIMIT_CHECK' "check limit of blanket PO |
| EXPORTING | ||
| I_ACTVALUE | = lv_i_actvalue | |
| I_SUMLIMIT | = lv_i_sumlimit | |
| I_BUKRS | = lv_i_bukrs | |
| I_HSWAE | = lv_i_hswae | |
| I_WAERS | = lv_i_waers | |
| I_KURSF | = lv_i_kursf | |
| I_WWERT | = lv_i_wwert | |
| IMPORTING | ||
| E_DIFFWERT | = lv_e_diffwert | |
| E_RC | = lv_e_rc | |
| . " MRM_LIMIT_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM MRM_LIMIT_CHECK
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.| "SELECT single ACTVALUE FROM ESUH INTO @DATA(ld_e_diffwert). | ||||
| "SELECT single ACTVALUE FROM ESUH INTO @DATA(ld_i_actvalue). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_rc). | ||||
| "SELECT single SUMLIMIT FROM ESUH INTO @DATA(ld_i_sumlimit). | ||||
| "SELECT single BUKRS FROM T169G INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single WAERS FROM T001 INTO @DATA(ld_i_hswae). | ||||
| DATA(ld_i_hswae) | = ' '. | |||
| "SELECT single WAERS FROM BKPF INTO @DATA(ld_i_waers). | ||||
| DATA(ld_i_waers) | = ' '. | |||
| "SELECT single KURSF FROM BKPF INTO @DATA(ld_i_kursf). | ||||
| "SELECT single WWERT FROM BKPF INTO @DATA(ld_i_wwert). | ||||
| DATA(ld_i_wwert) | = ' '. | |||
Search for further information about these or an SAP related objects