SAP FKK_PYMET_CHECK Function Module for Check Payment Method
FKK_PYMET_CHECK is a standard fkk pymet 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 Payment Method 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 pymet check FM, simply by entering the name FKK_PYMET_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_PYMET_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_PYMET_CHECK'"Check Payment Method.
EXPORTING
* I_LAND1 = "
* I_OPBUK = "Paying Company Code
I_PYMET = "Payment Method
* I_DIREC = "
* I_PYBUK_ITM = "
* I_PYBUK_ACC = "
* I_GPART = "Business Partner Number
* I_VKONT = "Contract Account Number
* I_FKKVKP = "Contract Account Partner-Specific
IMPORTING
E_TFK042Z = "
E_TFK042E = "
IMPORTING Parameters details for FKK_PYMET_CHECK
I_LAND1 -
Data type: TFK042Z-LAND1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_OPBUK - Paying Company Code
Data type: TFK042E-OPBUKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PYMET - Payment Method
Data type: TFK042Z-ZLSCHOptional: No
Call by Reference: No ( called with pass by value option)
I_DIREC -
Data type: TFK042Z-ZLSCHOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PYBUK_ITM -
Data type: PYBUK_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PYBUK_ACC -
Data type: PYBUK_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_GPART - Business Partner Number
Data type: GPART_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_VKONT - Contract Account Number
Data type: VKONT_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FKKVKP - Contract Account Partner-Specific
Data type: FKKVKPOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_PYMET_CHECK
E_TFK042Z -
Data type: TFK042ZOptional: No
Call by Reference: No ( called with pass by value option)
E_TFK042E -
Data type: TFK042EOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_PYMET_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_land1 | TYPE TFK042Z-LAND1, " | |||
| lv_e_tfk042z | TYPE TFK042Z, " | |||
| lv_i_opbuk | TYPE TFK042E-OPBUK, " | |||
| lv_e_tfk042e | TYPE TFK042E, " | |||
| lv_i_pymet | TYPE TFK042Z-ZLSCH, " | |||
| lv_i_direc | TYPE TFK042Z-ZLSCH, " | |||
| lv_i_pybuk_itm | TYPE PYBUK_KK, " | |||
| lv_i_pybuk_acc | TYPE PYBUK_KK, " | |||
| lv_i_gpart | TYPE GPART_KK, " | |||
| lv_i_vkont | TYPE VKONT_KK, " | |||
| lv_i_fkkvkp | TYPE FKKVKP. " |
|   CALL FUNCTION 'FKK_PYMET_CHECK' "Check Payment Method |
| EXPORTING | ||
| I_LAND1 | = lv_i_land1 | |
| I_OPBUK | = lv_i_opbuk | |
| I_PYMET | = lv_i_pymet | |
| I_DIREC | = lv_i_direc | |
| I_PYBUK_ITM | = lv_i_pybuk_itm | |
| I_PYBUK_ACC | = lv_i_pybuk_acc | |
| I_GPART | = lv_i_gpart | |
| I_VKONT | = lv_i_vkont | |
| I_FKKVKP | = lv_i_fkkvkp | |
| IMPORTING | ||
| E_TFK042Z | = lv_e_tfk042z | |
| E_TFK042E | = lv_e_tfk042e | |
| . " FKK_PYMET_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FKK_PYMET_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 LAND1 FROM TFK042Z INTO @DATA(ld_i_land1). | ||||
| "SELECT single OPBUK FROM TFK042E INTO @DATA(ld_i_opbuk). | ||||
| "SELECT single ZLSCH FROM TFK042Z INTO @DATA(ld_i_pymet). | ||||
| "SELECT single ZLSCH FROM TFK042Z INTO @DATA(ld_i_direc). | ||||
Search for further information about these or an SAP related objects