Hierarchy

⤷

⤷

Basic Data
Data Element | DMC_SEGMENT_SIZE |
Short Description | MWB: Maximum Segment Size for a Precalculation |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
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 | 10 | Segm PREC |
Medium | 18 | Segment Size PREC |
Long | 22 | Segment Size for PREC |
Heading | 33 | Maximum Segment Size Precalculatn |
Documentation
Definition
The segment size defines the maximum number of data records for a range of the precalculation.
During the precalculation, a table is split up into parts. The segment size specifies the maximum number of data records that may lie in a range at the time when the calculation is made.
If the counter is active during the precalculation (parameter RT_PRECALC_COUNT in DMC_RT_PARAMS), small parts up to the specified segment size are aggregated after the calculation so that the number of parts decreases. However this counting function reduces the performance and should consequently only be used if absolutely necessary.
If you also activate the recursive searche during the precalculation (parameter RT_PRECALC_RECSEARCH in DMC_RT_PARAMS), the tables are first split up down to the defined search depth. Parts that are still too big are then split up further. This function also reduces the performance and should consequently only be used if absolutely necessary.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20141029 |
SAP Release Created in | 620 |