SAP ABAP Data Element CIFPARAPO (Parallelized Processing of Several Queues in APO)
Hierarchy
SAP_APPL (Software Component) Logistics and Accounting
   SCM-BAS (Application Component) SCM Basis
     CIF (Package) Core Interface
Basic Data
Data Element CIFPARAPO
Short Description Parallelized Processing of Several Queues in APO  
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. APO 
Medium 15 Parall. APO 
Long 21 Parallel Process. APO 
Heading  
Documentation

Use

If you set this indicator, SAP APO processes several incoming queues in parallel for different work processes. In this case, the system uses a different queue name for each data block that is sent using qRFC. The queue name contains the number of the data block.

Parallelized processing can provide a significant improvement in performance. The block size (that is, the maximum number of filter objects that are processed per block) is specified using transaction CFC3, as before.

Parallelized transfer is currently only supported for the following object types:

  • Material masters
  • Production process models
  • Sales orders
  • Stocks of all types
  • Planned orders and production orders
  • Purchase orders and purchase requisitions
  • Sources of supply (contracts, purchasing info records, scheduling agreements)
  • Batches
  • Inspection lots
  • Networks
  • Maintenance task lists
  • Production data structures

If this indicator is not set, SAP APO processes the incoming queues in serial. In this case, the system only uses one queue name for the qRFC.

Dependencies

Note that a liveCache lock can be caused in SAP APO if two integration models are activated in parallel for different object types and they both affect the same material-plant combination or resource. This also applies to object types that have subobjects. Particularly critical object types are:

  • Planed orders and manufacturing orders with the subobjects 'operations' and 'components'
  • Subcontracting purchase orders and subcontracting purchase requisitions
  • Stock transport orders and stock transport requisitions

If a liveCache lock occurs, the qRFC must be processed again, which can cancel out any potential improvement in performance or lead to a decrease in performance. In this case, you may find it necessary only to parallelize the selection in the ERP system and leave the processing in SAP APO serial.

History
Last changed by/on SAP  20100310 
SAP Release Created in