SAP ABAP Data Element BLKSIZE_UR (Block Size in Processing of Mass Simulation Indexes)
Hierarchy
☛ IS-UT (Software Component) SAP Utilities/Telecommunication
   ⤷ IS-U-BI (Application Component) Contract Billing
     ⤷ EE20 (Package) IS-U: Billing
Basic Data
Data Element BLKSIZE_UR
Short Description Block Size in Processing of Mass Simulation Indexes  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type INT4    
Data Type INT4   4-byte integer, integer number with sign 
Length 10    
Decimal Places 0    
Output Length 10    
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 Block Size 
Medium 15 Block Size 
Long 27 Block Size 
Heading 10 Block Size 
Documentation

Definition

Block size is a parameter that you must enter in transaction Mass Act. Billing of Sim. Indexes (EAMS01) or for report Mass Billing of Simulation Indexes . It controls the internal processing of mass simulation indexes. You use the block size to influence the performance of mass simulation. An optimal block size depends greatly upon the hardware used and can only be determined by tests in the system involved.

The following example shows how the block size is used for the processing of mass indexes:

  • You bill mass simulation indexes with transaction EAMBA. You choose a variant with interval size 1000 and block size 50. Transaction EAMS01 bills the simulation indexes in parallel jobs that each have an interval with maximum 1000 indexes to be processed.
  • The 1000 indexes in each job are processed in blocks of 50 indexes. The following steps are run for each block:
    1. The installations belonging to the 50 indexes are locked.
    2. The billing-relevant data is read with mass access.
    3. The installations are simulated and the data of the billing documents is compressed for transfer to CO-PA.
    4. Database changes (CO-PA, indexes and, if necessary billing documents) are executed and completed with a database commit. The block on the 50 installations is removed.
  • The lower limit for block sizes is 1. The maximal upper limit is the interval size of the variant.
  • A block size that is significantly higher than 1, optimizes the runtime by mass access to the database, leads to fewer database commits and optimizes the update to CO-PA.
  • Block sizes must not be too large, especially when you start parallel jobs. Otherwise many installations must be locked at the same time. This can overload lock management and the database.

History
Last changed by/on SAP  20050224 
SAP Release Created in 463