When backflushing, it is important that response times are fast and that a large volume of data is processed quickly. In the standard system, the following sub-functions are automatically linked to backflushing:
You can differentiate between sub-functions that must be carried out quickly (critical) and sub-functions that can do not have to be carried out immediately (non-critical). This means that you can influence the performance of the backflush. The sub-functions you define as non-critical are saved in the background and are then processed later.
You can define the sub-functions that are to be carried out later in Customizing.
The sub-functions that are not posted immediately in the backflush are collected in a work list where they are aggregated if necessary and are processed later in a background job that is carried out periodically.