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

Function FKK_SAMPLE_0367 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_SAMPLE_0367'".
EXPORTING
T_FKKMAVS = "Mass Activities: Global Values for All Mass Activities
CHANGING
C_VKNT1 = "Leading Contract Account in Dunning
C_STDBK = "Standard Company Code
IMPORTING Parameters details for FKK_SAMPLE_0367
T_FKKMAVS - Mass Activities: Global Values for All Mass Activities
Data type: FKKMAVS_TOptional: No
Call by Reference: Yes
CHANGING Parameters details for FKK_SAMPLE_0367
C_VKNT1 - Leading Contract Account in Dunning
Data type: FKKMAGRP-VKNT1Optional: No
Call by Reference: Yes
C_STDBK - Standard Company Code
Data type: FKKMAGRP-STDBKOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_SAMPLE_0367 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_c_vknt1 | TYPE FKKMAGRP-VKNT1, " | |||
| lv_t_fkkmavs | TYPE FKKMAVS_T, " | |||
| lv_c_stdbk | TYPE FKKMAGRP-STDBK. " |
|   CALL FUNCTION 'FKK_SAMPLE_0367' " |
| EXPORTING | ||
| T_FKKMAVS | = lv_t_fkkmavs | |
| CHANGING | ||
| C_VKNT1 | = lv_c_vknt1 | |
| C_STDBK | = lv_c_stdbk | |
| . " FKK_SAMPLE_0367 | ||
ABAP code using 7.40 inline data declarations to call FM FKK_SAMPLE_0367
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 VKNT1 FROM FKKMAGRP INTO @DATA(ld_c_vknt1). | ||||
| "SELECT single STDBK FROM FKKMAGRP INTO @DATA(ld_c_stdbk). | ||||
Search for further information about these or an SAP related objects