Financial Management Blogs by SAP
Get financial management insights from blog posts by SAP experts. Find and share tips on how to increase efficiency, reduce risk, and optimize working capital.
Showing results for 
Search instead for 
Did you mean: 

FQEVENTS is a transaction for FICA related solutions and which enables easy and quick navigation to customization points within the solution. has some basic background on the FICA event concept here

Here's how to use it:

Execute transaction code FQEVENTS in ECC system.

Your screen may look slightly different - use the screen settings icon at the top to adjust as you like.

To find events which are assigned to a specific process, you can use the search term search at the top.  Scroll thru the list to find the search term you are looking for and double-click on it to pull up the list of events assigned, e.g. account determination.  (keep in mind that this list may not be 100% complete but is usually a good starting point)

The list below changes based upon the search term choice form the top window.  There is a list of events which are relevant to account determination.

Double-click on one of the events to pull up the details.

The details will provide 2 or 3 tabs depending on the event and your version of ECC.  There will always be a Documentation tab and a Function Modules tab.

The documentation tab will usually provide some background details about the event and how to use it.

The function modules tab shows what logic is called for this event and how/why.  There are 3 opportunities for logic to be provided:

  1. This is the sample module.  It is used for all industries and only used if no other logic is provided.  The function module provided here is usually empty and it is useful as a template for copy/create of your own custom logic.  In this area, the flag 'additional functions' is important. This flag controls whether one function can be called or several functions.  If empty, then it will call the customer-specific FM (for exception see #2).  If populated, then it will call the industry-specific functions followed by any customer-specific functions.  That order cannot be changed.   Table TFKFBM is used behind the scenes here.

  2. This is the industry specific logic.  If an industry solution requires logic in an event then it would be provided and assigned here.  The flag 'No customer modules' is important.  If checked, then a customer cannot provide their own logic for this event.  Very few events are limited in this manner.  As mentioned above, for some events the industry-specific logic will be called in addition to (and called first) the customer specific logic; for others, it is an either/or scenario.  Many events will have industry-specific logic provided here.  Table TFKFBS is used behind the scenes here.

  3. This is the place where customer-specific (or as in the text, installation-specific) logic is maintained.  As long as the 'No Cus.Mod' flag is not set,then the logic provided here will be called either in place of the industry-specific logic or in addition to it.  The flag in #1 will dictate whether you can assign one or several customer functions to this event.  Table TFKFBC is used behind the scenes here.  Use the pencil icon to change the customization for the event and add your own function module.

The sequence number is used when you have several functions assigned and will determine in which order they are called.  Enter the name of the function module which has your customer-specific logic, and which has the right signature based on copying from the sample function.

If an event has been designated internally as relevant for brfplus usage, then a third tab will appear as below.

This tab enables you to quickly generate the necessary brfplus function based on the data being provided in the event (This is event 0040 on ECC606).

For every event then, when it is called by the application program, function FKK_FUNC_MODULE_DETERMINE is used which derives the correct function(s) to use for the event.