SAP FKK_CHANGE_DYNP_FIELDS Function Module for
FKK_CHANGE_DYNP_FIELDS is a standard fkk change dynp fields 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 change dynp fields FM, simply by entering the name FKK_CHANGE_DYNP_FIELDS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKVT
Program Name: SAPLFKVT
Main Program: SAPLFKVT
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_CHANGE_DYNP_FIELDS 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_CHANGE_DYNP_FIELDS'".
EXPORTING
I_APPLK = "Application
* I_SET_INVISIBLE = ' ' "
* I_SET_INPUT = ' ' "
TABLES
* E_FKKDD1 = "
IMPORTING Parameters details for FKK_CHANGE_DYNP_FIELDS
I_APPLK - Application
Data type: FKKOP-APPLKOptional: No
Call by Reference: No ( called with pass by value option)
I_SET_INVISIBLE -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_SET_INPUT -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for FKK_CHANGE_DYNP_FIELDS
E_FKKDD1 -
Data type: FKKDD1Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FKK_CHANGE_DYNP_FIELDS 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_applk | TYPE FKKOP-APPLK, " | |||
| lt_e_fkkdd1 | TYPE STANDARD TABLE OF FKKDD1, " | |||
| lv_i_set_invisible | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_set_input | TYPE BOOLE-BOOLE. " SPACE |
|   CALL FUNCTION 'FKK_CHANGE_DYNP_FIELDS' " |
| EXPORTING | ||
| I_APPLK | = lv_i_applk | |
| I_SET_INVISIBLE | = lv_i_set_invisible | |
| I_SET_INPUT | = lv_i_set_input | |
| TABLES | ||
| E_FKKDD1 | = lt_e_fkkdd1 | |
| . " FKK_CHANGE_DYNP_FIELDS | ||
ABAP code using 7.40 inline data declarations to call FM FKK_CHANGE_DYNP_FIELDS
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 APPLK FROM FKKOP INTO @DATA(ld_i_applk). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_set_invisible). | ||||
| DATA(ld_i_set_invisible) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_set_input). | ||||
| DATA(ld_i_set_input) | = ' '. | |||
Search for further information about these or an SAP related objects