How To Fix TG104 - Collecting inactive DDIC objects to be exported in &

TG104 - Overview

• Message type: E = Error

• Message class: TG - Messages for Upgrade Repository Switch

• Message number: 104

• Message text: Collecting inactive DDIC objects to be exported in &

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 TG104 - Collecting inactive DDIC objects to be exported in & ?

  The SAP error message TG104 typically relates to issues with the Data Dictionary (DDIC) objects in the SAP system. This message indicates that there are inactive DDIC objects that need to be collected for export, which can occur during transport requests or system upgrades.
  
  Cause:
  
  Inactive Objects: The error usually arises when there are inactive Data Dictionary objects (like tables, views, domains, data elements, etc.) that are not yet activated in the system but are still part of a transport request.
  Transport Request Issues: If a transport request is trying to include inactive objects, it can lead to this error.
  System Configuration: Sometimes, the system configuration or the way the transport landscape is set up can lead to this issue.
  
  
  Solution:
  
  
  Activate Inactive Objects: The most straightforward solution is to activate the inactive DDIC objects. You can do this by:
  
  Going to the Data Dictionary (transaction SE11).
  Finding the inactive objects and activating them.
  
  
  
  Check Transport Request: Review the