How To Fix TD363 - Link to nonexistent font metrics &

SAP Error Message - Details

• Message type: E = Error

• Message class: TD - SAPscript: Text editor, composer, forms, styles and fonts

• Message number: 363

• Message text: Link to nonexistent font metrics &

What causes this issue?

The fontmetrics file (AFM file) contains a link to another fontmetrics
file. However, the latter does not exist.

System Response

The system sends an error message.

How to fix this error?

Correct the link in the fontmetrics by editing the AFM file and
correcting the link. Enter the key of a fontmetrics file which does
exist. A correct link appears as follows:

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

sapLinkToAFM HPLJIIID HELVE 120 false true
This statement represents a link to the AFM file for HPLJIIID HELVE 120
not bold, italic. If a link is inserted in an AFM file, the line with
the link must be the only line in the fontmetrics. Additional
specifications are not valid.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TD363 - Link to nonexistent font metrics & ?

  The SAP error message TD363, which states "Link to nonexistent font metrics," typically occurs when the SAP system is unable to find the font metrics for a specified font. This can happen for various reasons, such as missing font files, incorrect font configuration, or issues with the SAPscript or Smart Forms.
  Causes:
  
  Missing Font Files: The font specified in the SAPscript or Smart Form is not installed on the system or is not accessible.
  Incorrect Font Configuration: The font may not be correctly configured in the SAP system, leading to the inability to link to its metrics.
  Font Not Supported: The font being used may not be supported by the SAP system or the output device.
  Transport Issues: If the font was recently transported from another system, there may have been issues during the transport process.
  
  Solutions:
  
  
  Check Font Installation:
  
  Ensure that the required font is installed on the SAP system. You can check the installed fonts in transaction code SE73 (SAPscript Font Maintenance).
  If the font is missing, you may need to install it or configure it properly.
  
  
  
  Verify Font Configuration:
  
  Go to transaction SE73 and check the font settings. Ensure that the font metrics are correctly linked to the font you are trying to use.
  If necessary, create or adjust the font metrics for the font in question.
  
  
  
  Use Supported Fonts:
  
  If the font is not supported, consider using a different font that is known to work with SAPscript or Smart Forms.
  
  
  
  Check Output Device Settings:
  
  Ensure that the output device (printer or PDF) is configured to support the font being used. You can check this in transaction SPAD (Spool Administration).
  
  
  
  Transport Issues:
  
  If the font was recently transported, check the transport logs for any errors. You may need to re-transport the font metrics or check the transport settings.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to font management and troubleshooting for additional guidance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SE73: SAPscript Font Maintenance
  SPAD: Spool Administration
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to fonts and metrics.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to resolve the TD363 error and ensure that the necessary font metrics are correctly linked in your SAP environment.