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

Function FKK_SAMPLE_5085 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_5085'".
EXPORTING
I_GPART = "Business Partner Number
I_VKONT = "Contract Account Number
I_VTREF = "Reference Specifications from Contract
* I_SUBAP = "Subapplication in Contract Accounts Receivable and Payable
I_OPBEL = "Number of a Contract Accounts Receivable and Payable Document
I_BATCH = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
CHANGING
* C_NO_COLL_BILL_ITEMS = ' ' "
TABLES
T_SELTAB = "Table with Selection Conditions ->
* T_BUKTAB = "Table of Company Codes ->
* T_AGRTAB = "Table of Permitted Clearing Restrictions
IMPORTING Parameters details for FKK_SAMPLE_5085
I_GPART - Business Partner Number
Data type: FKKOP-GPARTOptional: No
Call by Reference: Yes
I_VKONT - Contract Account Number
Data type: FKKOP-VKONTOptional: No
Call by Reference: Yes
I_VTREF - Reference Specifications from Contract
Data type: FKKOP-VTREFOptional: No
Call by Reference: Yes
I_SUBAP - Subapplication in Contract Accounts Receivable and Payable
Data type: FKKOP-SUBAPOptional: Yes
Call by Reference: Yes
I_OPBEL - Number of a Contract Accounts Receivable and Payable Document
Data type: FKKOP-OPBELOptional: No
Call by Reference: Yes
I_BATCH - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
CHANGING Parameters details for FKK_SAMPLE_5085
C_NO_COLL_BILL_ITEMS -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for FKK_SAMPLE_5085
T_SELTAB - Table with Selection Conditions ->
Data type: ISELTABOptional: No
Call by Reference: Yes
T_BUKTAB - Table of Company Codes ->
Data type: IBUKTABOptional: Yes
Call by Reference: Yes
T_AGRTAB - Table of Permitted Clearing Restrictions
Data type: IAGRTABOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FKK_SAMPLE_5085 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_gpart | TYPE FKKOP-GPART, " | |||
| lt_t_seltab | TYPE STANDARD TABLE OF ISELTAB, " | |||
| lv_c_no_coll_bill_items | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_vkont | TYPE FKKOP-VKONT, " | |||
| lt_t_buktab | TYPE STANDARD TABLE OF IBUKTAB, " | |||
| lv_i_vtref | TYPE FKKOP-VTREF, " | |||
| lt_t_agrtab | TYPE STANDARD TABLE OF IAGRTAB, " | |||
| lv_i_subap | TYPE FKKOP-SUBAP, " | |||
| lv_i_opbel | TYPE FKKOP-OPBEL, " | |||
| lv_i_batch | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'FKK_SAMPLE_5085' " |
| EXPORTING | ||
| I_GPART | = lv_i_gpart | |
| I_VKONT | = lv_i_vkont | |
| I_VTREF | = lv_i_vtref | |
| I_SUBAP | = lv_i_subap | |
| I_OPBEL | = lv_i_opbel | |
| I_BATCH | = lv_i_batch | |
| CHANGING | ||
| C_NO_COLL_BILL_ITEMS | = lv_c_no_coll_bill_items | |
| TABLES | ||
| T_SELTAB | = lt_t_seltab | |
| T_BUKTAB | = lt_t_buktab | |
| T_AGRTAB | = lt_t_agrtab | |
| . " FKK_SAMPLE_5085 | ||
ABAP code using 7.40 inline data declarations to call FM FKK_SAMPLE_5085
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 GPART FROM FKKOP INTO @DATA(ld_i_gpart). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_c_no_coll_bill_items). | ||||
| DATA(ld_c_no_coll_bill_items) | = ' '. | |||
| "SELECT single VKONT FROM FKKOP INTO @DATA(ld_i_vkont). | ||||
| "SELECT single VTREF FROM FKKOP INTO @DATA(ld_i_vtref). | ||||
| "SELECT single SUBAP FROM FKKOP INTO @DATA(ld_i_subap). | ||||
| "SELECT single OPBEL FROM FKKOP INTO @DATA(ld_i_opbel). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_batch). | ||||
Search for further information about these or an SAP related objects