SAP FMTRE_CHANGE_RE Function Module for

Search SAP Function Modules

FMTRE_CHANGE_RE is a standard fmtre change re 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 fmtre change re FM, simply by entering the name FMTRE_CHANGE_RE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMTRE
Program Name: SAPLFMTRE
Main Program: SAPLFMTRE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FMTRE_CHANGE_RE 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 'FMTRE_CHANGE_RE'"
  EXPORTING
*  CTU = 'X' "
   I_FIPEX =  "
   I_FIKRS =  "
   I_GJAHR =  "
   I_VALUE =  "
   I_WAERS =  "
*  MODE = 'N' "
*  UPDATE = 'L' "
*  GROUP =  "
*  USER =  "
*  KEEP =  "
*  HOLDDATE =  "
*  NODATA = '/' "
   I_FISTL =  "

 IMPORTING
   SUBRC =  "

TABLES
*  MESSTAB =  "

.

IMPORTING Parameters details for FMTRE_CHANGE_RE

CTU -

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

I_FIPEX -

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

I_FIKRS -

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

I_GJAHR -

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

I_VALUE -

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

I_WAERS -

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

MODE -

Data type: APQI-PUTACTIVE
Default: 'N'
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPDATE -

Data type: APQI-PUTACTIVE
Default: 'L'
Optional: Yes
Call by Reference: No ( called with pass by value option)

GROUP -

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

USER -

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

KEEP -

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

HOLDDATE -

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

NODATA -

Data type: APQI-PUTACTIVE
Default: '/'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FISTL -

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

EXPORTING Parameters details for FMTRE_CHANGE_RE

SUBRC -

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

TABLES Parameters details for FMTRE_CHANGE_RE

MESSTAB -

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

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

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