It could be the case that a very large number of consumption items is to be rated for a business partner and you want to rate the consumption as total consumption. During rating, this can lead to bottlenecks pertaining to the required working memory and the data volume to be exchanged with the rating system. To avoid bottlenecks, you can aggregate the consumption items of a business partner before rating takes place, and then rate the aggregate.

During rating, you can either have the aggregates available virtually, or you can save them to the database. Saving them is particularly recommended, if not all consumption items of a business partner can be loaded to the working memory at the same time, due to system limitations.

In the standard system, the aggregation of consumption items and the rating of the aggregates resulting from them takes place in a single rating run. However, you have the option of decoupling these steps and rating the aggregates later in a subsequent rating run. You choose this separation of the steps in transaction FKKBIX_RATE_M by choosing the appropriate level of processing.