How To Fix TD747 - PC Editor could not be called (Hex command)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 747

• Message text: PC Editor could not be called (Hex command)

What causes this issue?

The PC editor could not be called because hexidecimal data (HEX
command) occurs in the text. SAPscript cannot interpret data between
HEX and ENDHEX and thus places it directly in the output flow. This
allows you to print graphics from SAPscript that are present in pixel
form.

System Response

The system automatically calls the line editor instead.

How to fix this error?

Please use the line editor.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TD747 - PC Editor could not be called (Hex command) ?

  The SAP error message TD747, which states "PC Editor could not be called (Hex command)," typically occurs when there is an issue with the integration between the SAP system and the local PC editor. This error can arise in various scenarios, such as when trying to edit documents or text elements in SAP that require an external editor.
  Causes:
  
  Missing or Incorrect Configuration: The SAP system may not be properly configured to call the local PC editor. This can happen if the editor is not installed or if the path to the editor is incorrect.
  Unsupported Editor: The editor you are trying to use may not be supported by SAP or may not be compatible with the version of SAP you are using.
  Network Issues: If the SAP GUI is running in a remote environment, network issues may prevent the editor from being launched.
  User Authorizations: The user may not have the necessary authorizations to call external applications from SAP.
  SAP GUI Settings: The settings in the SAP GUI may not be configured to allow the use of external editors.
  
  Solutions:
  
  
  Check Configuration:
  
  Go to the SAP GUI options and check the settings for the external editor. Ensure that the correct path to the editor is specified.
  You can find this under Options -> SAP GUI Options -> Accessibility & Scripting -> Scripting and ensure that the "Enable scripting" option is checked.
  
  
  
  Verify Editor Installation:
  
  Ensure that the editor you are trying to use (e.g., Notepad, Word, etc.) is installed on your local machine and is functioning correctly.
  
  
  
  Test with Different Editors:
  
  Try using a different text editor to see if the issue persists. This can help determine if the problem is specific to the editor you are trying to use.
  
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary authorizations to call external applications. This may require assistance from your SAP security team.
  
  
  
  Network Configuration:
  
  If you are using SAP in a remote environment, check your network settings and ensure that there are no firewalls or security settings blocking the connection to the local editor.
  
  
  
  SAP Notes:
  
  Check for any relevant SAP Notes or updates that may address this issue. Sometimes, specific patches or updates can resolve known issues.
  
  
  
  Related Information:
  
  SAP GUI Version: Ensure that you are using a compatible version of the SAP GUI with your SAP system.
  Operating System Compatibility: Check if there are any compatibility issues between the operating system and the SAP GUI or the external editor.
  SAP Community: You can search for discussions or solutions related to TD747 in the SAP Community forums, where other users may have encountered and resolved similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact your SAP support team for further assistance.