How To Fix KCCO111 - Comment table & is not completely active in dictionary -> no transport

SAP Error Message - Details

• Message type: E = Error

• Message class: KCCO - Comments in EIS

• Message number: 111

• Message text: Comment table & is not completely active in dictionary -> no transport

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 KCCO111 - Comment table & is not completely active in dictionary -> no transport ?

  The SAP error message KCCO111 indicates that a comment table is not completely active in the dictionary, which prevents the transport of the related objects. This error typically arises in the context of SAP's transport management system when there are inconsistencies or issues with the database dictionary objects.
  Cause:
  
  Incomplete Activation: The comment table or its associated objects (like data elements, domains, etc.) may not have been fully activated in the SAP system.
  Transport Issues: There may be issues with the transport request itself, such as missing objects or dependencies that have not been included in the transport.
  Database Issues: There could be underlying database issues that prevent the proper activation of the comment table.
  Development Environment: If the changes were made in a development environment, they may not have been properly released or included in the transport request.
  
  Solution:
  
  
  Check Activation: 
  
  Go to transaction SE11 (Data Dictionary) and check the status of the comment table. Ensure that it is fully activated.
  If it is not activated, activate it manually.
  
  
  
  Check Transport Request:
  
  Ensure that all necessary objects related to the comment table are included in the transport request.
  Use transaction SE09 or SE10 to review the transport request and its contents.
  
  
  
  Re-transport:
  
  If the comment table was modified, ensure that the changes are included in a new transport request and try to transport again.
  
  
  
  Database Consistency:
  
  Check for any database inconsistencies. You can use transaction SE14 (Database Utility) to check and repair inconsistencies in the database.
  
  
  
  Check for Dependencies:
  
  Ensure that all dependent objects (like domains, data elements, etc.) are also active and included in the transport.
  
  
  
  Consult SAP Notes:
  
  Look for relevant SAP Notes that might address this specific error. SAP Notes can provide additional insights or patches that may resolve the issue.
  
  
  
  System Restart:
  
  In some cases, a system restart may help clear temporary issues that could be causing the error.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SE11: Data Dictionary
  SE09/SE10: Transport Organizer
  SE14: Database Utility
  
  
  SAP Notes: Always check the SAP Support Portal for any specific notes related to the KCCO111 error.
  Documentation: Review SAP documentation for best practices on managing transport requests and database objects.
  
  If the issue persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.