Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KALC (Package) Cost Accounting allocations RK-S
Basic Data
| Data Element | KALC_PROCG |
| Short Description | Cycle Run Group |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KALC_PROCG | |
| Data Type | CHAR | Character String |
| 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 | 10 | Run group |
| Medium | 15 | Cycle run group |
| Long | 22 | Cycle run group |
| Heading | 6 | RunGrp |
Documentation
Definition
You can use cycle run groups to allow the cycles for an allocation type to run parallel, when these do overlap in their objects.
Each time, those cycles can run parallel that are assigned to different run groups (except group 0000).
If, for example, the definition for your cycles is split strictly by company code, so that no cycle needs the results of another, then you can assign your cycles to different run groups, which you can, for example, name as for the company codes. Then you can execute the cycles in parallel. Note that SAP does not yet perfom a validation of whether the cycles really do not build on one another. This is still your own responsibility.
If you do not want to use the cycle run groups, you do not need to maintain anything, as the default case (group 0000) corresponds to the situation in Release 3.0
History
| Last changed by/on | SAP | 20050615 |
| SAP Release Created in |
