How To Fix /BOBF/CONF_CDS079 - [BO sync] No Transport request. Synchronisation not started (view &1)

/BOBF/CONF_CDS079 - Overview

• Message type: E = Error

• Message class: /BOBF/CONF_CDS -

• Message number: 079

• Message text: [BO sync] No Transport request. Synchronisation not started (view &1)

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 /BOBF/CONF_CDS079 - [BO sync] No Transport request. Synchronisation not started (view &1) ?

  The SAP error message /BOBF/CONF_CDS079 [BO sync] No Transport request. Synchronisation not started (view &1) typically occurs in the context of Business Object Framework (BOBF) when there is an issue with the synchronization of a Core Data Services (CDS) view. This error indicates that the system is unable to start the synchronization process because there is no transport request associated with the operation.
  
  Cause:
  
  Missing Transport Request: The most common cause of this error is that the system is expecting a transport request to be assigned for the synchronization process, but none is available.
  Development Environment: If you are working in a development environment, it is possible that the necessary transport request has not been created or released.
  
  Configuration Issues: There may be configuration issues in the BOBF or CDS view that prevent the synchronization from being initiated.
  Authorization Issues: Lack of proper authorizations to create or manage transport requests can also lead to this