How To Fix FDT_TRANSPORT804 - Request &1 is persistent

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_TRANSPORT - Formula & Derivation Tool: Transport

• Message number: 804

• Message text: Request &1 is persistent

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 FDT_TRANSPORT804 - Request &1 is persistent ?

  The SAP error message FDT_TRANSPORT804 indicates that a transport request is persistent, meaning that it cannot be deleted or modified in the usual way. This typically occurs in the context of the SAP Fiori Design Time (FDT) or when dealing with transport requests in the SAP system.
  Cause:
  
  Transport Request Status: The transport request may be in a status that prevents it from being deleted or modified. For example, it might be released or already imported into the target system.
  Dependencies: There may be dependencies on the transport request that prevent it from being deleted.
  System Configuration: Certain configurations or settings in the SAP system may enforce persistence for specific transport requests.
  
  Solution:
  
  
  Check Transport Request Status: 
  
  Use transaction code SE09 or SE10 to check the status of the transport request. Ensure that it is not released or already imported.
  
  
  
  Delete or Modify the Request:
  
  If the request is not released, you can try to delete it directly from the transport organizer.
  If it is released, you may need to create a new transport request to move the changes instead of modifying the existing one.
  
  
  
  Check Dependencies:
  
  Investigate if there are any dependent objects or requests that are linked to the transport request. You may need to resolve these dependencies before proceeding.
  
  
  
  Consult with Basis Team:
  
  If you are unable to resolve the issue, consult with your SAP Basis team. They may have the necessary authorizations and tools to handle persistent transport requests.
  
  
  
  Use Transport Management System (TMS):
  
  If the request is part of a transport route, you may need to use TMS to manage the transport request appropriately.
  
  
  
  Related Information:
  
  Transport Organizer: The tool used to manage transport requests in SAP.
  Transport Request Types: Understand the different types of transport requests (e.g., workbench requests, customizing requests) and their implications.
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to transport requests and persistence issues.
  
  If the problem persists after following these steps, it may be necessary to escalate the issue to SAP support for further assistance.