The event concept enables the integration of industry-specific and customer-specific function modules at specific points in the existing system architecture. Using installation-specific and industry-specific function modules you can enhance the standard business processes by predefined program events without modifications. Depending on the event, they can either realize alternative program logic or additional functions.
Execute transaction code FQEVENTS and you will get the following overview screen:
>Contract Accounts Receivable and Payable
>Program Enhancements
>Define Customer-Specific Function Modules
The function module FKK_FUNC_MODULE_DETERMINE is processed for each event.
Where-Used list (Ctrl+Shift+F3)
From the following tables, the function module FKK_FUNC_MODULE_DETERMINE sequentially determines the event modules defined in Customizing that are to be processed:
You must not use the following language elements in events, unless they were explicitly declared to be allowed for the given event:
(Source: www.sap.com)
Overview
Execute transaction code FQEVENTS and you will get the following overview screen:
Transactions
|
Transaction |
DescriptionDescription |
|---|---|
| FQEVENTS | Management of Events |
| SE37 | Function Module Builder |
Customizing
FICAIMG>Contract Accounts Receivable and Payable
>Program Enhancements
>Define Customer-Specific Function Modules
Further technical information
Function Modules
The function module FKK_FUNC_MODULE_DETERMINE is processed for each event.
|
Function Module |
Short Desctiption |
|---|---|
| FKK_FUNC_MODULE_DETERMINE | Determines the event modules defined in Customizing |
Where-Used list (Ctrl+Shift+F3)With clicking on the Where-Used-List Icon in Function Builder (SE37) for Sample function module FKK_SAMPLE_XXXX you can see the standard coding where the event function modules are called.
Tables
From the following tables, the function module FKK_FUNC_MODULE_DETERMINE sequentially determines the event modules defined in Customizing that are to be processed:
|
Table |
Short Description |
|---|---|
| TFKFBM | Sample function modules |
| TFKFBS | Standard function modules for Industry solutions |
| TFKFBC | Installation-Specific Function Modules (Customer Function Modules) |
Flags
|
Flag |
Description |
|---|---|
| Additional Functions TFKFBM-MEHR |
Specifies whether several function modules can be processed in this event or a maximum of one. >If the indicator is set, several function modules of the corresponding industry solution and several customer-specific function modules can be processed. The modules that the application area has defined are called first, and then the customer-specific modules. > If this indicator is not set, only one function module is called. In this case, a customer function module has priority over an application-specific function module. |
| No Customer Module TFKFBS-NOCUS |
If this indicator is set, customer function modules are not taken into account for this event in the application area in question. |
Programming Restrictions
You must not use the following language elements in events, unless they were explicitly declared to be allowed for the given event:
- COMMIT WORK
- ROLLBACK WORK
- CALL FUNCTION 'DEQUEUE ALL'
- Deletion of locks that you have not set yourself
- Implicit database commits triggered by RFC calls or by a WAIT statement
(Source: www.sap.com)
Continue exploring
Knowledge guide
Continue with related SAP knowledge.
Save this guide, return to the Knowledge Navigator or review the author profile for more practical SAP context.
Sachin H. Patil
View full profile →SAP FI-CA Consultant & Architect
Practical SAP notes, structured for review, reuse and long-term maintenance.