How To Fix CNV705 - Information on settings for optimization transaction

CNV705 - Overview

• Message type: E = Error

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

• Message number: 705

• Message text: Information on settings for optimization transaction

Information
The optimizing transaction can be carried out after the conversion
programs have been generated. It is used to modify technical and
logical sequence criteria for a conversion package.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

The transaction can also be carried out during a conversion to modify
the optimization settings of a package.
Changeable settings and their meaning
Optimization active / de-activ.
Using a view maintenance, you can activate or deactivate optimization
for a package by selecting or deselecting the corresponding checkbox in
the maintenance accordingly.
Performance analysis
Here, the maximum number of CPU-intensive, I/O-intensive,
main-memory-intensive and rollback-intensive background processes as
well as the maximum total of background processes which was determined
during a performance analysis can be set for a given package.
These settings influence the start sequence of the conversion programs
with regard to available system resources for the individual areas.
Performance profile of system
The performance profile of the system for each of the areas of CPU,
I/O, main memory resources and rollback segments is set to 100 % at the
start of the conversion. By changing the percentage values, changes in
system performance can be taken into account.
By changing these settings, the determination of available system
resources by the start program of the conversion is influenced.
Requirement profile for scenarios
The generated conversion programs use a multitude of different
conversion techniques. These different techniques also have different
demands on the system.
Using a view maintenance, you can modify these requirement profiles for
the individual szenarios. A value of 1.0 means a main load, while a
smaller value means a secondary load for the system.
The default settings should only be changed under exceptional
circumstances.
Requirement profile for conversion
After generation, the requirement profile for each conversion program
can be displayed and changed manually (if necessary). The requirement
profile of all programs is updated after every change of the
optimization settings unless the job is locked by the 'MODIFICATION'
indicator.
Criteria for start sequence
Here, all start and sequence criteria that the start program of the
conversion can analyze are stored in a table.
These settings should not be changed.
Table-specific index handling
The highest indexes of tables that are handled by the selected
conversion package can be determined.
When indexes are selected, these indeces are dropped during the
conversion and re-created after the table has been converted. If memory
problems are likely to occur during creation of the indexes, a message
is created. This index determination works only for ORACLE databases.
Table pre-select
To avoid error ORA-1555 during selection and to define a start sequence
for the largest tables, you can flag the largest tables which are
handled by the conversion package (after determination). The selection
and determination of transparent tables and cluster tables are carried
out in different lists.
During the pre-select, program CNV_00001_TABLE_FULL_SCAN is executed
automatically before the start of the actual selection.

Error message extract from SAP system. Copyright SAP SE.

CNV705 - Details

• The SAP error message CNV705 typically relates to the settings for optimization transactions in the context of data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error can occur when there are issues with the configuration or settings that are required for the optimization of data during the migration process.
  
  Cause:
  
  Missing Configuration: The error may arise if certain required settings or configurations for the optimization transaction are missing or not properly set up in the system.
  Incompatible Data: The data being processed may not be compatible with the optimization settings, leading to conflicts.
  Authorization Issues: The user executing the transaction may not have the necessary authorizations to perform the optimization.
  Technical Issues: There may be underlying technical issues, such as system performance problems or bugs in the migration tool.
  
  
  Solution:
  
  Check Configuration Settings: Review the configuration settings for the optimization transaction. Ensure that all required parameters are correctly