SAP FMR8_CHECK_TOLERANCE Function Module for

Search SAP Function Modules

FMR8_CHECK_TOLERANCE is a standard fmr8 check tolerance 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 fmr8 check tolerance FM, simply by entering the name FMR8_CHECK_TOLERANCE into the relevant SAP transaction such as SE37 or SE38.

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

Function FMR8_CHECK_TOLERANCE 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 'FMR8_CHECK_TOLERANCE'"
  EXPORTING
   I_CONSUMPTION =  "Reduction
   I_APPROVEDAMOUNT =  "
   I_UEBTO =  "Tolerance limit for overrun
   I_FLG_UNL =  "Usage may exceed reserved amount without limit
   I_FLG_TOLOV =  "Indicator: Override Global (Percentage-Based) Tolerance
   I_BLART =  "Doc.type: Manual document entry
   I_BLTYP =  "Earmarked Funds Document Category
   I_HWAER =  "Local Currency Key
   I_WAERS =  "Transaction Currency

 IMPORTING
   E_STATUS =  "

CHANGING
   C_UEBPROZ =  "
   C_UEBTXT =  "

.

IMPORTING Parameters details for FMR8_CHECK_TOLERANCE

I_CONSUMPTION - Reduction

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

I_APPROVEDAMOUNT -

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

I_UEBTO - Tolerance limit for overrun

Data type: KBLP-UEBTO
Optional: No
Call by Reference: No ( called with pass by value option)

I_FLG_UNL - Usage may exceed reserved amount without limit

Data type: KBLP-CONSUMEKZ
Optional: No
Call by Reference: No ( called with pass by value option)

I_FLG_TOLOV - Indicator: Override Global (Percentage-Based) Tolerance

Data type: KBLP-TOLOV
Optional: No
Call by Reference: No ( called with pass by value option)

I_BLART - Doc.type: Manual document entry

Data type: KBLK-BLART
Optional: No
Call by Reference: No ( called with pass by value option)

I_BLTYP - Earmarked Funds Document Category

Data type: KBLK-BLTYP
Optional: No
Call by Reference: No ( called with pass by value option)

I_HWAER - Local Currency Key

Data type: KBLK-HWAER
Optional: No
Call by Reference: No ( called with pass by value option)

I_WAERS - Transaction Currency

Data type: KBLK-WAERS
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FMR8_CHECK_TOLERANCE

E_STATUS -

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

CHANGING Parameters details for FMR8_CHECK_TOLERANCE

C_UEBPROZ -

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

C_UEBTXT -

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

Copy and paste ABAP code example for FMR8_CHECK_TOLERANCE 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.

ABAP code using 7.40 inline data declarations to call FM FMR8_CHECK_TOLERANCE

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