Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
SCM-BAS (Application Component) SCM Basis⤷
CIF (Package) Core Interface
Basic Data
| Data Element | CIFPARSEL |
| Short Description | Parallelized Selection in ERP System |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Par. Sel. |
| Medium | 15 | Parallel Selec. |
| Long | 20 | Parallel Selection |
| Heading | 0 |
Documentation
Use
If you set this indicator, the ERP system selects objects that are to be transferred to SAP APO in parallel in different work processes. The parallelization takes place with reference to the blocks of a filter object type. Each work process processes a filter object block. You specify the block size (that is, the maximum number of filer objects to be processed per block) using transaction CFC3 as before. For more information about the influence of block size on parallelization, see Dependencies.
Parallelized selection can lead to a significant increase in performance.
Parallelized selection is currently supported for the following object types:
- Material masters
- Production process models
- Sales orders
- All stock types
- Planned orders and production orders
- Purchase orders and purchase requisitions
- Sources of supply (contracts, purchasing info records, scheduling agreements)
- Production data structures
If this indicator is not set, the ERP system selects the objects in serial.
Dependencies
The performance of the initial data transfer is not only determined by parallelization, but also by the size of the filter object blocks. If you specify a large block size in transaction CFC3, only a few blocks may be formed within the filter object type. This means that only a few work processes can be parallelized. However, for smaller block sizes it is possible to have a higher degree of parallelization although only a small number of objects are transferred to SAP APO per block. If you would like to optimize the performance of the initial data transfer, you also have to take into account the size of the filter blocks in addition to parallelization and adjust your system depending on the data being transferred.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
