SAP SD_PRINT_TERMS_OF_PAYMENT Function Module for Format Terms of Payment According to Table 052

Search SAP Function Modules

SD_PRINT_TERMS_OF_PAYMENT is a standard sd print terms of payment SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Format Terms of Payment According to Table 052 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 sd print terms of payment FM, simply by entering the name SD_PRINT_TERMS_OF_PAYMENT into the relevant SAP transaction such as SE37 or SE38.

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

Function SD_PRINT_TERMS_OF_PAYMENT 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 'SD_PRINT_TERMS_OF_PAYMENT'"Format Terms of Payment According to Table 052
  EXPORTING
*  BLDAT = 00000000 "Document date
*  BUDAT = 00000000 "Posting date
*  CPUDT = 00000000 "CPU date
*  LANGUAGE = ' ' "Language
   TERMS_OF_PAYMENT =  "Terms of payment key
*  COUNTRY = ' ' "
*  HOLDBACK = ' ' "
*  TOP_HOLDBACK_INFO =  "
*  DOCUMENT_CURRENCY = ' ' "

 IMPORTING
   BASELINE_DATE =  "Baseline date for payment
   PAYMENT_SPLIT =  "
   ZFBDT =  "

TABLES
   TOP_TEXT =  "Table with text for terms of payment

EXCEPTIONS
   TERMS_OF_PAYMENT_NOT_IN_T052 = 1 

.

IMPORTING Parameters details for SD_PRINT_TERMS_OF_PAYMENT

BLDAT - Document date

Data type: VBRK-ERDAT
Default: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)

BUDAT - Posting date

Data type: VBRK-FKDAT
Default: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)

CPUDT - CPU date

Data type: VBRK-ERDAT
Default: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE - Language

Data type: NAST-SPRAS
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TERMS_OF_PAYMENT - Terms of payment key

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

COUNTRY -

Data type: KNA1-LAND1
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

HOLDBACK -

Data type: VBDKR-P_SPLIT
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TOP_HOLDBACK_INFO -

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

DOCUMENT_CURRENCY -

Data type: VBRK-WAERK
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SD_PRINT_TERMS_OF_PAYMENT

BASELINE_DATE - Baseline date for payment

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

PAYMENT_SPLIT -

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

ZFBDT -

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

TABLES Parameters details for SD_PRINT_TERMS_OF_PAYMENT

TOP_TEXT - Table with text for terms of payment

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

EXCEPTIONS details

TERMS_OF_PAYMENT_NOT_IN_T052 -

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

Copy and paste ABAP code example for SD_PRINT_TERMS_OF_PAYMENT 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.

ABAP code using 7.40 inline data declarations to call FM SD_PRINT_TERMS_OF_PAYMENT

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