SAP PAYMENT_FORM_PRINT Function Module for









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

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



Function PAYMENT_FORM_PRINT 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 'PAYMENT_FORM_PRINT'"
EXPORTING
I_OPAYF = "Print Parameter
I_VBLNR = "Payment document number
* I_REPRI = "
* I_WWERT = "Translation Date
* I_CC_CURR = "Currency Key

IMPORTING
EB_PRINT_ALLOWED = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
.



IMPORTING Parameters details for PAYMENT_FORM_PRINT

I_OPAYF - Print Parameter

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

I_VBLNR - Payment document number

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

I_REPRI -

Data type: BOOLE_D
Optional: Yes
Call by Reference: Yes

I_WWERT - Translation Date

Data type: BKPF-WWERT
Optional: Yes
Call by Reference: Yes

I_CC_CURR - Currency Key

Data type: T001-WAERS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PAYMENT_FORM_PRINT

EB_PRINT_ALLOWED - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

Copy and paste ABAP code example for PAYMENT_FORM_PRINT 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_opayf  TYPE OPAYF, "   
lv_eb_print_allowed  TYPE BOOLE_D, "   
lv_i_vblnr  TYPE REGUH-VBLNR, "   
lv_i_repri  TYPE BOOLE_D, "   
lv_i_wwert  TYPE BKPF-WWERT, "   
lv_i_cc_curr  TYPE T001-WAERS. "   

  CALL FUNCTION 'PAYMENT_FORM_PRINT'  "
    EXPORTING
         I_OPAYF = lv_i_opayf
         I_VBLNR = lv_i_vblnr
         I_REPRI = lv_i_repri
         I_WWERT = lv_i_wwert
         I_CC_CURR = lv_i_cc_curr
    IMPORTING
         EB_PRINT_ALLOWED = lv_eb_print_allowed
. " PAYMENT_FORM_PRINT




ABAP code using 7.40 inline data declarations to call FM PAYMENT_FORM_PRINT

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 VBLNR FROM REGUH INTO @DATA(ld_i_vblnr).
 
 
"SELECT single WWERT FROM BKPF INTO @DATA(ld_i_wwert).
 
"SELECT single WAERS FROM T001 INTO @DATA(ld_i_cc_curr).
 


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!