Based on a request from the application, the correspondence tool creates a correspondence container for each recipient from a correspondence request. Each correspondence container saves references to correspondence data in an abstract form and the control parameters for creating correspondence.
The application links to the correspondence tool using the event specific to a correspondence type (BTE, BAdI, event of FI-CA event concept) to create a correspondence request. During creation of the correspondence request, a series of events of the correspondence tool are run that the application uses to define the correspondence tool. For more information about which events of the correspondence tool the application includes and how it uses the functions, see the documentation for correspondence for each specific application.
You can also define these events specifically for your installation, and thereby adjust them to the requirements of your company.
The business process that is to be documented by the creation of correspondence has been executed for the business object (for example, contract or account).
The recipients are assigned and the system settings for the correspondence type and control parameters used for creating the correspondence are maintained.
The creation of correspondence with the correspondence tool is divided into the following steps:
The application creates a correspondence request.
The application transfers the following information to the correspondence tool:
Template of the correspondence request that contains the business data
The template consists of the correspondence header and the correspondence data record. The correspondence data record contains data or references to data that cannot be stored in the correspondence header.
Archiving ID for optical archiving
Options:
Suppress company code determination
Suppress sender determination
Suppress recipient determination
Suppress language determination
Suppress application form determination
Processing of a series of events for the correspondence request that are used to determine correspondence-specific data:
Correspondence recipient (business partner)
Company code
Sender
Creation of a correspondence container for each correspondence recipient from the correspondence request template
The recipient, the recipient, who receives the original, and the correspondence role are stored in the appropriate correspondence container.
If the application has suppressed recipient determination, the correspondence tool generates a correspondence container from the correspondence request template. This means that the application needs to enter the recipient and his or her address in the template.
Processing of a series of events for each correspondence recipient that are used to determine correspondence-specific data:
Recipient’s address
Recipient’s language
Archiving ID for optical archiving dependent on the recipient
Form, layout
Dispatch control (print, fax, e-mail, SMS)
The data and control parameters are saved in separate correspondence containers for each recipient.
Using BAdI FKKCORR_EVENTS_CREATE
, you can adapt the creation of correspondence to the requirements of the application. The interface IF_FKK_CORR_EVENTS_CREATE
, which is assigned to the BAdI, defines methods that are run as events during the creation of a correspondence request.
The following BAdI events are run during creation of a correspondence request:
Name | Method |
| |
| |
| |
|
The following BAdI events are run for each correspondence recipient:
Name | Method |
| |
| |
| |
| |
|
Each application has to create its own implementation and assign the application area as a filter value to the application.
If the recipients are business partners, then the implementing class can inherit from class CL_FKK_CORR_EVENT_CREATE_PATT
, and you have to implement the protected methods of this class.
Example
Enhancement implementation FKKCORR_EXP_EVENTS_CREATE
with the implementing class CL_FKK_CORR_EVENT_CREATE_0BAI
Fallback class CL_FKK_CORR_EVENT_CREATE_DFLT
, which implements the BTE event concept, is assigned to the BAdI. All existing and new applications that do not create their own implementation and do not have filter assignment for their application area use the BTE event concept.
The following tables show in which methods of fallback class CL_FKK_CORR_EVENT_CREATE_DFLT
which BTEs are processed, and which standard modules exist for single BTEs.
The following BTE events are run during creation of a correspondence request:
Method | Name | BTE | Standard Module |
|
| ||
|
| ||
|
| ||
|
|
|
The following BTE events are run for each correspondence recipient:
Method | Name | BTE | Standard Module |
|
| ||
|
| ||
|
| ||
|
| ||
|
|
|