SAP ABAP Data Element TV_PCKSIZE (RM: Packet Size for Parallel Processing)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ FIN-FSCM-TRM-MR (Application Component) Market Risk Analyzer
     ⤷ FTBB (Package) Risk Management Basis
Basic Data
Data Element TV_PCKSIZE
Short Description RM: Packet Size for Parallel Processing  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type INT2    
Data Type INT2   2-byte integer, only for length field before LCHR or LRAW 
Length 5    
Decimal Places 0    
Output Length 5    
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 Pckt Size 
Medium 15 Packet Size 
Long 20 Packet Size 
Heading 9 Pckt Size 
Documentation

Definition

Indicates the number of financial objects that can be processed together in a parallel task. This value must be seen in conjunction with the number of tasks available for parallel processing.

The total number of financial objects to be processed divided by the packet size gives you the number of RFC calls that can be used for parallel processing. Each RFC has its own main memory area in the synchronizing batch job, in which the results data is collected. For this reason, you should avoid setting too many RFC calls (maximum of about 1000). If the packet size is too small, you get a large number of RFCs. If the packet size is too large, there is a danger that certain tasks will take a long time to process large packets of complex transactions, which has an adverse effect on performance. The packet size should never exceed the quotient "financial objects: number of available tasks".

Example

  • If you have 100,000 financial objects and 10 available tasks, the packet size should not be smaller than 100 financial objects, and not greater than 10,000. A packet size of 100 gives you 1000 RFCs for parallel processing, whereas a packet size of 10,000 gives you exactly 10, which corresponds to the number of free tasks. You must find out the optimal ratio by testing in the relevant system environment.
  • The evaluation category "Limit: Create Totals Records", however, requires a packet size between 1 and 5, depending on the number of limit types and values you have in your system. In this case, each limit type already summarizes several financial objects.

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