SAP ABAP Data Element /RTF/K_Y_PARALLEL_FIELD (Field for Use in Parallel Processing)
Hierarchy
☛ BI_CONT (Software Component) Business Intelligence Content
   ⤷ BW-BCT-ISR (Application Component) Retail and Consumer Goods
     ⤷ /RTF/P02 (Package) BW Content Retail Foundation - Outbound
Basic Data
Data Element /RTF/K_Y_PARALLEL_FIELD
Short Description Field for Use in Parallel Processing  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type FDNAME    
Data Type CHAR   Character String 
Length 30    
Decimal Places 0    
Output Length 30    
Value Table DD03L    
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 Part. 
Medium 15 Partitioning 
Long 25 Partitioning Field 
Heading 30 Partitioning Field 
Documentation

Definition

This field serves as a partitioning criterion for cases where the data is to be sent in parallel.

Use

Where the data is to be sent to the relevant Open Hub Destination in parallel from multiple processes, the quantity of data to be transferred must be appropriately partitioned. The partitions formed are read and sent by the individual processes independently of each other.

This field defines how the total quantity of data is to be partitioned: All data that possesses the same value for the specified field belongs to one partition.

Dependencies

Not every field of the Open Hub Destination is suitable as a partitioning criterion.

A suitable field has the following properties:

  • It is the left-most field of a database index. This can be the primary or the secondary index. Otherwise the system cannot carry out partitioning of the data fast enough.
  • The number of partitions should not be smaller than the number of processes that are to be deployed for the parallel execution. Otherwise, all the processes cannot be used.
  • The number of partitions should, rather, be significantly greater than the number of processes so as to guarantee a balanced load distribution.
  • The partitions should not be too small because that would result in the partitioning overhead becoming too great. The partitions should contain at least 1000 data records.

Example

Where sales data is transferred weekly, the calendar week would be an inappropriate partitioning criterion, since all the data is for the same calendar week.

In most cases the location will represent an appropriate criterion.

History
Last changed by/on SAP  20141031 
SAP Release Created in 703