SAP ABAP Data Element MD_MAXCOMM (No. of transactions per commit unit for data transfer)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ LO-MD-MM (Application Component) Material Master
⤷ MGAD (Package) Data Transfer R/3 Material Master as of 3.0
⤷ LO-MD-MM (Application Component) Material Master
⤷ MGAD (Package) Data Transfer R/3 Material Master as of 3.0
Basic Data
Data Element | MD_MAXCOMM |
Short Description | No. of transactions per commit unit for data transfer |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC6 | |
Data Type | NUMC | Character string with only digits |
Length | 6 | |
Decimal Places | 0 | |
Output Length | 6 | |
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 | CommitSize |
Medium | 15 | Commit size |
Long | 20 | Recs per commit unit |
Heading | 10 | CommitSize |
Documentation
Definition
You use this number to define how many transactions are to be processed in a physical step.
- The higher the number, the less frequently the system has to access the database, increasing, however, the size of internal tables.
- The smaller the number, the more frequently the system needs to access the database, reducing, however, the size of internal tables.
Use
Procedure
By changing this number, you may be able to improve performance. Unfortunately, it is not possible to make any general recommendation regarding size. However, 500 is appropriate.
Examples
Dependencies
History
Last changed by/on | SAP | 19980706 |
SAP Release Created in |