How To Fix CNV779 - Creation of indexes has already been scheduled by another job

CNV779 - Overview

• Message type: E = Error

• Message class: CNV - Conversion: Messages for Conversion Services (CNCC)

• Message number: 779

• Message text: Creation of indexes has already been scheduled by another job

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.

CNV779 - Details

• The SAP error message "CNV779 Creation of indexes has already been scheduled by another job" typically occurs during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there is already a job scheduled to create indexes for the same database table, which prevents the current job from proceeding.
  
  Cause:
  
  Concurrent Jobs: The most common cause is that another job is already running or has been scheduled to create indexes for the same table. This can happen if multiple migration or data processing jobs are initiated simultaneously.
  Job Overlap: If a previous job did not complete successfully or is still in progress, it can lead to this error when a new job attempts to create indexes for the same table.
  System Configuration: In some cases, system settings or configurations may lead to jobs being scheduled inappropriately.
  
  
  Solution:
  
  Check Job Status: Use transaction code SM37 to check