How To Fix FTBU598 - DDIC objects included in transport request .................. &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FTBU - Conversion: Treasury partner CBP messages

• Message number: 598

• Message text: DDIC objects included in transport request .................. &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 FTBU598 - DDIC objects included in transport request .................. &1 ?

  The SAP error message FTBU598 indicates that there are DDIC (Data Dictionary) objects included in a transport request that are not allowed to be transported. This typically occurs when you attempt to transport objects that are not meant to be moved between systems, such as certain types of database objects or configuration settings.
  Cause:
  
  Inappropriate Objects: The transport request includes Data Dictionary objects that are not allowed to be transported, such as certain types of views, domains, or data elements that are locked or not in a transportable state.
  Transport Layer Issues: The transport layer settings may not allow certain objects to be included in transport requests.
  Development Class Restrictions: The development class of the objects may have restrictions on transportability.
  
  Solution:
  
  Review Transport Request: Check the transport request to identify which DDIC objects are causing the issue. You can do this by analyzing the transport request in transaction SE09 or SE10.
  Remove Non-Transportable Objects: If you identify non-transportable objects, remove them from the transport request. You can do this by editing the transport request and excluding the problematic objects.
  Check Object Status: Ensure that the objects are in a transportable state. If they are locked or in a development phase, you may need to unlock or finalize them before they can be transported.
  Consult Documentation: Refer to SAP documentation or notes related to transport management for specific guidelines on which objects can be transported.
  Use Transport Organizer: Use the Transport Organizer (transaction SE09 or SE10) to manage and organize your transport requests effectively.
  
  Related Information:
  
  Transaction Codes: SE09 (Transport Organizer), SE10 (Transport Organizer - Modifiable Requests), SE11 (Data Dictionary), SE80 (Object Navigator).
  SAP Notes: Check for relevant SAP Notes that may provide additional insights or solutions for specific cases related to transport issues.
  Transport Management System (TMS): Familiarize yourself with the TMS configuration and settings, as they can impact the transportability of objects.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis team or consulting SAP support for further assistance.