Hierarchy
DMIS (Software Component) DMIS 2011_1⤷
CA-GTF-BS (Application Component) Business Application Support⤷
CNV_BASIS (Package) Conversion: Basis functions 
Attribute
| Message class |  |
CNV | |
| Short Description |  |
Conversion: Messages for Conversion Services (CNCC) | |
| Message Number |  |
705 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20141030 |
Message Text
Help Document
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 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.
History
| Last changed on/by | |
20141030 | SAP |
| SAP Release Created in |
