How To Fix TL717 - System &2 not intended for translation into target lang. &1

SAP Error Message - Details

• Message type: E = Error

• Message class: TL - Messages for language transports

• Message number: 717

• Message text: System &2 not intended for translation into target lang. &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message TL717 - System &2 not intended for translation into target lang. &1 ?

  The SAP error message TL717 indicates that the system you are trying to translate (System &2) is not intended for translation into the target language (&1). This error typically arises during the translation process in SAP, particularly when using the Translation Workbench or when attempting to transport language-specific objects.
  Cause:
  
  Language Configuration: The target language may not be configured correctly in the system. The system may not support translations for that specific language.
  Object Settings: The objects you are trying to translate may not be marked for translation in the source system.
  Transport Requests: If you are trying to transport language-specific objects, the transport request may not include the necessary language settings.
  System Settings: The system may have restrictions or settings that prevent certain languages from being used for translation.
  
  Solution:
  
  
  Check Language Configuration:
  
  Go to transaction SMLT (Language Transport) and ensure that the target language is correctly configured in the system.
  Verify that the language is installed and active in the system.
  
  
  
  Review Object Settings:
  
  Ensure that the objects you are trying to translate are marked for translation. You can check this in the relevant development environment (e.g., ABAP Dictionary for data elements, domains, etc.).
  
  
  
  Transport Request:
  
  If you are using a transport request, ensure that it includes the necessary language settings and that the objects are included in the transport.
  
  
  
  System Settings:
  
  Check the system settings to see if there are any restrictions on translations for the target language. This may involve consulting with your SAP Basis team or reviewing system documentation.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to language settings and translations for any specific guidance or updates that may apply to your version of SAP.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance, especially if this is a production environment.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE63 (Translation) and SMLT (Language Transport).
  SAP Notes: Search for SAP Notes related to translation issues, as they may provide specific fixes or workarounds for known problems.
  Documentation: Review the SAP Help Portal for information on language management and translation processes.
  
  By following these steps, you should be able to identify the cause of the TL717 error and implement a solution to resolve it.