SAP FMFR_CHANGE_COMPLETION_FLAG Function Module for
FMFR_CHANGE_COMPLETION_FLAG is a standard fmfr change completion flag 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 fmfr change completion flag FM, simply by entering the name FMFR_CHANGE_COMPLETION_FLAG into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMFR
Program Name: SAPLFMFR
Main Program: SAPLFMFR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMFR_CHANGE_COMPLETION_FLAG 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 'FMFR_CHANGE_COMPLETION_FLAG'".
EXPORTING
* I_FLG_COMMIT = ' ' "
* I_FLG_CHECKONLY = 'X' "
* I_FLG_COMPLETE_DOC = ' ' "
IMPORTING
E_COUNT_SUCCESS = "
E_COUNT_SETHEAD = "
TABLES
T_POSITIONS = "
EXCEPTIONS
NOT_FOUND = 1 INTERNAL_ERROR = 2 ERROR_OCCURED = 3
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_SAPLFMFR_001 Earmarked Funds: PBO Initial Screen
EXIT_SAPLFMFR_002 Earmarked Funds: PAI Initial Screen, All Data Read
EXIT_SAPLFMFR_003 Earmarked Funds: PAI, Checking of Item on Overview and Detail Screen
EXIT_SAPLFMFR_004 Earmarked Funds: PAI, Total Documents Check (Also Before Saving)
EXIT_SAPLFMFR_005 Earmarked Funds: PBO for Every Line, for Example, Field Control (2)
EXIT_SAPLFMFR_006 Earmarked Funds: PBO for Every Line, for example, Field Control (1)
EXIT_SAPLFMFR_007 Earmarked Funds: Conditions for Workflow Restart
EXIT_SAPLFMFR_008 Earmarked Funds: Function Code Processing in Overview Screen
EXIT_SAPLFMFR_009 Earmarked Fund: Function Code Processing in Detail Screen
EXIT_SAPLFMFR_010 Earmarked Fund: Update of Data in Database
IMPORTING Parameters details for FMFR_CHANGE_COMPLETION_FLAG
I_FLG_COMMIT -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_CHECKONLY -
Data type: BOOLE-BOOLEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_COMPLETE_DOC -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FMFR_CHANGE_COMPLETION_FLAG
E_COUNT_SUCCESS -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
E_COUNT_SETHEAD -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FMFR_CHANGE_COMPLETION_FLAG
T_POSITIONS -
Data type: FMRE_SERLKOptional: 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)
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_OCCURED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FMFR_CHANGE_COMPLETION_FLAG 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_not_found | TYPE STRING, " | |||
| lt_t_positions | TYPE STANDARD TABLE OF FMRE_SERLK, " | |||
| lv_i_flg_commit | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_e_count_success | TYPE I, " | |||
| lv_internal_error | TYPE I, " | |||
| lv_e_count_sethead | TYPE I, " | |||
| lv_i_flg_checkonly | TYPE BOOLE-BOOLE, " 'X' | |||
| lv_error_occured | TYPE BOOLE, " | |||
| lv_i_flg_complete_doc | TYPE BOOLE-BOOLE. " SPACE |
|   CALL FUNCTION 'FMFR_CHANGE_COMPLETION_FLAG' " |
| EXPORTING | ||
| I_FLG_COMMIT | = lv_i_flg_commit | |
| I_FLG_CHECKONLY | = lv_i_flg_checkonly | |
| I_FLG_COMPLETE_DOC | = lv_i_flg_complete_doc | |
| IMPORTING | ||
| E_COUNT_SUCCESS | = lv_e_count_success | |
| E_COUNT_SETHEAD | = lv_e_count_sethead | |
| TABLES | ||
| T_POSITIONS | = lt_t_positions | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| INTERNAL_ERROR = 2 | ||
| ERROR_OCCURED = 3 | ||
| . " FMFR_CHANGE_COMPLETION_FLAG | ||
ABAP code using 7.40 inline data declarations to call FM FMFR_CHANGE_COMPLETION_FLAG
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 BOOLE FROM BOOLE INTO @DATA(ld_i_flg_commit). | ||||
| DATA(ld_i_flg_commit) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_flg_checkonly). | ||||
| DATA(ld_i_flg_checkonly) | = 'X'. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_flg_complete_doc). | ||||
| DATA(ld_i_flg_complete_doc) | = ' '. | |||
Search for further information about these or an SAP related objects