How To Fix FDT_TRANSPORT173 - BRF+: Physical delete started for &1 versioned object IDs (table type &2)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 173

• Message text: BRF+: Physical delete started for &1 versioned object IDs (table type &2)

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_TRANSPORT173 - BRF+: Physical delete started for &1 versioned object IDs (table type &2) ?

  The SAP error message FDT_TRANSPORT173 is related to the Business Rule Framework (BRF+) in SAP. This message indicates that a physical delete operation has been initiated for versioned object IDs in a specific table type. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Versioned Objects: The error typically arises when there are versioned objects in BRF+ that are being deleted. This can happen during transport or when cleaning up unused or obsolete rules, functions, or other BRF+ objects.
  Transport Issues: If you are trying to transport BRF+ objects and there are inconsistencies or issues with the transport request, it may trigger this error.
  Database Constraints: There may be constraints or dependencies in the database that prevent the deletion of certain objects.
  
  Solution:
  
  Check Transport Request: Ensure that the transport request is correctly configured and that all necessary objects are included. You may need to re-import or adjust the transport request.
  Review Object Dependencies: Before performing a delete operation, check for any dependencies or references to the objects you are trying to delete. Ensure that there are no active references to these objects.
  Use BRF+ Workbench: Access the BRF+ workbench to manually check the status of the objects. You can also attempt to delete the objects directly from the workbench if necessary.
  Database Cleanup: If the error persists, consider performing a database cleanup or maintenance to remove any orphaned entries or inconsistencies.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently updates its knowledge base with solutions for known issues.
  
  Related Information:
  
  BRF+ Documentation: Familiarize yourself with the BRF+ documentation provided by SAP, which can give insights into managing rules and objects effectively.
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can provide insights or solutions.
  System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.