How To Fix FTBU603 - DDIC objects not included in transport request (Error)&1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 603

• Message text: DDIC objects not included in transport request (Error)&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 FTBU603 - DDIC objects not included in transport request (Error)&1 ?

  The SAP error message FTBU603 indicates that certain Data Dictionary (DDIC) objects are not included in a transport request. This can occur when you attempt to transport changes to DDIC objects (like tables, views, domains, data elements, etc.) but those objects have not been properly included in the transport request.
  Cause:
  
  Missing Inclusion: The DDIC objects were not added to the transport request when the changes were made.
  Transport Request Issues: The transport request may not have been released or may be in a state that prevents the inclusion of new objects.
  Development Class: The objects may belong to a development class that is not transportable or is incorrectly configured.
  Authorization Issues: Lack of proper authorizations to include objects in the transport request.
  
  Solution:
  
  
  Check Transport Request:
  
  Open the transport request in the Transport Organizer (transaction SE09 or SE10).
  Verify if the DDIC objects are listed in the transport request. If not, you need to add them manually.
  
  
  
  Include Objects Manually:
  
  Go to the relevant transaction (e.g., SE11 for Data Dictionary objects).
  Find the object that is causing the error.
  Use the "Transport" button to include the object in the transport request.
  
  
  
  Release Transport Request:
  
  Ensure that the transport request is released properly. You can do this in SE09/SE10 by selecting the request and choosing the "Release" option.
  
  
  
  Check Development Class:
  
  Ensure that the development class of the DDIC objects is transportable. You can check this in SE11 by looking at the attributes of the object.
  
  
  
  Authorization Check:
  
  Ensure that you have the necessary authorizations to include objects in the transport request. If not, contact your SAP Basis administrator.
  
  
  
  Recreate Transport Request:
  
  If the transport request is corrupted or not functioning as expected, consider creating a new transport request and including the necessary objects.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SE09: Transport Organizer
  SE10: Transport Organizer (for released requests)
  SE11: Data Dictionary
  
  
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to transport requests and DDIC objects.
  Documentation: Review SAP documentation on transport management for best practices and troubleshooting steps.
  
  By following these steps, you should be able to resolve the FTBU603 error and successfully include the necessary DDIC objects in your transport request.