How To Fix FDT_TRANSPORT160 - BRF+: Import queue could not be restarted due to foreign lock

FDT_TRANSPORT160 - Overview

• Message type: E = Error

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

• Message number: 160

• Message text: BRF+: Import queue could not be restarted due to foreign lock

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_TRANSPORT160 - BRF+: Import queue could not be restarted due to foreign lock ?

  The SAP error message FDT_TRANSPORT160 related to BRF+ (Business Rule Framework plus) indicates that the import queue could not be restarted due to a foreign lock. This typically occurs when there is a lock on the transport request that is preventing the import process from proceeding.
  
  Cause:
  
  Foreign Lock: The error is primarily caused by a lock on the transport request that is being used for the import. This lock could be due to:
  Another user or process currently working on the same transport request.
  A previous import process that did not complete successfully and left a lock in place.
  A system issue or inconsistency that has caused the lock to persist.
  
  
  
  
  Solution:
  To resolve the issue, you can follow these steps:
  
  
  Check Locks:
  
  Use transaction code SM12 to check for any existing locks on the transport request. Look for locks that are related to the transport request you are trying to import.
  If you find locks that are not