How To Fix FDT_TRANSPORT805 - Request &1 is not persistent

FDT_TRANSPORT805 - Overview

• Message type: E = Error

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

• Message number: 805

• Message text: Request &1 is not 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_TRANSPORT805 - Request &1 is not persistent ?

  The SAP error message FDT_TRANSPORT805 indicates that a transport request is not persistent. This typically occurs in the context of the SAP Fiori Design Time (FDT) or when working with transport requests in the SAP system. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause
  
  Non-Persistent Transport Request: The transport request you are trying to use is not marked as persistent. This can happen if the request was not properly saved or if it was deleted or not released correctly.
  Transport Request Status: The transport request may be in a status that does not allow it to be used for transport (e.g., it might be in a "modification" state).
  System Configuration: There may be issues with the configuration of the transport management system (TMS) or the transport layer.
  
  Solution
  
  
  Check Transport Request Status:
  
  Go to transaction SE09 or SE10 to check the status of the transport request. Ensure that it is in a "released"