SAP CLSE_CLFM_BUF_FLAGS Function Module for Set Buffer Indicator if Classification Data Changed in CLFM
CLSE_CLFM_BUF_FLAGS is a standard clse clfm buf flags SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Buffer Indicator if Classification Data Changed in CLFM 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 clse clfm buf flags FM, simply by entering the name CLSE_CLFM_BUF_FLAGS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CLSE
Program Name: SAPLCLSE
Main Program: SAPLCLSE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CLSE_CLFM_BUF_FLAGS 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 'CLSE_CLFM_BUF_FLAGS'"Set Buffer Indicator if Classification Data Changed in CLFM.
EXPORTING
* I_AUSP_FLG = ' ' "AUSP Was Processed in CLFM
* I_KSSK_FLG = ' ' "KSSK Was Processed in CLFM
IMPORTING Parameters details for CLSE_CLFM_BUF_FLAGS
I_AUSP_FLG - AUSP Was Processed in CLFM
Data type: RMCLF-KREUZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KSSK_FLG - KSSK Was Processed in CLFM
Data type: RMCLF-KREUZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CLSE_CLFM_BUF_FLAGS 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_ausp_flg | TYPE RMCLF-KREUZ, " SPACE | |||
| lv_i_kssk_flg | TYPE RMCLF-KREUZ. " SPACE |
|   CALL FUNCTION 'CLSE_CLFM_BUF_FLAGS' "Set Buffer Indicator if Classification Data Changed in CLFM |
| EXPORTING | ||
| I_AUSP_FLG | = lv_i_ausp_flg | |
| I_KSSK_FLG | = lv_i_kssk_flg | |
| . " CLSE_CLFM_BUF_FLAGS | ||
ABAP code using 7.40 inline data declarations to call FM CLSE_CLFM_BUF_FLAGS
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 KREUZ FROM RMCLF INTO @DATA(ld_i_ausp_flg). | ||||
| DATA(ld_i_ausp_flg) | = ' '. | |||
| "SELECT single KREUZ FROM RMCLF INTO @DATA(ld_i_kssk_flg). | ||||
| DATA(ld_i_kssk_flg) | = ' '. | |||
Search for further information about these or an SAP related objects