Application Exit Class in BRF Plus(BRF+)

[VaraPrasadT]

An application exit class in BRF+ (Business Rule Framework Plus) is a custom ABAP class that we can create and use to add custom logic to expand BRF+'s functionality. Using this class, you can add custom methods that can be called when BRF+ rules are being executed. This way, we can handle particular business needs that aren't addressed by the standard BRF+ functionality and also helps to maintain the entries as system specific entries similar like SM30 t-code.

To achieve, we need to create a class by using SE24 t-code and add interface IF_FDT_APPLICATION_SETTINGS in the class.

After adding the interface IF_FDT_APPLICATION_SETTINGS, below methods will be added.

Execute the required procedures from the interface. The custom logic you wish to use with the BRF+ framework will be contained in these methods.

Implement the custom logic :

Within the ABAP class's methods, we can write our own logic. This could include complicated computations, data validation, or any other rules unique to your business.

In my scenario, BRF+ Decision table should work like SM30 in higher systems like Quality and Production. To do, we have written logic in AUTHORITY_CHECK method in the global class which we created.

EV_SKIP_CHECK -> flag if set to TRUE, will skip standard authorization checks and will consider custom authorization check.
EV_PASSED -> Indication of whether the check was passed successfully

In the constructor class, pass gv_authority_check equal to abap_true.

To register the global class in BRF+ transaction, open BRF+ and double click on the Application component.

In this manner, application exits in a non-development or production environment can be used for decision table maintenance. I hope this blog was also helpful in providing information about BRFPlus application exits.

Conclusion :

BRF+'s application exit classes offer an effective way to increase the platform's built-in capabilities. You can modify the BRF+ framework to satisfy complex business requirements by adding additional logic to the rule processing flow through the creation of unique ABAP classes and the implementation of particular interfaces.