How To Fix CNV_OM_PRESEL118 - Table count started as batch job for preselection table &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_OM_PRESEL - Messages for LT Object Based Preselection

• Message number: 118

• Message text: Table count started as batch job for preselection table &1

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_OM_PRESEL118 - Table count started as batch job for preselection table &1 ?

  The SAP error message CNV_OM_PRESEL118 typically occurs during the execution of a conversion or migration process, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that the system has started a batch job to count the entries in a preselection table, but there may be issues related to the execution or the data in that table.
  Cause:
  
  Data Volume: The preselection table may contain a large volume of data, which can lead to performance issues or timeouts during the counting process.
  Locking Issues: If other processes are accessing the same table, it may lead to locking issues that prevent the batch job from executing properly.
  Configuration Issues: There may be misconfigurations in the migration settings or the environment that could lead to this error.
  Database Performance: The underlying database may be experiencing performance issues, which can affect the execution of batch jobs.
  
  Solution:
  
  Check Job Logs: Review the job logs for any additional error messages or warnings that can provide more context about the failure.
  Optimize Data Volume: If possible, reduce the volume of data in the preselection table by filtering out unnecessary records before running the migration.
  Increase Resources: Ensure that the system has adequate resources (CPU, memory) to handle the batch job, especially if the data volume is large.
  Check for Locks: Use transaction codes like SM12 to check for locks on the preselection table and resolve any conflicts.
  Run in Smaller Batches: If the data volume is too large, consider breaking it down into smaller batches to avoid performance issues.
  Database Maintenance: Perform database maintenance tasks, such as updating statistics or optimizing indexes, to improve performance.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM12 (Lock Entries), and ST22 (Dump Analysis) to help diagnose the issue.
  SAP Documentation: Review the official SAP documentation for the migration tool you are using, as it may provide specific guidance on handling errors related to preselection tables.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found effective.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP Support for further assistance.