SAP FMFG_SET_PAYMENT_METHOD Function Module for Set payment methode for 0$ transactions
FMFG_SET_PAYMENT_METHOD is a standard fmfg set payment method SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set payment methode for 0$ transactions 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 fmfg set payment method FM, simply by entering the name FMFG_SET_PAYMENT_METHOD into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMFG_PAYMENT_CORE
Program Name: SAPLFMFG_PAYMENT_CORE
Main Program: SAPLFMFG_PAYMENT_CORE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMFG_SET_PAYMENT_METHOD 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 'FMFG_SET_PAYMENT_METHOD'"Set payment methode for 0$ transactions.
EXPORTING
IM_REGUH = "Settlement data from payment program
* IM_REGUP = "Processed items from payment program
IMPORTING
EX_RZAWE = "Payment Method for This Payment
EX_UBNKL = "Bank number of our bank
EX_UZAWE = "Payment Method Supplement
EX_HBKID = "Short Key for a House Bank
EX_HKTID = "ID for Account Details
EX_UBHKT = "G/L Account Number for Our Bank Account / Bank Sub-Account
EX_UBKON = "Bank control key at our bank
EX_UBNKS = "Bank country key
EX_UBNKY = "Bank key of our bank
EX_UBKNT = "Our account number at the bank
IMPORTING Parameters details for FMFG_SET_PAYMENT_METHOD
IM_REGUH - Settlement data from payment program
Data type: REGUHOptional: No
Call by Reference: Yes
IM_REGUP - Processed items from payment program
Data type: REGUPOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FMFG_SET_PAYMENT_METHOD
EX_RZAWE - Payment Method for This Payment
Data type: RZAWEOptional: No
Call by Reference: Yes
EX_UBNKL - Bank number of our bank
Data type: UBNKLOptional: No
Call by Reference: Yes
EX_UZAWE - Payment Method Supplement
Data type: UZAWEOptional: No
Call by Reference: Yes
EX_HBKID - Short Key for a House Bank
Data type: HBKIDOptional: No
Call by Reference: Yes
EX_HKTID - ID for Account Details
Data type: HKTIDOptional: No
Call by Reference: Yes
EX_UBHKT - G/L Account Number for Our Bank Account / Bank Sub-Account
Data type: UBHKTOptional: No
Call by Reference: Yes
EX_UBKON - Bank control key at our bank
Data type: UBKONOptional: No
Call by Reference: Yes
EX_UBNKS - Bank country key
Data type: BANKSOptional: No
Call by Reference: Yes
EX_UBNKY - Bank key of our bank
Data type: UBNKYOptional: No
Call by Reference: Yes
EX_UBKNT - Our account number at the bank
Data type: UBKNTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMFG_SET_PAYMENT_METHOD 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_ex_rzawe | TYPE RZAWE, " | |||
| lv_im_reguh | TYPE REGUH, " | |||
| lv_ex_ubnkl | TYPE UBNKL, " | |||
| lv_ex_uzawe | TYPE UZAWE, " | |||
| lv_im_regup | TYPE REGUP, " | |||
| lv_ex_hbkid | TYPE HBKID, " | |||
| lv_ex_hktid | TYPE HKTID, " | |||
| lv_ex_ubhkt | TYPE UBHKT, " | |||
| lv_ex_ubkon | TYPE UBKON, " | |||
| lv_ex_ubnks | TYPE BANKS, " | |||
| lv_ex_ubnky | TYPE UBNKY, " | |||
| lv_ex_ubknt | TYPE UBKNT. " |
|   CALL FUNCTION 'FMFG_SET_PAYMENT_METHOD' "Set payment methode for 0$ transactions |
| EXPORTING | ||
| IM_REGUH | = lv_im_reguh | |
| IM_REGUP | = lv_im_regup | |
| IMPORTING | ||
| EX_RZAWE | = lv_ex_rzawe | |
| EX_UBNKL | = lv_ex_ubnkl | |
| EX_UZAWE | = lv_ex_uzawe | |
| EX_HBKID | = lv_ex_hbkid | |
| EX_HKTID | = lv_ex_hktid | |
| EX_UBHKT | = lv_ex_ubhkt | |
| EX_UBKON | = lv_ex_ubkon | |
| EX_UBNKS | = lv_ex_ubnks | |
| EX_UBNKY | = lv_ex_ubnky | |
| EX_UBKNT | = lv_ex_ubknt | |
| . " FMFG_SET_PAYMENT_METHOD | ||
ABAP code using 7.40 inline data declarations to call FM FMFG_SET_PAYMENT_METHOD
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.Search for further information about these or an SAP related objects