SAP FKK_VARIANT_MD_SAVE Function Module for
FKK_VARIANT_MD_SAVE is a standard fkk variant md save 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 fkk variant md save FM, simply by entering the name FKK_VARIANT_MD_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_VARIANT
Program Name: SAPLFKK_VARIANT
Main Program: SAPLFKK_VARIANT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_VARIANT_MD_SAVE 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 'FKK_VARIANT_MD_SAVE'".
EXPORTING
* IV_DESCRIPTION = "Description
* IT_RANGE_GPART = "Range Table GPART
* IT_RANGE_VKONT = "Range Table VKONT
* IT_RANGE_VTREF = "Range Table Type VTREF
* IT_RANGE_BUKRS = "Range Table Company Code
* IT_MASTERDATA = "Table with Business Partners, Contract Accounts, Contracts
* IV_CURRENT = ' ' "
* IV_USER_SPECIFIC = 'X' "Custom Implementation
* IV_NO_MSG = ' ' "
* IV_GPART = "Business Partner Number
* IV_VKONT = "Contract Account Number
* IV_VTREF = "Reference Specifications from Contract
* IV_SUBAP = "Subapplication in Contract Accounts Receivable and Payable
* IV_BUKRS = "Company Code
EXCEPTIONS
E_NO_DESCRIPTION = 1
IMPORTING Parameters details for FKK_VARIANT_MD_SAVE
IV_DESCRIPTION - Description
Data type: TEXT30Optional: Yes
Call by Reference: Yes
IT_RANGE_GPART - Range Table GPART
Data type: FKK_RT_GPARTOptional: Yes
Call by Reference: Yes
IT_RANGE_VKONT - Range Table VKONT
Data type: FKK_RT_VKONTOptional: Yes
Call by Reference: Yes
IT_RANGE_VTREF - Range Table Type VTREF
Data type: FKK_RT_VTREFOptional: Yes
Call by Reference: Yes
IT_RANGE_BUKRS - Range Table Company Code
Data type: FKK_RT_BUKRSOptional: Yes
Call by Reference: Yes
IT_MASTERDATA - Table with Business Partners, Contract Accounts, Contracts
Data type: FKK_MASTERDATA_TOptional: Yes
Call by Reference: Yes
IV_CURRENT -
Data type: BOOLEANDefault: ' '
Optional: No
Call by Reference: Yes
IV_USER_SPECIFIC - Custom Implementation
Data type: BOOLEANDefault: 'X'
Optional: No
Call by Reference: Yes
IV_NO_MSG -
Data type: BOOLEANDefault: ' '
Optional: No
Call by Reference: Yes
IV_GPART - Business Partner Number
Data type: GPART_KKOptional: Yes
Call by Reference: Yes
IV_VKONT - Contract Account Number
Data type: VKONT_KKOptional: Yes
Call by Reference: Yes
IV_VTREF - Reference Specifications from Contract
Data type: VTREF_KKOptional: Yes
Call by Reference: Yes
IV_SUBAP - Subapplication in Contract Accounts Receivable and Payable
Data type: SUBAP_KKOptional: Yes
Call by Reference: Yes
IV_BUKRS - Company Code
Data type: BUKRSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
E_NO_DESCRIPTION - No Description
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_VARIANT_MD_SAVE 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_iv_description | TYPE TEXT30, " | |||
| lv_e_no_description | TYPE TEXT30, " | |||
| lv_it_range_gpart | TYPE FKK_RT_GPART, " | |||
| lv_it_range_vkont | TYPE FKK_RT_VKONT, " | |||
| lv_it_range_vtref | TYPE FKK_RT_VTREF, " | |||
| lv_it_range_bukrs | TYPE FKK_RT_BUKRS, " | |||
| lv_it_masterdata | TYPE FKK_MASTERDATA_T, " | |||
| lv_iv_current | TYPE BOOLEAN, " ' ' | |||
| lv_iv_user_specific | TYPE BOOLEAN, " 'X' | |||
| lv_iv_no_msg | TYPE BOOLEAN, " ' ' | |||
| lv_iv_gpart | TYPE GPART_KK, " | |||
| lv_iv_vkont | TYPE VKONT_KK, " | |||
| lv_iv_vtref | TYPE VTREF_KK, " | |||
| lv_iv_subap | TYPE SUBAP_KK, " | |||
| lv_iv_bukrs | TYPE BUKRS. " |
|   CALL FUNCTION 'FKK_VARIANT_MD_SAVE' " |
| EXPORTING | ||
| IV_DESCRIPTION | = lv_iv_description | |
| IT_RANGE_GPART | = lv_it_range_gpart | |
| IT_RANGE_VKONT | = lv_it_range_vkont | |
| IT_RANGE_VTREF | = lv_it_range_vtref | |
| IT_RANGE_BUKRS | = lv_it_range_bukrs | |
| IT_MASTERDATA | = lv_it_masterdata | |
| IV_CURRENT | = lv_iv_current | |
| IV_USER_SPECIFIC | = lv_iv_user_specific | |
| IV_NO_MSG | = lv_iv_no_msg | |
| IV_GPART | = lv_iv_gpart | |
| IV_VKONT | = lv_iv_vkont | |
| IV_VTREF | = lv_iv_vtref | |
| IV_SUBAP | = lv_iv_subap | |
| IV_BUKRS | = lv_iv_bukrs | |
| EXCEPTIONS | ||
| E_NO_DESCRIPTION = 1 | ||
| . " FKK_VARIANT_MD_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM FKK_VARIANT_MD_SAVE
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.| DATA(ld_iv_current) | = ' '. | |||
| DATA(ld_iv_user_specific) | = 'X'. | |||
| DATA(ld_iv_no_msg) | = ' '. | |||
Search for further information about these or an SAP related objects