Lesson Overview
At the conclusion of this lesson, you will be able to recognize the definition and concept of events in contract accounts receivable and payable and understand how to use installation-specific enhancements in your system.
Business Example
Use of convergent invoicing is industry specific. The integration between contract account balance in FI-CA and the invoice document in convergent invoicing is activated with use of event technology.
Integration of Customer-Specific Requirements
The event concept allows you to include specific source code passages in the events (defined points in a program). These passages are encapsulated in function modules and are therefore exchangeable. You use defined interfaces to include them in the events.
You maintain events and their function modules in customizing for contract accounts receivable and payable, under Program Enhancements → Define Customer-Specific Function Modules.
The FKK_FUNC_MODULE_DETERMINE function module runs for each event. It uses the sequence in the following table to determine the event modules stored in customizing that have to be processed:
TFKFBM (sample function module from contract accounts receivable and payable).
TFKFBS (applications from standard function module).
TFKFBC (installation-specific function modules).
The technical name of the sample function module is formed from the technical code FKK_SAMPLE_ and the name of the event. In the case of a sample function module defined at event 1117, the name would be FKK_SAMPLE_1117.
If the Add functions indicator is set, several function modules of the corresponding application area (industry component) and several customer-specific function modules can be processed. The modules that the application area has defined are called first, followed by the customer-specific modules. The sample module is not processed, it is used merely to define the interface.
As well as the events that are available to all industry components, additional industry-specific events also exist. You can recognize these from the encryption of the application area in the technical name.
Overview of Event Nomenclature
| From Event | To Event | Application |
|---|---|---|
| 2600 | 2799 | FI-CA Invoicing |
| 8001 | 8199 | FI-CA Billing |
| 0 | 9999 | Application-Independent |
| R0 | R999 | Utilities Industry |
| V0 | V999 | Insurance |
| T0 | T999 | Telecommunications |
| P0 | P999 | Public Sector |
| X0 | X999 | Partner Developments |
| Z0 | Z999 | Customer Developments |
| S0 | S999 | SAP Contract Accounts Receivable and Payable |
| M0 | M999 | Media Companies |
Events can be managed using transaction FQEVENT.
To use the event concept, you must have prior knowledge of the program and the data structure. If you require functions other than those provided as standard, proceed as follows:
Analyze the standard function modules from the application (TFKBS). These function modules define the required interfaces.
Copy the function group that groups customer-specific function modules according to business transactions.
Program and activate the individual enhancements/changes in the installation-specific function module.
Enter the installation-specific function module in table TFKFBC (Customizing: Program Enhancements).
Start the program that calls the enhanced event.