SAP ABAP Data Element CPO_PARA_VARIANT_PO (Parallel Processing Variant for Purchase Order Generation)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
LO-MDS (Application Component) Merchandise Distribution
⤷
WFRM (Package) ISR: Cross-Docking and Floor-Ready Merchandise

⤷

⤷

Basic Data
Data Element | CPO_PARA_VARIANT_PO |
Short Description | Parallel Processing Variant for Purchase Order Generation |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | W_PARA_VARIANT | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | TPARA_VARIANTS |
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. PO |
Medium | 19 | Parallel Variant PO |
Long | 37 | Parallel Processing Variant PO |
Heading | 19 | Parallel Variant PO |
Documentation
Use
If you enter a parallelization variant, it affects collective purchase order generation. The system then runs parallelization in the variant as detailed.
Reference figure for the number of objects that are processed in a packet is the vendor. By entering a limiting value, you can restrict the maximum number of materials that can be processed in a packet.
You can create parallelization variants with transaction W_PARA.
You can also use parallelization variants for the following events:
- Issue document selection
- Parallel processing variant for material processing
- Updating issue documents
The best results are possible if you create parallelization variants for collective purchase order generation. This is because this function requires a larger proportion of system runtime when compared to selection, aggregation and updating.
History
Last changed by/on | SAP | 20010607 |
SAP Release Created in | 46C |