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

Function FKK_SAMPLE_6035 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_6035'".
EXPORTING
X_FIKEY = "Reconciliation Key for General Ledger
X_KEYZ1 = "Payment Lot
X_FKEYS = "
X_CSHKZ = "Cash Payment
X_CHQKZ = "Check Payment
X_CRDKZ = "
X_XEIZA = "Incoming Payment
X_XAUZA = "Outgoing Payment
IMPORTING
Y_NO_POSTINGS = "Do not Execute Posting
Y_DISPLAY = "Line Item Displayed on the Screen
Y_KEYZ1 = "Payment Lot
Y_FKEYS = "
Y_FIKEY = "Reconciliation Key
IMPORTING Parameters details for FKK_SAMPLE_6035
X_FIKEY - Reconciliation Key for General Ledger
Data type: RFKH0-FIKEYOptional: No
Call by Reference: Yes
X_KEYZ1 - Payment Lot
Data type: RFKH2-KEYZ1Optional: No
Call by Reference: Yes
X_FKEYS -
Data type: RFKH2-FKEYSOptional: No
Call by Reference: Yes
X_CSHKZ - Cash Payment
Data type: RFKH0-CSHKZOptional: No
Call by Reference: Yes
X_CHQKZ - Check Payment
Data type: RFKH0-CHQKZOptional: No
Call by Reference: Yes
X_CRDKZ -
Data type: RFKH0-CRDKZOptional: No
Call by Reference: Yes
X_XEIZA - Incoming Payment
Data type: RFKH0-XEIZAOptional: No
Call by Reference: Yes
X_XAUZA - Outgoing Payment
Data type: RFKH0-XAUZAOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FKK_SAMPLE_6035
Y_NO_POSTINGS - Do not Execute Posting
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
Y_DISPLAY - Line Item Displayed on the Screen
Data type: RFKH0-AZEI1Optional: No
Call by Reference: Yes
Y_KEYZ1 - Payment Lot
Data type: RFKH2-KEYZ1Optional: No
Call by Reference: Yes
Y_FKEYS -
Data type: RFKH2-FKEYSOptional: No
Call by Reference: Yes
Y_FIKEY - Reconciliation Key
Data type: RFKH0-FIKEYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_SAMPLE_6035 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_x_fikey | TYPE RFKH0-FIKEY, " | |||
| lv_y_no_postings | TYPE BOOLE-BOOLE, " | |||
| lv_x_keyz1 | TYPE RFKH2-KEYZ1, " | |||
| lv_y_display | TYPE RFKH0-AZEI1, " | |||
| lv_x_fkeys | TYPE RFKH2-FKEYS, " | |||
| lv_y_keyz1 | TYPE RFKH2-KEYZ1, " | |||
| lv_x_cshkz | TYPE RFKH0-CSHKZ, " | |||
| lv_y_fkeys | TYPE RFKH2-FKEYS, " | |||
| lv_x_chqkz | TYPE RFKH0-CHQKZ, " | |||
| lv_y_fikey | TYPE RFKH0-FIKEY, " | |||
| lv_x_crdkz | TYPE RFKH0-CRDKZ, " | |||
| lv_x_xeiza | TYPE RFKH0-XEIZA, " | |||
| lv_x_xauza | TYPE RFKH0-XAUZA. " |
|   CALL FUNCTION 'FKK_SAMPLE_6035' " |
| EXPORTING | ||
| X_FIKEY | = lv_x_fikey | |
| X_KEYZ1 | = lv_x_keyz1 | |
| X_FKEYS | = lv_x_fkeys | |
| X_CSHKZ | = lv_x_cshkz | |
| X_CHQKZ | = lv_x_chqkz | |
| X_CRDKZ | = lv_x_crdkz | |
| X_XEIZA | = lv_x_xeiza | |
| X_XAUZA | = lv_x_xauza | |
| IMPORTING | ||
| Y_NO_POSTINGS | = lv_y_no_postings | |
| Y_DISPLAY | = lv_y_display | |
| Y_KEYZ1 | = lv_y_keyz1 | |
| Y_FKEYS | = lv_y_fkeys | |
| Y_FIKEY | = lv_y_fikey | |
| . " FKK_SAMPLE_6035 | ||
ABAP code using 7.40 inline data declarations to call FM FKK_SAMPLE_6035
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 FIKEY FROM RFKH0 INTO @DATA(ld_x_fikey). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_y_no_postings). | ||||
| "SELECT single KEYZ1 FROM RFKH2 INTO @DATA(ld_x_keyz1). | ||||
| "SELECT single AZEI1 FROM RFKH0 INTO @DATA(ld_y_display). | ||||
| "SELECT single FKEYS FROM RFKH2 INTO @DATA(ld_x_fkeys). | ||||
| "SELECT single KEYZ1 FROM RFKH2 INTO @DATA(ld_y_keyz1). | ||||
| "SELECT single CSHKZ FROM RFKH0 INTO @DATA(ld_x_cshkz). | ||||
| "SELECT single FKEYS FROM RFKH2 INTO @DATA(ld_y_fkeys). | ||||
| "SELECT single CHQKZ FROM RFKH0 INTO @DATA(ld_x_chqkz). | ||||
| "SELECT single FIKEY FROM RFKH0 INTO @DATA(ld_y_fikey). | ||||
| "SELECT single CRDKZ FROM RFKH0 INTO @DATA(ld_x_crdkz). | ||||
| "SELECT single XEIZA FROM RFKH0 INTO @DATA(ld_x_xeiza). | ||||
| "SELECT single XAUZA FROM RFKH0 INTO @DATA(ld_x_xauza). | ||||
Search for further information about these or an SAP related objects