Show TOC

Function documentationDetermination of Correspondence Recipient

 

For each correspondence request, the correspondence recipients are determined for a specific correspondence type and contract. To do so, the system accesses data that you specified in the contract in application-specific correspondence recipient management. For more information, see the documentation of the application. For each correspondence recipient, you have to generate a correspondence container from the template of the correspondence request. You can use the functions of recipient management in the correspondence tool to do so. The recipient, the recipient, who receives the original, and the correspondence role are stored in the appropriate correspondence container.

It is beneficial to execute the following functions along with recipient determination, rather than defining the corresponding events:

  • Language Determination

  • Determination of Address Type

  • Determination of Dispatch Control

  • Determination of Application Form

For special cases, you can also generate correspondence containers without correspondence recipients.

Prerequisites

A contract exists for which correspondence is to be created. You entered the recipient(s) and the attributes for controlling correspondence creation in this contract.

The application does not suppress recipient determination when requesting the correspondence.

Features

The recipient is determined when a correspondence request is created.

If the application suppresses recipient determination, the correspondence tool generates a correspondence container from the correspondence request template. In this case, the application has to specify the recipient, the correspondence role, and the address number in the template.

Otherwise, the method DETERMINE_RECEIVERS of the interface assigned to the BAdI FKKCORR_EVENTS_CREATE is called. The application needs to determine a recipient for the original and any other recipients to whom you want a duplicate to be sent. In addition, the application can provide other parameters, such as the correspondence role and correspondence variant for controlling correspondence creation. The application can also suppress the address type determination for correspondence. In that case, the person number and address number must be determined within recipient determination.

If the application has chosen the BTE event concept, then it has to define the event BTE 44012020 for determining the recipient.

For a description of the interface for the BTE event concept, see sample function module SAMPLE_INTERFACE_44012020.