Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KKR (Package) CO Hierarchy Summarization
Basic Data
| Data Element | KKR_PRLNOD |
| Short Description | Number of Nodes per Process in Parallel Processing |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM04 | |
| Data Type | NUMC | Character string with only digits |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | 6 | Nodes |
| Medium | 11 | Nodes/proc |
| Long | 22 | Nodes per process |
| Heading | 4 | Node |
Documentation
Definition
Specifies how many summarization nodes per process are processed in parallel processing.
Use
You can use parallel processing for the summarization of your costs, quantities, and other data. This reduces the total runtime. With parallel processing, the system summarizes the different branches of the summarization hierarchy in parallel as different processes on different application servers. When the summarization of these branches is completed, the system processes the nodes of the next-highest summarization level.
Procedure
The number of summarization nodes per process can affect the runtime. For summarization nodes with a large amount of data (totals records), you should enter a low number. For summarization nodes with little data, you can enter a higher number.
Examples
Dependencies
History
| Last changed by/on | SAP | 19980713 |
| SAP Release Created in |
