FICA FQEVENTS

FQEVENTS

When I began my career in the FICA world, everyone in our FICA Project team talked about FQEVENT. I often wondered what FQEVENT was. When someone from my project team helped me understand FQEVENT, I felt puzzled and couldn't grasp it. I persisted in my efforts and eventually gained some understanding. Now, I want to share my insights with you.

Basics about FQEVENTS:

When executing any FICA business process, such as posting a security deposit, making a payment, or initiating dunning, FQEVENTS are triggered in the backend, containing function modules. If a particular business transaction does not meet the client's business requirements, we have the option to enhance the function module derived from FQEVENT. This enhancement can involve screen fields or customer exits from the configuration, enabling us to define business process-specific function modules. These function modules help us to streamline and customize our business processes.

Business processes may include installment plans, payments, security deposits, dunning, collection agency activities, write-offs, etc. This approach is similarly applicable in SAP CI invoicing (BRIM)

Table: TFKFBM

Tcode: SM30

Let’s say we execute any FICA transaction like Security deposit. How do I check which events got called or trigger. 

There is a function module:

FKK_FUNC_MODULE_DETERMINE

In order to know the events for particular transaction, we need to debug that business transaction.

This FM will help us to find out the backend events for the particular transaction

We need to put a break point and look for the value of FBEVE variable. All fqevents that will be called will be going inside the FBEVE variable.

When we display the FM and can see the code which is written line by line if we execute any transaction it will read in one go but if we put breakpoint at any line that means code will stop at that line.

When we execute: 

F5 - Step by Step debugging

F6 - Skips loops and Subroutines

F7 - Skips the loop or subroutine and returns to the last cursor point

F8 - Execute and come out of debugging

Let’s say we want to post a security deposit and want to know about the events which get trigger when we post a security deposit.

Step 1: Go to TCODE: FPSEC1

Step 2: Hit enter and filled the parameter 

IF you save then security deposit will be posted but before that I want to know the FQEVENTS

For that we need to debug

Steps for Debug:

Step 1: Go to SE37 and enter fkk_func_module_determine and display

Step 2 :  We need to find FBEVE and Place a breakpoint before FBEVE

Step 3: Go back to security deposit screen and save for posting

Step 4: Once you save, Debug session2 will open

Step 5: F5 once it read FBEVE then double click on I_FBEVE

Event: 810

Keep Press F8 now and every time you can the events in I_FBEVE variable

In parallel you can also check the event in FQEVENTS, So let’s check 810 events

TCODE:  FQEVENTS

Let’s check about 810 events: Close Find tab

This event is triggered when checking the request amount on the security deposit maintenance screen

There is a sample FM which is activated

You double click; you can see the code and import/export parameter

Import parameter: 3 table entry

Once you double click I_SEC_C

E_REQUEST=I_SEC_C-REQUEST

Now go back to FM and click export parameter

Here you may see FKK_SEC_C-Request which is responsible for security deposit request amount. It ll update the amount which is requested when we post security deposit.

Similar way you can identify other event and can do analysis. 

Now go back to debug screen and check other events:

Press F8: New event get trigger that is 820

Again press F8 new event get trigger. 1113

Again press F8 new event get trigger  1310

Again press F8 new event get trigger 0800

Keep press F8 you can see the below events which get triggers: 800,2100,1330,2200,1320,0100,0045,1118,1102,1320,0045,R020,0205,0060,0040,1320,0062,0042,5500,0606,0061,0010,0030,0100,0820,0608,1107

As a functional consultant, you have to note these events and give it ABAPers to enhance/Debug as per requirements.

Keep press F8

Security deposit created and checks the security deposit documents:

Also FICA Documents: 1000000864 is posted