How To Fix CNV_CMIS_M035 - DDIC and DB Index &1 created for table &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_CMIS_M - Message class for CMIS Migration

• Message number: 035

• Message text: DDIC and DB Index &1 created for table &2

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 CNV_CMIS_M035 - DDIC and DB Index &1 created for table &2 ?

  The SAP error message CNV_CMIS_M035 typically relates to issues encountered during data migration or conversion processes, particularly when using the SAP Conversion Management Information System (CMIS). The message indicates that a Data Dictionary (DDIC) and database index have been created for a specific table, but it may also imply that there are issues with the data or the configuration of the migration process.
  Cause:
  
  Data Dictionary Issues: The error may arise if there are inconsistencies or issues in the Data Dictionary definitions for the specified table.
  Index Creation Problems: The message may indicate that the index creation for the specified table has not been completed successfully or is not aligned with the expected structure.
  Migration Configuration: There may be misconfigurations in the migration settings or parameters that are causing the process to fail or not behave as expected.
  Database Constraints: There could be constraints or locks on the database that prevent the creation of the index or the proper handling of the data.
  
  Solution:
  
  Check Data Dictionary: Verify the definitions in the Data Dictionary for the specified table. Ensure that all fields, data types, and relationships are correctly defined.
  Review Index Creation: Check if the index for the specified table has been created successfully. If not, attempt to recreate the index manually using transaction codes like SE11 (Data Dictionary) or SE14 (Database Utility).
  Migration Settings: Review the migration settings and parameters in the CMIS to ensure they are correctly configured. Adjust any settings that may be causing the issue.
  Database Locks: Investigate if there are any locks or constraints on the database that could be preventing the index creation. Use transaction codes like SM12 (Display and Delete Locks) to check for locks.
  Check Logs: Review the logs generated during the migration process for any additional error messages or warnings that could provide more context on the issue.
  Consult Documentation: Refer to SAP documentation or notes related to the specific migration process you are using, as there may be known issues or additional steps required.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues related to the error message CNV_CMIS_M035. SAP frequently updates their knowledge base with solutions to common problems.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE14 (Database Utility), and SM12 (Display and Delete Locks) for troubleshooting.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.