How To Fix FDT_TRANSPORT734 - BRF+: &1 objects are marked for delete

FDT_TRANSPORT734 - Overview

• Message type: E = Error

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

• Message number: 734

• Message text: BRF+: &1 objects are marked for delete

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.

FDT_TRANSPORT734 - Details

• The SAP error message FDT_TRANSPORT734 related to BRF+ (Business Rule Framework plus) indicates that certain objects are marked for deletion in the transport request. This typically occurs when you are trying to transport BRF+ objects (like rules, expressions, or decision tables) that have been flagged for deletion in the source system.
  
  Cause:
  
  Marked for Deletion: The objects you are trying to transport have been marked for deletion in the source system. This can happen if someone has deleted or flagged these objects for deletion in the BRF+ workbench.
  Transport Request Issues: The transport request may not be properly configured or may contain inconsistencies.
  Versioning Issues: There may be versioning issues where the objects in the transport request do not match the current state of the objects in the target system.
  
  
  Solution:
  
  
  Check the Transport Request: 
  
  Open the transport request in the source system and check the objects included in it. Look for any objects that are