How To Fix EZ390 - Transport entry for text &1 (language &2) was created in request &3

SAP Error Message - Details

• Message type: E = Error

• Message class: EZ - Print workbench

• Message number: 390

• Message text: Transport entry for text &1 (language &2) was created in request &3

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 EZ390 - Transport entry for text &1 (language &2) was created in request &3 ?

  The SAP error message EZ390 indicates that a transport entry for a specific text (identified by &1) in a particular language (identified by &2) has been created in a transport request (identified by &3). This message typically arises during the transport of language-dependent objects, such as texts, messages, or other translatable content.
  Cause:
  
  Transport Request Creation: The error usually occurs when a transport request is created for language-dependent objects, and the system is trying to process or transport these objects.
  Missing Language: The specified language might not be available in the target system, or the transport request may not have been properly configured to include the necessary language texts.
  Inconsistent Data: There may be inconsistencies in the transport request, such as missing dependencies or objects that are not properly included.
  
  Solution:
  
  Check Transport Request: Review the transport request (&3) to ensure that it includes all necessary objects and dependencies. Make sure that the text for the specified language (&2) is included.
  Language Availability: Verify that the target system has the specified language installed and configured. If not, you may need to install the language or adjust the transport request accordingly.
  Re-transport: If the transport request is incomplete or incorrect, you may need to create a new transport request that includes the necessary language texts and objects.
  Transport Organizer: Use the Transport Organizer (transaction SE09 or SE10) to check the status of the transport request and ensure that it is released and properly configured.
  Check for Errors: Look for any other error messages or logs that may provide additional context about the issue. This can help identify if there are other underlying problems.
  
  Related Information:
  
  Transaction Codes: SE09 (Transport Organizer), SE10 (Transport Organizer - Modifiable Requests), SE01 (Transport Organizer - Transport Requests).
  Language Configuration: You can check the installed languages in the system using transaction SMLT.
  Transport Management System (TMS): Ensure that the TMS is properly configured and that all systems in the landscape are correctly set up to handle transports.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or refer to SAP Notes for more specific guidance related to your system version and configuration.