SAP FKK_INV_CFC_VALIDATION_INVDOC0 Function Module for
FKK_INV_CFC_VALIDATION_INVDOC0 is a standard fkk inv cfc validation invdoc0 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 inv cfc validation invdoc0 FM, simply by entering the name FKK_INV_CFC_VALIDATION_INVDOC0 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKKINV_CFC_VALIDATION
Program Name: SAPLFKKINV_CFC_VALIDATION
Main Program: SAPLFKKINV_CFC_VALIDATION
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_INV_CFC_VALIDATION_INVDOC0 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_INV_CFC_VALIDATION_INVDOC0'".
EXPORTING
I_INVDOC = "Invoicing Document
I_FKKVKP = "Contract Account Partner-Specific
* I_PROCESS = ' ' "
* I_CHECK_ONLY = ' ' "
* I_DIALOG = ' ' "Dialog Window Permitted
* I_CFCCASE_TAB = "Clarification Cases (Table for type FKKINV_CFC)
* I_INVTRIG_TAB = "Invoicing Trigger (Table for Structure FKKINV_TRIG)
IMPORTING
E_CFCCASE_NEW = "Clarification Case Invoicing
E_CFC_MSG_TAB = "Invoicing: Messages for Clarification Case
E_EXIT_ACC_INV = "Terminate Invoicing of Current Contract Account
E_USER_UNIT_ABORT = "Processing of Invoicing Unit Terminated Manually
E_USER_CLARIFIED = "
EXCEPTIONS
GENERAL_FAULT = 1
IMPORTING Parameters details for FKK_INV_CFC_VALIDATION_INVDOC0
I_INVDOC - Invoicing Document
Data type: FKKINVDOCOptional: No
Call by Reference: Yes
I_FKKVKP - Contract Account Partner-Specific
Data type: FKKVKPOptional: No
Call by Reference: Yes
I_PROCESS -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_CHECK_ONLY -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_DIALOG - Dialog Window Permitted
Data type: DIALOG_KKDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_CFCCASE_TAB - Clarification Cases (Table for type FKKINV_CFC)
Data type: FKKINV_CFC_TABOptional: Yes
Call by Reference: Yes
I_INVTRIG_TAB - Invoicing Trigger (Table for Structure FKKINV_TRIG)
Data type: FKKINV_TRIG_TABOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FKK_INV_CFC_VALIDATION_INVDOC0
E_CFCCASE_NEW - Clarification Case Invoicing
Data type: FKKINV_CFCOptional: No
Call by Reference: Yes
E_CFC_MSG_TAB - Invoicing: Messages for Clarification Case
Data type: FKKINV_CFC_MSG_TABOptional: No
Call by Reference: Yes
E_EXIT_ACC_INV - Terminate Invoicing of Current Contract Account
Data type: EXIT_ACC_INV_KKOptional: No
Call by Reference: Yes
E_USER_UNIT_ABORT - Processing of Invoicing Unit Terminated Manually
Data type: USER_UNIT_ABORT_KKOptional: No
Call by Reference: Yes
E_USER_CLARIFIED -
Data type: XFELDOptional: No
Call by Reference: Yes
EXCEPTIONS details
GENERAL_FAULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_INV_CFC_VALIDATION_INVDOC0 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_invdoc | TYPE FKKINVDOC, " | |||
| lv_e_cfccase_new | TYPE FKKINV_CFC, " | |||
| lv_general_fault | TYPE FKKINV_CFC, " | |||
| lv_i_fkkvkp | TYPE FKKVKP, " | |||
| lv_e_cfc_msg_tab | TYPE FKKINV_CFC_MSG_TAB, " | |||
| lv_i_process | TYPE C, " SPACE | |||
| lv_e_exit_acc_inv | TYPE EXIT_ACC_INV_KK, " | |||
| lv_i_check_only | TYPE XFELD, " SPACE | |||
| lv_e_user_unit_abort | TYPE USER_UNIT_ABORT_KK, " | |||
| lv_i_dialog | TYPE DIALOG_KK, " SPACE | |||
| lv_e_user_clarified | TYPE XFELD, " | |||
| lv_i_cfccase_tab | TYPE FKKINV_CFC_TAB, " | |||
| lv_i_invtrig_tab | TYPE FKKINV_TRIG_TAB. " |
|   CALL FUNCTION 'FKK_INV_CFC_VALIDATION_INVDOC0' " |
| EXPORTING | ||
| I_INVDOC | = lv_i_invdoc | |
| I_FKKVKP | = lv_i_fkkvkp | |
| I_PROCESS | = lv_i_process | |
| I_CHECK_ONLY | = lv_i_check_only | |
| I_DIALOG | = lv_i_dialog | |
| I_CFCCASE_TAB | = lv_i_cfccase_tab | |
| I_INVTRIG_TAB | = lv_i_invtrig_tab | |
| IMPORTING | ||
| E_CFCCASE_NEW | = lv_e_cfccase_new | |
| E_CFC_MSG_TAB | = lv_e_cfc_msg_tab | |
| E_EXIT_ACC_INV | = lv_e_exit_acc_inv | |
| E_USER_UNIT_ABORT | = lv_e_user_unit_abort | |
| E_USER_CLARIFIED | = lv_e_user_clarified | |
| EXCEPTIONS | ||
| GENERAL_FAULT = 1 | ||
| . " FKK_INV_CFC_VALIDATION_INVDOC0 | ||
ABAP code using 7.40 inline data declarations to call FM FKK_INV_CFC_VALIDATION_INVDOC0
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_i_process) | = ' '. | |||
| DATA(ld_i_check_only) | = ' '. | |||
| DATA(ld_i_dialog) | = ' '. | |||
Search for further information about these or an SAP related objects