Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MCP2 (Package) R/3 application development: Sales & Operations Planning
Basic Data
| Data Element | FLGPA |
| Short Description | Switch on parallel database access |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR01 | |
| 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 | 10 | Paral. on |
| Medium | 20 | Paral. DB-select on |
| Long | 37 | Switch on parallel database access |
| Heading | 37 | Switch on parallel database access |
Documentation
Definition
This switch influences performance.
If you switch it on, the system does not carry out database selection at aggregate level. The system performs parallel database accesses one level deeper, and then calculates the aggregate level. Therefore, in the first drilldown, there is now no need for the system to read data retrospectively. This can lead to a considerable improvement in performace for certain data patterns. Sometimes, however, there is no advantage in using parallel selection.
Example
Level A: 01
Level B: 01 02 03 04 05 06 07 08
You plan 01 at level A. The eight members are read in parallel and then aggregated; the first drilldown has a very fast response time.
If the system had not read the members in parallel, it would have read the data in aggregated form and would have had to read additional data for the drilldown. If the time taken to administer and transport the partially aggregated values exceeds the time taken for data selection, then the non-parallel database access is the quicker method. If the dataset is very large and also well distributed over the members of level B, individual data selection exceeds the time taken for data administration and transport of values; parallel access is therefore faster.
If you do activate this switch, you need to enter a maximum limit for parallel processes. If you had set '7' in the above example, then the system would not have performed parallel selection, despite the switch being active.
In addition, you can enter a destination group in order to put a limit on the servers that use the parallel processes. The default value 'space' means that all available servers can be used.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
