How To Fix FDT_TRANSPORT128 - BRF+: &1 unnamed unused objects have been physically deleted

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 128

• Message text: BRF+: &1 unnamed unused objects have been 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_TRANSPORT128 - BRF+: &1 unnamed unused objects have been physically deleted ?

  The SAP error message FDT_TRANSPORT128 related to BRF+ (Business Rule Framework plus) indicates that there are unnamed unused objects that have been physically deleted during a transport process. This typically occurs when you are trying to transport BRF+ objects from one system to another (e.g., from a development system to a quality assurance or production system) and there are references to objects that are no longer valid or have not been properly defined.
  Cause:
  
  Unused Objects: The error suggests that there are objects in the BRF+ repository that are not being used or referenced anywhere, and they have been marked for deletion.
  Transport Issues: The transport request may have included references to these unnamed objects, leading to inconsistencies during the transport process.
  Configuration Changes: Changes made in the BRF+ configuration that involve deleting or renaming objects without proper handling can lead to this error.
  
  Solution:
  
  
  Check for Unused Objects: 
  
  Go to the BRF+ workbench (transaction code BRF+) and check for any unused or unnamed objects. You can use the "Unused Objects" report to identify these.
  If you find any, you can either delete them or ensure they are properly named and referenced.
  
  
  
  Transport Request Review:
  
  Review the transport request to ensure that it does not include references to these unnamed objects. You may need to adjust the transport request accordingly.
  If necessary, create a new transport request that only includes valid and named objects.
  
  
  
  Consistency Check:
  
  Perform a consistency check in the BRF+ workbench to ensure that all objects are correctly defined and referenced.
  Use the "Consistency Check" feature to identify any inconsistencies in your BRF+ configuration.
  
  
  
  Re-transport:
  
  After resolving the issues with unused objects, attempt to re-transport the BRF+ objects again.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to BRF+ and transport issues for any specific guidelines or updates that may apply to your version of SAP.
  
  
  
  Related Information:
  
  BRF+ Documentation: SAP provides extensive documentation on BRF+, which can be helpful in understanding how to manage and transport BRF+ objects.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  SAP Community: Engaging with the SAP Community can provide insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to resolve the FDT_TRANSPORT128 error and successfully manage your BRF+ objects during transport.