Unbox

Understanding the basics.

BRF+ is a black box that needs opening.

You’ve heard the name. In a workshop, from a developer, or on this site a minute ago. Time to look inside. No ABAP required.

Where it lives

BRF+ is short for Business Rule Framework. It’s part of SAP ECC and S/4HANA, on-premise and private cloud. No add-on, nothing to install. Type BRF+ in the command field and the workbench opens. That’s the whole installation.

If nothing happens, or the browser shows an error, ask your Basis team to activate the BRF+ services in a test system. Then check with the authorisations team that you have the access you need.

One function, one question

The core object is a function. It works like this:

You decide what goes in: a customer, a material, an order value, a country.

You decide what comes out: a yes or no, a price, a route, a message.

Then you decide what happens in between. That middle part is your business rule.

What goes in the middle

Most of the time, a decision table. Condition columns on the left, result columns on the right. Each row is one combination and its answer. Think spreadsheet.

When a table isn’t enough, you get decision trees, formulas, lookups and rulesets with conditions and priorities. You combine them like building blocks. You configure them. You don’t program them.

Prove it before anyone builds it

Run the function in the workbench with test values and watch the answer come back. No orders, no customers, no live data needed. Sit next to the person who owns the rule, change a row, run it again.

When the business says “yes, that’s what we meant”, they aren’t approving a specification. They’re approving a working rule.

From rule to code

Once the rule is approved, SAP generates object-oriented ABAP from what you configured. It also gives you a code template: a few lines a developer places in the user exit, BAdI or enhancement point where the decision is needed. The program fills in the inputs, calls the BRF+ function and acts on the answer.

That’s the contract. The program stops deciding and starts asking. Next time the rule changes, you change the rule. The code around it remains unchanged. Your developer gets their evening back.

Not a toy

Functions live in applications, versions are kept, and changes travel by transport like any other configuration. SAP uses the same framework to build parts of S/4HANA itself.

Rather feel it than read it?

Play puts all of this into a penalty shoot-out. Two hours, one goalkeeper, not a line of ABAP rewritten.

What the box won’t do

BRF+ decides. Your program still supplies the context and acts on the answer, so someone still builds both ends. And BRF+ won’t tell you which rules belong inside it. That takes judgement. Yours.