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

Function KAUF_SET_CHANGE_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 'KAUF_SET_CHANGE_FLAG'".
EXPORTING
I_KAUF = "Administration Data for Internal Orders
EXCEPTIONS
ORDER_NOT_IN_BUFFER = 1 ILLEGAL_CHANGE = 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_SAPLKAUF_001 Function call from master data maintenance
EXIT_SAPLKAUF_004 Customer exit for controlling printing of master data for internal orders
IMPORTING Parameters details for KAUF_SET_CHANGE_FLAG
I_KAUF - Administration Data for Internal Orders
Data type: KAUFOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ORDER_NOT_IN_BUFFER - Order does not exist
Data type:Optional: No
Call by Reference: Yes
ILLEGAL_CHANGE - Change Not Allowed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for KAUF_SET_CHANGE_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_i_kauf | TYPE KAUF, " | |||
| lv_order_not_in_buffer | TYPE KAUF, " | |||
| lv_illegal_change | TYPE KAUF. " |
|   CALL FUNCTION 'KAUF_SET_CHANGE_FLAG' " |
| EXPORTING | ||
| I_KAUF | = lv_i_kauf | |
| EXCEPTIONS | ||
| ORDER_NOT_IN_BUFFER = 1 | ||
| ILLEGAL_CHANGE = 2 | ||
| . " KAUF_SET_CHANGE_FLAG | ||
ABAP code using 7.40 inline data declarations to call FM KAUF_SET_CHANGE_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.Search for further information about these or an SAP related objects