SAP FMPAY_PAYMENT_TRANSFER Function Module for









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

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



Function FMPAY_PAYMENT_TRANSFER 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 'FMPAY_PAYMENT_TRANSFER'"
  EXPORTING
   I_BUKRS =  "Company Code
   I_SKNTO =  "
   I_ARCH =  "
   I_GJAHR =  "Fiscal year for FI document number
   I_PSTDAT =  "Exception Posting Date for Payments
   I_PARTPY =  "Conversion of Partial Pymts/Residual Items Active (S200_OLD)
   I_TEST =  "Execute Test Run
   I_HHM =  "
   I_SELRES =  "
   I_CHPART =  "
   I_TRCHCK =  "

 IMPORTING
   E_ARCH_OK =  "

TABLES
   C_T_OUTPUT =  "Output Structure for S200_OLD
   I_T_S200_LEDGER =  "Structure of a Range Table for a (10) Character Field
   I_T_T001 =  "Structure of a Range Table for a (10) Character Field
   S_BELNR =  "Structure of a Range Table for a (10) Character Field
   S_KUNNR =  "Structure of a Range Table for a (10) Character Field
   S_LIFNR =  "Structure of a Range Table for a (10) Character Field
.



IMPORTING Parameters details for FMPAY_PAYMENT_TRANSFER

I_BUKRS - Company Code

Data type: FMIFIIT-BUKRS
Optional: No
Call by Reference: Yes

I_SKNTO -

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

I_ARCH -

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

I_GJAHR - Fiscal year for FI document number

Data type: FMIFIIT-KNGJAHR
Optional: No
Call by Reference: Yes

I_PSTDAT - Exception Posting Date for Payments

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

I_PARTPY - Conversion of Partial Pymts/Residual Items Active (S200_OLD)

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

I_TEST - Execute Test Run

Data type: LKO74-TESTLAUF
Optional: No
Call by Reference: Yes

I_HHM -

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

I_SELRES -

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

I_CHPART -

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

I_TRCHCK -

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

EXPORTING Parameters details for FMPAY_PAYMENT_TRANSFER

E_ARCH_OK -

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

TABLES Parameters details for FMPAY_PAYMENT_TRANSFER

C_T_OUTPUT - Output Structure for S200_OLD

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

I_T_S200_LEDGER - Structure of a Range Table for a (10) Character Field

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

I_T_T001 - Structure of a Range Table for a (10) Character Field

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

S_BELNR - Structure of a Range Table for a (10) Character Field

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

S_KUNNR - Structure of a Range Table for a (10) Character Field

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

S_LIFNR - Structure of a Range Table for a (10) Character Field

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

Copy and paste ABAP code example for FMPAY_PAYMENT_TRANSFER 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_bukrs  TYPE FMIFIIT-BUKRS, "   
lv_e_arch_ok  TYPE C, "   
lt_c_t_output  TYPE STANDARD TABLE OF FMOUT_S200_OLD, "   
lv_i_sknto  TYPE C, "   
lv_i_arch  TYPE C, "   
lv_i_gjahr  TYPE FMIFIIT-KNGJAHR, "   
lt_i_t_s200_ledger  TYPE STANDARD TABLE OF FMS200_OLD_LEDGER, "   
lv_i_pstdat  TYPE FM_PAYTR_PSTDAT, "   
lt_i_t_t001  TYPE STANDARD TABLE OF T001, "   
lt_s_belnr  TYPE STANDARD TABLE OF RANGE_C10, "   
lv_i_partpy  TYPE FM_PARTPAY, "   
lv_i_test  TYPE LKO74-TESTLAUF, "   
lt_s_kunnr  TYPE STANDARD TABLE OF RANGE_C10, "   
lv_i_hhm  TYPE C, "   
lt_s_lifnr  TYPE STANDARD TABLE OF RANGE_C10, "   
lv_i_selres  TYPE C, "   
lv_i_chpart  TYPE C, "   
lv_i_trchck  TYPE C. "   

  CALL FUNCTION 'FMPAY_PAYMENT_TRANSFER'  "
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_SKNTO = lv_i_sknto
         I_ARCH = lv_i_arch
         I_GJAHR = lv_i_gjahr
         I_PSTDAT = lv_i_pstdat
         I_PARTPY = lv_i_partpy
         I_TEST = lv_i_test
         I_HHM = lv_i_hhm
         I_SELRES = lv_i_selres
         I_CHPART = lv_i_chpart
         I_TRCHCK = lv_i_trchck
    IMPORTING
         E_ARCH_OK = lv_e_arch_ok
    TABLES
         C_T_OUTPUT = lt_c_t_output
         I_T_S200_LEDGER = lt_i_t_s200_ledger
         I_T_T001 = lt_i_t_t001
         S_BELNR = lt_s_belnr
         S_KUNNR = lt_s_kunnr
         S_LIFNR = lt_s_lifnr
. " FMPAY_PAYMENT_TRANSFER




ABAP code using 7.40 inline data declarations to call FM FMPAY_PAYMENT_TRANSFER

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 BUKRS FROM FMIFIIT INTO @DATA(ld_i_bukrs).
 
 
 
 
 
"SELECT single KNGJAHR FROM FMIFIIT INTO @DATA(ld_i_gjahr).
 
 
 
 
 
 
"SELECT single TESTLAUF FROM LKO74 INTO @DATA(ld_i_test).
 
 
 
 
 
 
 


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!