Hierarchy
DMIS (Software Component) DMIS 2011_1⤷
CA-GTF-BS (Application Component) Business Application Support⤷
CNV_BASIS (Package) Conversion: Basis functions
Basic Data
| Data Element | CNV_COMBY |
| Short Description | DB commit frequency in bytes |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CNV_SIZE | |
| Data Type | NUMC | Character string with only digits |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 8 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Commits |
| Medium | 15 | Commit freq. |
| Long | 25 | Commit frequency |
| Heading | 25 | Commit frequency |
Documentation
Definition
Frequency of database commits during the update phase of the conversion.
Use
During the selection phase of the conversion the data is written to the special cluster table. In update phase this data is read from this cluster table, converted and written back to the original database table. To commit the changes in the database a COMMIT command has to be issued. This value controls how often this happens (after how many bytes are read from the cluster table since the last commit).
Dependencies
Example
Supplementary Documentation - CNV_COMBY 0001
Use
This value can have impact on the performance. The greater the value, the more seldom the data has to be commited and the less I/O activity is needed (commits are quite I/O-intensive). On the other hand seldom commits imply long transactions and the longer the transaction is the more undo / rollback buffer space is used, which can even lead the conversion program to dump.
Dependencies
Example
History
| Last changed by/on | SAP | 20141030 |
| SAP Release Created in | 2006_1_46C |
