SAP LOAD_FONT Function Module for
LOAD_FONT is a standard load font 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 load font FM, simply by entering the name LOAD_FONT into the relevant SAP transaction such as SE37 or SE38.
Function Group: STXG
Program Name: SAPLSTXG
Main Program: SAPLSTXG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LOAD_FONT 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 'LOAD_FONT'".
EXPORTING
BOLD = "Flag for bold type
FAMILY = "Font family
HEIGHT = "Font size
ITALIC = "Flag for italics
PRINTER = "Printer destination
* CODEPAGE = 0000 "
IMPORTING
FONT_HEADER = "Font header data
RESULT = "Result
TABLES
METRIC = "Character metric table
EXCEPTIONS
FONT_FAMILY = 1 CODEPAGE = 2 DEVICE_TYPE = 3
IMPORTING Parameters details for LOAD_FONT
BOLD - Flag for bold type
Data type: ITCFH-TDBOLDOptional: No
Call by Reference: No ( called with pass by value option)
FAMILY - Font family
Data type: ITCFH-TDFAMILYOptional: No
Call by Reference: No ( called with pass by value option)
HEIGHT - Font size
Data type: ITCFH-TDHEIGHTOptional: No
Call by Reference: No ( called with pass by value option)
ITALIC - Flag for italics
Data type: ITCFH-TDITALICOptional: No
Call by Reference: No ( called with pass by value option)
PRINTER - Printer destination
Data type: TSP0A-PATYPEOptional: No
Call by Reference: No ( called with pass by value option)
CODEPAGE -
Data type: TCP00-CPCODEPAGEDefault: 0000
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LOAD_FONT
FONT_HEADER - Font header data
Data type: ITCFHOptional: No
Call by Reference: No ( called with pass by value option)
RESULT - Result
Data type: ITCRSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for LOAD_FONT
METRIC - Character metric table
Data type: ITCFCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FONT_FAMILY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CODEPAGE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DEVICE_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LOAD_FONT 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_bold | TYPE ITCFH-TDBOLD, " | |||
| lt_metric | TYPE STANDARD TABLE OF ITCFC, " | |||
| lv_font_family | TYPE ITCFC, " | |||
| lv_font_header | TYPE ITCFH, " | |||
| lv_family | TYPE ITCFH-TDFAMILY, " | |||
| lv_result | TYPE ITCRS, " | |||
| lv_codepage | TYPE ITCRS, " | |||
| lv_height | TYPE ITCFH-TDHEIGHT, " | |||
| lv_device_type | TYPE ITCFH, " | |||
| lv_italic | TYPE ITCFH-TDITALIC, " | |||
| lv_printer | TYPE TSP0A-PATYPE, " | |||
| lv_codepage | TYPE TCP00-CPCODEPAGE. " 0000 |
|   CALL FUNCTION 'LOAD_FONT' " |
| EXPORTING | ||
| BOLD | = lv_bold | |
| FAMILY | = lv_family | |
| HEIGHT | = lv_height | |
| ITALIC | = lv_italic | |
| PRINTER | = lv_printer | |
| CODEPAGE | = lv_codepage | |
| IMPORTING | ||
| FONT_HEADER | = lv_font_header | |
| RESULT | = lv_result | |
| TABLES | ||
| METRIC | = lt_metric | |
| EXCEPTIONS | ||
| FONT_FAMILY = 1 | ||
| CODEPAGE = 2 | ||
| DEVICE_TYPE = 3 | ||
| . " LOAD_FONT | ||
ABAP code using 7.40 inline data declarations to call FM LOAD_FONT
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 TDBOLD FROM ITCFH INTO @DATA(ld_bold). | ||||
| "SELECT single TDFAMILY FROM ITCFH INTO @DATA(ld_family). | ||||
| "SELECT single TDHEIGHT FROM ITCFH INTO @DATA(ld_height). | ||||
| "SELECT single TDITALIC FROM ITCFH INTO @DATA(ld_italic). | ||||
| "SELECT single PATYPE FROM TSP0A INTO @DATA(ld_printer). | ||||
| "SELECT single CPCODEPAGE FROM TCP00 INTO @DATA(ld_codepage). | ||||
| DATA(ld_codepage) | = 0000. | |||
Search for further information about these or an SAP related objects