SAP ABAP Data Element KCBLKSIZE (External data transfer: Block size)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷ CA-GTF-DCM (Application Component) Data Transfer
⤷ BKD (Package) Tools for (external) data transfer
⤷ CA-GTF-DCM (Application Component) Data Transfer
⤷ BKD (Package) Tools for (external) data transfer
Basic Data
Data Element | KCBLKSIZE |
Short Description | External data transfer: Block size |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SYST_LONG | |
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 11 | |
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 | 5 | Block |
Medium | 5 | Block |
Long | 10 | Block size |
Heading | 0 |
Documentation
Definition
In order to improve the performance of external data transfers, it makes sense to execute multiple jobs in parallel. When doing so, however, note that this increases the main memory workload. The block size determines the number of objects to be processed for each job. The larger the block size, the more records are processed for each job. Smaller block sizes allow parallel processing because the main memory requirement is smaller.
The optimal value depends on the user's hardware, parallel processing, the size of the sender structure, and other factors such as the maximum number of lock entries in a system. Sometimes using a certain block size can help to avoid exceeding this limit.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in |