Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-COR (Application Component) Correspondence Tool⤷
FKKCORR (Package) Correspondence Tool
IMG Activity
| ID | _CRTL_EVENTS_CREATE | Events of Generating Correspondence |
| Transaction Code | S_ABA_72000421 | (empty) |
| Created on | 20090723 | |
| Customizing Attributes | _CRTL_EVENTS_CREATE | Events of Generating Correspondence |
| Customizing Activity | _CRTL_EVENTS_CREATE | Events of Generating Correspondence |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FKKCORR_EVENTS_CREATE |
Use
Using this BAdI, you can modify the events for creating a correspondence request to meet the needs of your application.
This BAdI uses the interface IF_FKK_CORR_EVENTS_CREATE.
Requirements
Standard settings
This BAdI calls the fallback class CL_FKK_CORR_EVENT_CREATE_DFLT # provided no filter combination was created for the application area.
Activities
The correspondence tool makes the following classes available that implement the interface:
- CL_FKK_CORR_EVENT_CREATE_DFLT
This implementation calls the Business Transaction Events (BTE) 44012000, 44012010, 44012020, 44012030, 44012040, 44012050, 44012060, 44012080 and 44012080. It ensures the compatibility with the BTE event concept of the correspondence tool. However, from the perspective of performance, this is the solution that consumes the highest level.
This class inherits from the superclass CL_FKK_CORR_EVENT_CREATE_PATT.
- CL_FKK_CORR_EVENT_CREATE_PATT
This abstract class provides certain attributes and method implementations that make it easier for you to create your own implementation.
The methods DETERMINE_RECEIVERS and DETERMINE_SENDER are implemented abstractly. Therefore you have to create your own implementations for these methods.
Call the method FORMKEY_DETERMINATION for each correspondence container during the determination of the correspondence recipient. In this way, you ensure that the determination of the application forms is uniform for all application areas.
When you create your own implementation, we recommend that you create a class that inherits from the superclass CL_FKK_CORR_EVENT_CREATE_PATT. After that, create a BAdI implementation and assign your class to it. Also assign the application area of your application as filter values.
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20090723 |
| SAP Release Created in | 730 |
