SAP FI_PAYMENT_METHODS_SELECT Function Module for









FI_PAYMENT_METHODS_SELECT is a standard fi payment methods select 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 fi payment methods select FM, simply by entering the name FI_PAYMENT_METHODS_SELECT into the relevant SAP transaction such as SE37 or SE38.

Function Group: F11M
Program Name: SAPLF11M
Main Program: SAPLF11M
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FI_PAYMENT_METHODS_SELECT 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 'FI_PAYMENT_METHODS_SELECT'"
EXPORTING
I_REGUH = "
I_ZBUKR = "
I_WAERS = "
I_ZLSCH = "
I_KATEG = "
I_ZWELS = "
I_ZHLG2 = "
I_BUDAT = "Posting Date in the Document
I_XTRACE = "

IMPORTING
E_VALID_PAYMETHODS = "
E_GRP_STATUS = "

TABLES
T_XBANK = "
T_XZAHLB = "
.



IMPORTING Parameters details for FI_PAYMENT_METHODS_SELECT

I_REGUH -

Data type: REGUH
Optional: No
Call by Reference: No ( called with pass by value option)

I_ZBUKR -

Data type: ZHLG1-ZBUKR
Optional: No
Call by Reference: No ( called with pass by value option)

I_WAERS -

Data type: ZHLG1-WAERS
Optional: No
Call by Reference: No ( called with pass by value option)

I_ZLSCH -

Data type: ZHLG1-ZLSCH
Optional: No
Call by Reference: No ( called with pass by value option)

I_KATEG -

Data type: ZHLG2-KATEG
Optional: No
Call by Reference: No ( called with pass by value option)

I_ZWELS -

Data type: FIPRQ_ZHLG2-ZWELS
Optional: No
Call by Reference: No ( called with pass by value option)

I_ZHLG2 -

Data type: FIPRQ_ZHLG2
Optional: No
Call by Reference: No ( called with pass by value option)

I_BUDAT - Posting Date in the Document

Data type: F110C-BUDAT
Optional: No
Call by Reference: No ( called with pass by value option)

I_XTRACE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FI_PAYMENT_METHODS_SELECT

E_VALID_PAYMETHODS -

Data type: REGUP-ZWELS
Optional: No
Call by Reference: No ( called with pass by value option)

E_GRP_STATUS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FI_PAYMENT_METHODS_SELECT

T_XBANK -

Data type: FIPRQ_BANK_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

T_XZAHLB -

Data type: TABLE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FI_PAYMENT_METHODS_SELECT 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_reguh  TYPE REGUH, "   
lt_t_xbank  TYPE STANDARD TABLE OF FIPRQ_BANK_TAB, "   
lv_e_valid_paymethods  TYPE REGUP-ZWELS, "   
lv_i_zbukr  TYPE ZHLG1-ZBUKR, "   
lt_t_xzahlb  TYPE STANDARD TABLE OF TABLE, "   
lv_e_grp_status  TYPE TABLE, "   
lv_i_waers  TYPE ZHLG1-WAERS, "   
lv_i_zlsch  TYPE ZHLG1-ZLSCH, "   
lv_i_kateg  TYPE ZHLG2-KATEG, "   
lv_i_zwels  TYPE FIPRQ_ZHLG2-ZWELS, "   
lv_i_zhlg2  TYPE FIPRQ_ZHLG2, "   
lv_i_budat  TYPE F110C-BUDAT, "   
lv_i_xtrace  TYPE F110C. "   

  CALL FUNCTION 'FI_PAYMENT_METHODS_SELECT'  "
    EXPORTING
         I_REGUH = lv_i_reguh
         I_ZBUKR = lv_i_zbukr
         I_WAERS = lv_i_waers
         I_ZLSCH = lv_i_zlsch
         I_KATEG = lv_i_kateg
         I_ZWELS = lv_i_zwels
         I_ZHLG2 = lv_i_zhlg2
         I_BUDAT = lv_i_budat
         I_XTRACE = lv_i_xtrace
    IMPORTING
         E_VALID_PAYMETHODS = lv_e_valid_paymethods
         E_GRP_STATUS = lv_e_grp_status
    TABLES
         T_XBANK = lt_t_xbank
         T_XZAHLB = lt_t_xzahlb
. " FI_PAYMENT_METHODS_SELECT




ABAP code using 7.40 inline data declarations to call FM FI_PAYMENT_METHODS_SELECT

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 ZWELS FROM REGUP INTO @DATA(ld_e_valid_paymethods).
 
"SELECT single ZBUKR FROM ZHLG1 INTO @DATA(ld_i_zbukr).
 
 
 
"SELECT single WAERS FROM ZHLG1 INTO @DATA(ld_i_waers).
 
"SELECT single ZLSCH FROM ZHLG1 INTO @DATA(ld_i_zlsch).
 
"SELECT single KATEG FROM ZHLG2 INTO @DATA(ld_i_kateg).
 
"SELECT single ZWELS FROM FIPRQ_ZHLG2 INTO @DATA(ld_i_zwels).
 
 
"SELECT single BUDAT FROM F110C INTO @DATA(ld_i_budat).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!