How To Fix FDT_TRANSPORT121 - BRF+: &1 is physically deleted

FDT_TRANSPORT121 - Overview

• Message type: E = Error

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

• Message number: 121

• Message text: BRF+: &1 is physically deleted

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_TRANSPORT121 - BRF+: &1 is physically deleted ?

  The SAP error message FDT_TRANSPORT121 related to BRF+ (Business Rule Framework plus) indicates that a specific object (in this case, identified by &1) has been physically deleted from the system. This can occur during transport operations or when objects are manually deleted from the BRF+ repository.
  
  Cause:
  
  Physical Deletion: The object referenced by &1 has been deleted from the BRF+ repository, which means it no longer exists in the database.
  Transport Issues: If you are transporting BRF+ objects from one system to another (e.g., from development to quality assurance), and the object was deleted in the source system, the transport request may fail because it references a non-existent object.
  Inconsistent State: The system may be in an inconsistent state where the metadata or references to the object are still present, but the actual object has been removed.
  
  
  Solution:
  
  Check Object Existence: Verify if the object (e.g., rule, decision table, etc.) still exists in the BRF+ repository.