SAP ABAP Data Element VERW_COMM (Portion size for COMMIT sections)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MG (Package) Application development R/3 material master prior to 3.0
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MG (Package) Application development R/3 material master prior to 3.0
Basic Data
Data Element | VERW_COMM |
Short Description | Portion size for COMMIT sections |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC10 | |
Data Type | NUMC | Character string with only digits |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Size |
Medium | 15 | Portion size |
Long | 20 | Portion size |
Heading | 10 | Size |
Documentation
Definition
Number of materials that are to be processed together in a COMMIT unit.
Use
Procedure
Examples
Dependencies
If the number is small, the system needs to access the database more frequently, increasing the runtime. If the number is too large (over 1,000), there is a risk of the program terminating due to the roll area being too small.
Generally speaking, the following recommendation for improving performance can be made: The more organizational units that materials have, the smaller this number can be. However, the optimum number can only be determined by trying out different numbers yourself.
History
Last changed by/on | SAP | 19971006 |
SAP Release Created in |