How To Fix FDT_TRANSPORT172 - BRF+: Physical delete started for &1 packages (versioned IDs)

FDT_TRANSPORT172 - Overview

• Message type: E = Error

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

• Message number: 172

• Message text: BRF+: Physical delete started for &1 packages (versioned IDs)

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_TRANSPORT172 - BRF+: Physical delete started for &1 packages (versioned IDs) ?

  The SAP error message FDT_TRANSPORT172 is related to the Business Rule Framework (BRF+) in SAP, specifically concerning the transport of BRF+ objects. This error indicates that a physical delete operation has been initiated for certain packages that have versioned IDs. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Physical Deletion Request: The error typically arises when there is an attempt to physically delete BRF+ objects (like rules, functions, etc.) that are associated with specific packages. This can happen during a transport request or when cleaning up unused objects.
  Versioned IDs: The mention of "versioned IDs" suggests that the objects in question have multiple versions, and the system is trying to delete a specific version or all versions of the object.
  Transport Issues: There may be inconsistencies or issues with the transport request that is trying to delete these objects, such as dependencies on other objects or incorrect configurations.
  
  
  Solution:
  
  Check Transport Request: