SAP AFM_EDIT Function Module for Maintain SAPscript fonts: Edit an AFM file
AFM_EDIT is a standard afm edit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Maintain SAPscript fonts: Edit an AFM file 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 afm edit FM, simply by entering the name AFM_EDIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: STXF
Program Name: SAPLSTXF
Main Program: SAPLSTXF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function AFM_EDIT 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 'AFM_EDIT'"Maintain SAPscript fonts: Edit an AFM file.
EXPORTING
BOLD = "Flag for bold type
* DISPLAY = ' ' "Case <> space, only display of the
FAMILY = "Font family
HEIGHT = "Font size
ITALIC = "Flag for italics
PRINTER = "Printer destination
* USELINES = ' ' "If <> space table LINES is used
TABLES
LINES = "Text table with AFM font metric da
EXCEPTIONS
SAVED_AFM = 1 ERR_TOO_MANY_LINES = 2
IMPORTING Parameters details for AFM_EDIT
BOLD - Flag for bold type
Data type: TFO03-TDBOLDOptional: No
Call by Reference: No ( called with pass by value option)
DISPLAY - Case <> space, only display of the
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FAMILY - Font family
Data type: TFO03-TDFAMILYOptional: No
Call by Reference: No ( called with pass by value option)
HEIGHT - Font size
Data type: TFO03-TDFONTSIZEOptional: No
Call by Reference: No ( called with pass by value option)
ITALIC - Flag for italics
Data type: TFO03-TDITALICOptional: No
Call by Reference: No ( called with pass by value option)
PRINTER - Printer destination
Data type: TFO03-TDPRINTEROptional: No
Call by Reference: No ( called with pass by value option)
USELINES - If <> space table LINES is used
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for AFM_EDIT
LINES - Text table with AFM font metric da
Data type: AFMLNOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SAVED_AFM - The AFM file was saved by the user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERR_TOO_MANY_LINES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AFM_EDIT 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 TFO03-TDBOLD, " | |||
lt_lines | TYPE STANDARD TABLE OF AFMLN, " | |||
lv_saved_afm | TYPE AFMLN, " | |||
lv_display | TYPE AFMLN, " SPACE | |||
lv_err_too_many_lines | TYPE AFMLN, " | |||
lv_family | TYPE TFO03-TDFAMILY, " | |||
lv_height | TYPE TFO03-TDFONTSIZE, " | |||
lv_italic | TYPE TFO03-TDITALIC, " | |||
lv_printer | TYPE TFO03-TDPRINTER, " | |||
lv_uselines | TYPE TFO03. " SPACE |
  CALL FUNCTION 'AFM_EDIT' "Maintain SAPscript fonts: Edit an AFM file |
EXPORTING | ||
BOLD | = lv_bold | |
DISPLAY | = lv_display | |
FAMILY | = lv_family | |
HEIGHT | = lv_height | |
ITALIC | = lv_italic | |
PRINTER | = lv_printer | |
USELINES | = lv_uselines | |
TABLES | ||
LINES | = lt_lines | |
EXCEPTIONS | ||
SAVED_AFM = 1 | ||
ERR_TOO_MANY_LINES = 2 | ||
. " AFM_EDIT |
ABAP code using 7.40 inline data declarations to call FM AFM_EDIT
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 TFO03 INTO @DATA(ld_bold). | ||||
DATA(ld_display) | = ' '. | |||
"SELECT single TDFAMILY FROM TFO03 INTO @DATA(ld_family). | ||||
"SELECT single TDFONTSIZE FROM TFO03 INTO @DATA(ld_height). | ||||
"SELECT single TDITALIC FROM TFO03 INTO @DATA(ld_italic). | ||||
"SELECT single TDPRINTER FROM TFO03 INTO @DATA(ld_printer). | ||||
DATA(ld_uselines) | = ' '. | |||
Search for further information about these or an SAP related objects