SAP FMRS_SUPPLEMENT_APPROVE Function Module for Approve Value Adjustment









FMRS_SUPPLEMENT_APPROVE is a standard fmrs supplement approve SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Approve Value Adjustment 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 fmrs supplement approve FM, simply by entering the name FMRS_SUPPLEMENT_APPROVE into the relevant SAP transaction such as SE37 or SE38.

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



Function FMRS_SUPPLEMENT_APPROVE 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 'FMRS_SUPPLEMENT_APPROVE'"Approve Value Adjustment
EXPORTING
I_BELNR = "
I_BLPOS = "
I_BPENT = "
* I_FLG_MULTIPLE = "
* I_SETLOCK = "

CHANGING
C_REASON = "
C_APPROVE = "
C_FLG_FINAL = "

EXCEPTIONS
NOT_FOUND = 1 CANCELLED = 2
.




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_SAPLFMRS_001 Value Adjustment Documents: Program Exit Initial Screen
EXIT_SAPLFMRS_002 Value Adjustment Documents: Program Exit Function Code Processing

IMPORTING Parameters details for FMRS_SUPPLEMENT_APPROVE

I_BELNR -

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

I_BLPOS -

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

I_BPENT -

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

I_FLG_MULTIPLE -

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

I_SETLOCK -

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

CHANGING Parameters details for FMRS_SUPPLEMENT_APPROVE

C_REASON -

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

C_APPROVE -

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

C_FLG_FINAL -

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

EXCEPTIONS details

NOT_FOUND -

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

CANCELLED -

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

Copy and paste ABAP code example for FMRS_SUPPLEMENT_APPROVE 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_belnr  TYPE KBLPS-BELNR, "   
lv_c_reason  TYPE KBLPS-REASON, "   
lv_not_found  TYPE KBLPS, "   
lv_i_blpos  TYPE KBLPS-BLPOS, "   
lv_cancelled  TYPE KBLPS, "   
lv_c_approve  TYPE TRWF_STRUC-APP_RCODE, "   
lv_i_bpent  TYPE KBLPS-BPENT, "   
lv_c_flg_final  TYPE BOOLE-BOOLE, "   
lv_i_flg_multiple  TYPE BOOLE-BOOLE, "   
lv_i_setlock  TYPE KBLPS-PMLOCK. "   

  CALL FUNCTION 'FMRS_SUPPLEMENT_APPROVE'  "Approve Value Adjustment
    EXPORTING
         I_BELNR = lv_i_belnr
         I_BLPOS = lv_i_blpos
         I_BPENT = lv_i_bpent
         I_FLG_MULTIPLE = lv_i_flg_multiple
         I_SETLOCK = lv_i_setlock
    CHANGING
         C_REASON = lv_c_reason
         C_APPROVE = lv_c_approve
         C_FLG_FINAL = lv_c_flg_final
    EXCEPTIONS
        NOT_FOUND = 1
        CANCELLED = 2
. " FMRS_SUPPLEMENT_APPROVE




ABAP code using 7.40 inline data declarations to call FM FMRS_SUPPLEMENT_APPROVE

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 BELNR FROM KBLPS INTO @DATA(ld_i_belnr).
 
"SELECT single REASON FROM KBLPS INTO @DATA(ld_c_reason).
 
 
"SELECT single BLPOS FROM KBLPS INTO @DATA(ld_i_blpos).
 
 
"SELECT single APP_RCODE FROM TRWF_STRUC INTO @DATA(ld_c_approve).
 
"SELECT single BPENT FROM KBLPS INTO @DATA(ld_i_bpent).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_c_flg_final).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_flg_multiple).
 
"SELECT single PMLOCK FROM KBLPS INTO @DATA(ld_i_setlock).
 


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!