PREP_CHKIMPORT/CNV_CHK_IMP: The following unprocessed db conversion request were found

You are getting below error message in the midst of executing SUM activities.

SUM-Phase: PREP_CHKIMPORT/CNV_CHK_IMP
WARNING: The following unprocessed database conversion requests were found: 

Entry
INDXZVSCRM_HZ010CREIE20200225DDIC  

An import might still be running. The tables of the converter 
program must be empty in the first CNV_CHK phase. 
In this phase, the converter program tables are checked again. 
In case the tables are not empty, the SUM stops and prompts 
you to empty the converter tables.

Solution

Refer to SAP Note 2443202 – Cleaning Up Terminated Conversions in the DB Conversion Phases and SUM guide.

Procedure for “Restart Logs of DB Conversions Found”

1. To find the terminated conversions, execute SE14. Choose DB Requests > Terminated.
2. Double-click a table name to see its details. Check the meaning and status of the table.
   1. Find out whether the table is still needed. Sometimes the tables are test tables that are no longer needed. For SAP tables, contact SAP Support, which can assess if an SAP table is still needed.
   2. Ask the last person who changed the table, or the table owner, to find out its status. If the table is no longer needed, choose Unlock table in the detailed display. This prevents the conversion from being continued automatically. The table itself does not return to a consistent state. Any data that is still in the temporary table is lost during the next conversion. In some cases, however, the table was already corrected without the reset log being deleted. The function Unlock table is harmless in this case.
   3. You can determine the state of the table with Check > Database object and Check > Runtime object.
   4. Check if the table contains the data you expect. You can do this with transaction SE16, for example. If the data does not exist, it could still be in the temporary table. Contact your SAP consultant or SAP Support for help in saving this data.
3. Determine the cause of the error. If you find out that the table is still needed, choose Object log. Look for error messages that explain why the conversions were terminated. You could encounter the following problems here:
   1. You cannot find a log because it was deleted at some time in the past. Continue with step 6 (continue the conversion to the end).
   2. The log does not contain an error message, but ends abruptly. This indicates that the conversion was stopped by an external event. Call transaction SM21 to read the system log and find out the approximate time the conversion was terminated, and to look for the cause of the error.
   3. If the log clearly gives a reason for the error, you have to correct it.
4. Continue the conversion to the end. In the detailed display, choose Continue adjustment. Since you do not know how long this takes, choose processing type Background. The situation can be as follows:
   1. The conversion finished successfully. You can see this because the error message disappears, the Check function does not display any further problems, and there is a success message in the object log.
   2. The conversion terminates again. A log now exists. Repeat the analysis from step 5 (Determine the cause of the error).

Procedure for “Outstanding DB conversions found”

1. Determine the objects that are affected.
   1. From transaction SE14, choose DB Requests >Mass Processing.
   2. Choose All requests. The worklist of the conversion program appears. This worklist was generated by developments or modifications in your SAP system, but has not yet been processed.
   3. Choose DB requests > Created with import. The worklist that was not processed correctly during the last update appears.
2. Check the meaning and status of the requests. In contrast to the procedure for the message Restart logs of DB conversions found, this
   procedure can also include requests for indexes, views and match code objects. The requests that are found are not always terminated. They might not even have been started.
   1. Ask the last person who changed the object if the request should still be processed.
   2. If the user does not want it to be processed, select the request and choose Delete selected. This removes the objects from the worklist of the conversion program. Do not remove requests from the last update.
3. Process the outstanding requests. You can select the requests from the list of mass processing requests and schedule a job for execution with the function Schedule selections.
   1. Go to the detailed display of the object by double-clicking it in the list of requests created by the import.
   2. Schedule the request, or continue it. Since you do not know how long this takes, choose processing type Background.