How To Fix FDT_TRANSPORT058 - BRF+: &1 Object IDs skipped: Already deleted logical in target and source

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 058

• Message text: BRF+: &1 Object IDs skipped: Already deleted logical in target and source

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_TRANSPORT058 - BRF+: &1 Object IDs skipped: Already deleted logical in target and source ?

  The SAP error message FDT_TRANSPORT058 related to BRF+ (Business Rule Framework plus) indicates that certain object IDs were skipped during a transport process because they were already deleted in both the target and source systems. This typically occurs when you are trying to transport BRF+ objects (like rules, functions, or decision tables) from one SAP system to another, and the transport process detects that the objects in question no longer exist in either system.
  Cause:
  
  Deleted Objects: The objects you are trying to transport have been deleted in both the source and target systems. This can happen if the objects were removed after the transport request was created but before the transport was executed.
  Inconsistent State: There may be inconsistencies between the source and target systems regarding the existence of certain BRF+ objects.
  Transport Request Issues: The transport request may not have been properly updated to reflect the current state of the objects.
  
  Solution:
  
  Check Object Existence: Verify whether the objects listed in the error message actually exist in the source and target systems. You can do this by checking the BRF+ workbench (transaction code BRF+) in both systems.
  Update Transport Request: If the objects have been deleted, you may need to update the transport request to remove references to these objects. This can be done by:
  
  Opening the transport request in the source system.
  Removing the deleted objects from the request.
  Re-saving the transport request.
  
  
  Recreate Objects: If the objects are still needed, consider recreating them in the source system and then transporting them again.
  Ignore the Warning: If the objects are no longer needed, you can choose to ignore the warning and proceed with the transport, as the system is informing you that these objects are not present.
  Consult Logs: Check the transport logs for more detailed information about the skipped objects and any other related issues.
  
  Related Information:
  
  BRF+ Documentation: Familiarize yourself with the BRF+ documentation to understand how objects are managed and transported.
  Transport Management: Review SAP's transport management documentation to ensure you are following best practices for transporting objects between systems.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance related to BRF+ transport errors.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.