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

Function FKK_FILL_PAYMO 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_FILL_PAYMO'".
EXPORTING
* I_ANRED = ' ' "
I_RBBTR = "
I_RWBBT = "
* I_AVSID = "
I_FORMKEY = "
* I_APPLK = "
* I_GPART = "
* I_VKONT = "
* I_NRZAS = "
I_PNAME1 = "
I_PNAME2 = "
I_PNAME3 = "
I_PNAME4 = "
I_BUS020_EXT = "
I_BUKRS = "
I_SPRAS = "
I_WAERS = "
IMPORTING
E_PAYMO = "
EXCEPTIONS
NO_PRINT = 1 NO_APPLIKATION = 2 NO_POSTING_AREA_X100 = 3
IMPORTING Parameters details for FKK_FILL_PAYMO
I_ANRED -
Data type: PAYMI-ANREDDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_RBBTR -
Data type: PAYMI-RBBTROptional: No
Call by Reference: Yes
I_RWBBT -
Data type: PAYMI-RWBBTOptional: No
Call by Reference: Yes
I_AVSID -
Data type: PAYMI-AVSIDOptional: Yes
Call by Reference: Yes
I_FORMKEY -
Data type: EFRM-FORMKEYOptional: No
Call by Reference: Yes
I_APPLK -
Data type: FKKOP-APPLKOptional: Yes
Call by Reference: Yes
I_GPART -
Data type: FKKOP-GPARTOptional: Yes
Call by Reference: Yes
I_VKONT -
Data type: FKKOP-VKONTOptional: Yes
Call by Reference: Yes
I_NRZAS -
Data type: DFKKZR-NRZASOptional: Yes
Call by Reference: Yes
I_PNAME1 -
Data type: PAYMI-NAME1Optional: No
Call by Reference: Yes
I_PNAME2 -
Data type: PAYMI-NAME2Optional: No
Call by Reference: Yes
I_PNAME3 -
Data type: PAYMI-NAME3Optional: No
Call by Reference: Yes
I_PNAME4 -
Data type: PAYMI-NAME4Optional: No
Call by Reference: Yes
I_BUS020_EXT -
Data type: BUS020_EXTOptional: No
Call by Reference: Yes
I_BUKRS -
Data type: PAYMI-BUKRSOptional: No
Call by Reference: Yes
I_SPRAS -
Data type: PAYMI-SPRASOptional: No
Call by Reference: Yes
I_WAERS -
Data type: PAYMI-WAERSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FKK_FILL_PAYMO
E_PAYMO -
Data type: PAYMOOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_PRINT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_APPLIKATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_POSTING_AREA_X100 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_FILL_PAYMO 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_e_paymo | TYPE PAYMO, " | |||
| lv_i_anred | TYPE PAYMI-ANRED, " SPACE | |||
| lv_no_print | TYPE PAYMI, " | |||
| lv_i_rbbtr | TYPE PAYMI-RBBTR, " | |||
| lv_i_rwbbt | TYPE PAYMI-RWBBT, " | |||
| lv_i_avsid | TYPE PAYMI-AVSID, " | |||
| lv_i_formkey | TYPE EFRM-FORMKEY, " | |||
| lv_i_applk | TYPE FKKOP-APPLK, " | |||
| lv_i_gpart | TYPE FKKOP-GPART, " | |||
| lv_i_vkont | TYPE FKKOP-VKONT, " | |||
| lv_i_nrzas | TYPE DFKKZR-NRZAS, " | |||
| lv_i_pname1 | TYPE PAYMI-NAME1, " | |||
| lv_no_applikation | TYPE PAYMI, " | |||
| lv_i_pname2 | TYPE PAYMI-NAME2, " | |||
| lv_no_posting_area_x100 | TYPE PAYMI, " | |||
| lv_i_pname3 | TYPE PAYMI-NAME3, " | |||
| lv_i_pname4 | TYPE PAYMI-NAME4, " | |||
| lv_i_bus020_ext | TYPE BUS020_EXT, " | |||
| lv_i_bukrs | TYPE PAYMI-BUKRS, " | |||
| lv_i_spras | TYPE PAYMI-SPRAS, " | |||
| lv_i_waers | TYPE PAYMI-WAERS. " |
|   CALL FUNCTION 'FKK_FILL_PAYMO' " |
| EXPORTING | ||
| I_ANRED | = lv_i_anred | |
| I_RBBTR | = lv_i_rbbtr | |
| I_RWBBT | = lv_i_rwbbt | |
| I_AVSID | = lv_i_avsid | |
| I_FORMKEY | = lv_i_formkey | |
| I_APPLK | = lv_i_applk | |
| I_GPART | = lv_i_gpart | |
| I_VKONT | = lv_i_vkont | |
| I_NRZAS | = lv_i_nrzas | |
| I_PNAME1 | = lv_i_pname1 | |
| I_PNAME2 | = lv_i_pname2 | |
| I_PNAME3 | = lv_i_pname3 | |
| I_PNAME4 | = lv_i_pname4 | |
| I_BUS020_EXT | = lv_i_bus020_ext | |
| I_BUKRS | = lv_i_bukrs | |
| I_SPRAS | = lv_i_spras | |
| I_WAERS | = lv_i_waers | |
| IMPORTING | ||
| E_PAYMO | = lv_e_paymo | |
| EXCEPTIONS | ||
| NO_PRINT = 1 | ||
| NO_APPLIKATION = 2 | ||
| NO_POSTING_AREA_X100 = 3 | ||
| . " FKK_FILL_PAYMO | ||
ABAP code using 7.40 inline data declarations to call FM FKK_FILL_PAYMO
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 ANRED FROM PAYMI INTO @DATA(ld_i_anred). | ||||
| DATA(ld_i_anred) | = ' '. | |||
| "SELECT single RBBTR FROM PAYMI INTO @DATA(ld_i_rbbtr). | ||||
| "SELECT single RWBBT FROM PAYMI INTO @DATA(ld_i_rwbbt). | ||||
| "SELECT single AVSID FROM PAYMI INTO @DATA(ld_i_avsid). | ||||
| "SELECT single FORMKEY FROM EFRM INTO @DATA(ld_i_formkey). | ||||
| "SELECT single APPLK FROM FKKOP INTO @DATA(ld_i_applk). | ||||
| "SELECT single GPART FROM FKKOP INTO @DATA(ld_i_gpart). | ||||
| "SELECT single VKONT FROM FKKOP INTO @DATA(ld_i_vkont). | ||||
| "SELECT single NRZAS FROM DFKKZR INTO @DATA(ld_i_nrzas). | ||||
| "SELECT single NAME1 FROM PAYMI INTO @DATA(ld_i_pname1). | ||||
| "SELECT single NAME2 FROM PAYMI INTO @DATA(ld_i_pname2). | ||||
| "SELECT single NAME3 FROM PAYMI INTO @DATA(ld_i_pname3). | ||||
| "SELECT single NAME4 FROM PAYMI INTO @DATA(ld_i_pname4). | ||||
| "SELECT single BUKRS FROM PAYMI INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single SPRAS FROM PAYMI INTO @DATA(ld_i_spras). | ||||
| "SELECT single WAERS FROM PAYMI INTO @DATA(ld_i_waers). | ||||
Search for further information about these or an SAP related objects