Collective Runs
Definition
Beside V1 and V2 function modules, there are also “collective run” function modules. Unlike V1 and V2, these function modules are not updated automatically. They are only updated if report RSM13005 starts the update. Then, all the calls for the function module are collected, compressed (see example), and updated at one time. Collective runs are handled like V2 update modules.
Use
When programming a transaction, you use collective runs if a function module is called frequently, and you want to avoid each call causing a database update.
Integration
You can see the collective run update modules in update management up until the point when the report that triggers the processing is started. The status of the update records whose V1 and V2 modules are processed correctly, but still contain collective runs, is V2.
Example
A function module increases a statistical entry by one. It is called 10 times during the transaction. If you implement the collective run as a V2 function module, the function module is updated 10 times (written to the database 10 times) after the V1 update is complete.
If you classify this as a collective run, you can run the update in one go and at any time. The program calculates that the statistical entry must be increased by 10 and does this in the database operation.