Hierarchy

⤷

⤷

Basic Data
Data Element | RSAN_WB_DS_QUERY_CH_S |
Short Description | Partition the Data |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
Use
If you set the Divide Data Collection into Packages indicator, then the query selected for data collection is not called up straight away with all of the data, but instead is called up in separate packages. The packages are created for the Partitioning Characteristic, applying the specified package size.
Choosing this option can be necessary because a query is optimized for executing reports. Reports only show small data sets at a time in one screen. For this reason, all of the required data is loaded into the main memory when a query is executed. Processing of mass data is only possible when all the required data fits into the main memory. If, however, you would like to process larger data sets in the Analysis Process Designer, you can set this indicator.
Since smaller amounts of data are read, partitioning reduces memory consumption. On the other hand, it increases the runtime due to the additional creation of packages.
Dependencies
The function is only available for standard InfoCubes. As the partitioning characteristic, you can only use characteristics for which no conditions are stored in the query.
Example
You use the characteristic Business Partner as a partitioning characteristic and set the package size to 500. The system determines a list of all business partners and divides them into groups of 500. The query is then called up separately for each group of business partners.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 400 |