Skip to end of metadata
Go to start of metadata


Set up a mass activity (for the first time) in contract accounts receivable and payable. The performance is very low.


Do some general technical settings to increase the performance. 
→ Call transaction of mass activity.
→ Go to tab 'Technical settings':


1. Set the block size (technical field 'LIMIT').
Excerpt from F1-help: The block size controls "how many selected items are stored in the main memory or how large a COMMIT block is. If the block size is too small, this results in more frequent database accesses. A block size that is too large places a heavy load on the system due to data management. Adjust the block size to be in agreement with the interval size."
→ It is important to check in a test system with productive data which block size is the best one. Block size 1.000 is the standard recommended value. 


2. Set a variant to enable parallel processing (technical field 'VARI'). 
Excerpt from F1-help: "Each process started selects work packages from a worklist, completes the task, and then selects the next work package until all packages have been completed.
This procedure is implemented by splitting objects (for example, business partner or contract account) into intervals of similar size. When intervals are created (usually in background processing), their number or size can be defaulted. The number of intervals should increase in proportion to the number of processes to achieve an equal distribution of the processes."
→ The purpose is that all parallel background jobs are completed at the same time and therefore should have the same processing time. 
→ During the processing of an interval, the objects are blocked. This leads to the scenario, that bigger intervals leads to longer locking times.  
→ Customized variants have to be reviewed regularly (e.g. monthly to avoid different interval sizes). To schedule an automatic generation of the variants, please see suggestion from FICA Wiki: Automatic generation of parallel processing variant. When a variant is not refreshed from time to time, it could happen that one job and interval takes significant more time.
→ It is recommended to have a 1:10 ratio between jobs and intervals. That means, when deploy processing to 10 jobs, the best is to define about 100 intervals.
→ Sometimes it is necessary to have more or less intervals. Try to find out in a test system how many intervals are useful. As general hint the following check could be useful:

    • When the most intervals take only some seconds, too many intervals are maintained and it is useful to reduce the number of intervals.
    • When the most intervals take too much time, maybe more than one hour, it should be useful to increase the number of intervals.


3. Check, if option "Automatic Load Distribution" can be used or to have to deploy the job on several severs (option: "Explicit Load Distribution")
→ The number of jobs should be adjusted to the resources of the application servers and the database server. So contact local IT-team for setting up the load distribution.

option "Automatic Load Distribution"
Excerpt from F1-help "Jobs are divided up among application servers using the system's automatic load distribution."
→ That means, that the system decides on which server the jobs will be run, depending on resource availability. This option is recommend by SAP.

option "Explicit Load Distribution"
Excerpt from F1-help: "The jobs are distributed to the application server by means of the explicit load distribution for target hosts specified by the user."
→ If the automatic load distribution does not meet the requirements, then use the option "Explicit Load Distribution". Manually and explicitly enter the servers and the number of jobs to run on this server.


4. Set problem class in logs: "Very Important"
→ In productive environment it is also recommend to downgrade the logfile, so that only "very important" information are written.
→ For this go to tab "Logs" in mass transaction / area "settings for application log" and choose "Very Important".


Further Hints

See SAP Help: Parallelization of Data Processing for further general information. For further specified recommendations how to set up mass activities read the following SAP Consulting Notes and referred attachments:



Additional information about IS-U Mass Activities

144461Mass activities: Step-by-step setup
2032637How to debug a mass activity?


Search Terms

DE: Massentransaktion, technische Einstellungen, Variante, Einrichtung, Automatische Lastverteilung, Explizite Lastverteilung, Blockgröße, Performanz, Parallelisierungsobjekt
EN: mass activity, mass activities, Explicit Load Distribution, Automatic Load Distribution, variant, block size, performance, low, technical settings, processing time, parallel processing object




  • No labels