SAP FI_PRINT_ZTERM Function Module for









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

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



Function FI_PRINT_ZTERM 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_PRINT_ZTERM'"
EXPORTING
* I_ZTERM = "Terms of Payment Key
* I_LANGU = SY-LANGU "Language Key
* I_XT052U = ' ' "
* I_T052 = "Term of Payment

TABLES
T_ZTEXT = "

EXCEPTIONS
ZTERM_NOT_FOUND = 1
.



IMPORTING Parameters details for FI_PRINT_ZTERM

I_ZTERM - Terms of Payment Key

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

I_LANGU - Language Key

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XT052U -

Data type: RFCU4-FLAGX
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_T052 - Term of Payment

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

TABLES Parameters details for FI_PRINT_ZTERM

T_ZTEXT -

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

EXCEPTIONS details

ZTERM_NOT_FOUND -

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

Copy and paste ABAP code example for FI_PRINT_ZTERM 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_zterm  TYPE T052-ZTERM, "   
lt_t_ztext  TYPE STANDARD TABLE OF TTEXT, "   
lv_zterm_not_found  TYPE TTEXT, "   
lv_i_langu  TYPE SY-LANGU, "   SY-LANGU
lv_i_xt052u  TYPE RFCU4-FLAGX, "   SPACE
lv_i_t052  TYPE T052. "   

  CALL FUNCTION 'FI_PRINT_ZTERM'  "
    EXPORTING
         I_ZTERM = lv_i_zterm
         I_LANGU = lv_i_langu
         I_XT052U = lv_i_xt052u
         I_T052 = lv_i_t052
    TABLES
         T_ZTEXT = lt_t_ztext
    EXCEPTIONS
        ZTERM_NOT_FOUND = 1
. " FI_PRINT_ZTERM




ABAP code using 7.40 inline data declarations to call FM FI_PRINT_ZTERM

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 ZTERM FROM T052 INTO @DATA(ld_i_zterm).
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_i_langu).
DATA(ld_i_langu) = SY-LANGU.
 
"SELECT single FLAGX FROM RFCU4 INTO @DATA(ld_i_xt052u).
DATA(ld_i_xt052u) = ' '.
 
 


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!