SAP FKK_FKKOP_COMPLETE_CHECK Function Module for Check FKKOP Item
FKK_FKKOP_COMPLETE_CHECK is a standard fkk fkkop complete check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check FKKOP Item 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 fkk fkkop complete check FM, simply by entering the name FKK_FKKOP_COMPLETE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKB3
Program Name: SAPLFKB3
Main Program: SAPLFKB3
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_FKKOP_COMPLETE_CHECK 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_FKKOP_COMPLETE_CHECK'"Check FKKOP Item.
EXPORTING
I_FKKKO = "Document Header
I_FKKOP = "Posting Date
* I_WARNINGS = ' ' "Output warnings?
* I_ACTVT = '01' "Activity: 01 Post 02 Change 03 Display
* I_NO_LOCK_CHECK = "'X' No Posting Lock Check
* I_CHECK_MODE = ' ' "Check Mode (01 Do Not Check Bank Details)
IMPORTING
E_FKKHKONT = "General Ledger Account Control Data
E_PERIOD_MESSAGES = "
TABLES
* T_FKKOPW = "Repetition Specifications
IMPORTING Parameters details for FKK_FKKOP_COMPLETE_CHECK
I_FKKKO - Document Header
Data type: FKKKOOptional: No
Call by Reference: No ( called with pass by value option)
I_FKKOP - Posting Date
Data type: FKKOPOptional: No
Call by Reference: No ( called with pass by value option)
I_WARNINGS - Output warnings?
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTVT - Activity: 01 Post 02 Change 03 Display
Data type: TACT-ACTVTDefault: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NO_LOCK_CHECK - 'X' No Posting Lock Check
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CHECK_MODE - Check Mode (01 Do Not Check Bank Details)
Data type: CHKMD_KKDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_FKKOP_COMPLETE_CHECK
E_FKKHKONT - General Ledger Account Control Data
Data type: FKKHKONTOptional: No
Call by Reference: No ( called with pass by value option)
E_PERIOD_MESSAGES -
Data type: FKKWNPEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FKK_FKKOP_COMPLETE_CHECK
T_FKKOPW - Repetition Specifications
Data type: FKKOPWOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_FKKOP_COMPLETE_CHECK 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_fkkko | TYPE FKKKO, " | |||
| lt_t_fkkopw | TYPE STANDARD TABLE OF FKKOPW, " | |||
| lv_e_fkkhkont | TYPE FKKHKONT, " | |||
| lv_i_fkkop | TYPE FKKOP, " | |||
| lv_e_period_messages | TYPE FKKWNPER, " | |||
| lv_i_warnings | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_actvt | TYPE TACT-ACTVT, " '01' | |||
| lv_i_no_lock_check | TYPE BOOLE-BOOLE, " | |||
| lv_i_check_mode | TYPE CHKMD_KK. " SPACE |
|   CALL FUNCTION 'FKK_FKKOP_COMPLETE_CHECK' "Check FKKOP Item |
| EXPORTING | ||
| I_FKKKO | = lv_i_fkkko | |
| I_FKKOP | = lv_i_fkkop | |
| I_WARNINGS | = lv_i_warnings | |
| I_ACTVT | = lv_i_actvt | |
| I_NO_LOCK_CHECK | = lv_i_no_lock_check | |
| I_CHECK_MODE | = lv_i_check_mode | |
| IMPORTING | ||
| E_FKKHKONT | = lv_e_fkkhkont | |
| E_PERIOD_MESSAGES | = lv_e_period_messages | |
| TABLES | ||
| T_FKKOPW | = lt_t_fkkopw | |
| . " FKK_FKKOP_COMPLETE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FKK_FKKOP_COMPLETE_CHECK
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 BOOLE FROM BOOLE INTO @DATA(ld_i_warnings). | ||||
| DATA(ld_i_warnings) | = ' '. | |||
| "SELECT single ACTVT FROM TACT INTO @DATA(ld_i_actvt). | ||||
| DATA(ld_i_actvt) | = '01'. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_no_lock_check). | ||||
| DATA(ld_i_check_mode) | = ' '. | |||
Search for further information about these or an SAP related objects