How To Fix FDT_TRANSPORT078 - BRF+: Object &1 is not updated due to customer changes

FDT_TRANSPORT078 - Overview

• Message type: E = Error

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

• Message number: 078

• Message text: BRF+: Object &1 is not updated due to customer changes

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_TRANSPORT078 - BRF+: Object &1 is not updated due to customer changes ?

  The SAP error message FDT_TRANSPORT078 related to BRF+ (Business Rule Framework plus) indicates that an object (like a rule, decision table, or function) is not being updated in the transport request due to customer-specific changes. This typically occurs when there are modifications made to the BRF+ objects that are not aligned with the standard transport process.
  
  Cause:
  
  Customer-Specific Changes: The object in question has been modified in a way that is not compatible with the standard transport mechanism. This could be due to custom enhancements or changes made directly in the development environment.
  Transport Request Issues: The object may not be included in the transport request due to its status or because it was not properly added to the request.
  Versioning: There may be version conflicts if the object has been changed in multiple environments (e.g., development and quality assurance) without proper synchronization.
  
  
  Solution:
  
  Check Object Status: Verify the status of the object in the BRF+