How To Fix TG163 - Object & & & is not included because of exception &, try next object

SAP Error Message - Details

• Message type: E = Error

• Message class: TG - Messages for Upgrade Repository Switch

• Message number: 163

• Message text: Object & & & is not included because of exception &, try next object

What causes this issue?

A transport object could not be added to the table of objects delivered
by SAP.

System Response

Error message in the upgrade phase JOB_RDDIT021.

How to fix this error?

Contact the upgrade hotline.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TG163 - Object & & & is not included because of exception &, try next object ?

  The SAP error message TG163 indicates that a specific object is not included in a transport request due to an exception. This message typically arises during the transport of objects between different SAP systems, such as from a development system to a quality assurance or production system.
  Cause:
  The error message TG163 can occur due to several reasons, including:
  
  
  Object Locking: The object you are trying to transport may be locked by another user or process, preventing it from being included in the transport request.
  
  
  Missing Dependencies: The object may have dependencies that are not met, meaning that other related objects must be transported first.
  
  
  Transport Configuration Issues: There may be issues with the transport configuration or settings in the SAP system that prevent the object from being included.
  
  
  Authorization Issues: The user attempting to create the transport request may not have the necessary authorizations to include certain objects.
  
  
  Exceptions in Object Definition: The object itself may have exceptions defined that prevent it from being transported.
  
  
  Solution:
  To resolve the TG163 error, you can take the following steps:
  
  
  Check Object Locking:
  
  Use transaction code SE03 (Transport Organizer Tools) to check if the object is locked. If it is, you may need to wait until the lock is released or contact the user who has locked it.
  
  
  
  Review Dependencies:
  
  Ensure that all dependent objects are included in the transport request. You can check the object dependencies using transaction SE80 or SE11.
  
  
  
  Verify Transport Configuration:
  
  Check the transport configuration settings in transaction STMS (Transport Management System) to ensure everything is set up correctly.
  
  
  
  Check Authorizations:
  
  Ensure that you have the necessary authorizations to transport the object. You may need to consult with your SAP security team.
  
  
  
  Review Object Definition:
  
  Check the object definition for any exceptions that may prevent it from being transported. This can often be done in the object’s development environment.
  
  
  
  Try Next Object:
  
  As the error message suggests, you can attempt to transport the next object in the list if the current one cannot be included.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SE03: Transport Organizer Tools
  SE80: Object Navigator
  STMS: Transport Management System
  SE11: Data Dictionary
  
  
  
  SAP Notes: Check SAP Notes related to transport issues for any specific patches or updates that may address known issues.
  
  
  Documentation: Refer to SAP Help documentation for more detailed information on transport management and object dependencies.
  
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.