Function documentationAggregation and Correspondence Request Creation

 

The ICM correspondence print uses a two-step approach to generate correspondence requests. The correspondence print run determines the correspondence data that was stored during settlement in the course of correspondence request generation, aggregates this according to customer requirements and writes it to the correspondence container.

This aggregation step is mandatory if multiple settlements are to be run within periods but only one correspondence document is to be created for each period. One important argument in favor of multiple subperiod settlements is for better utilization of the infrastructure and to reduce load peaks by processing all data at period end.

Prerequisites

The correspondence type is determined in the summarization step. If, for instance, you need different correspondence types for use in different application forms, you can use the Business Add-In (BAdI) for this purpose. Correspondence type “ICM1” is part of the standard delivery.

Features

The summarization/aggregation of the ICM correspondence requests has the following result:

  • Generation of new correspondence requests

  • ICM correspondence request now references the correspondence request.

  • ICM correspondence request is now identified to prevent subsequent aggregations.