Challenge

The tool is innocent.

A woman seen from behind watches a line-up of five office workers through an interview-room window, each standing against a wall of height lines and looking faintly guilty, in late golden light.

Something doesn’t add up

BRF+ has been in SAP for years. It handles exactly the kind of rules that otherwise end up buried in custom code. Consultants can learn it. It’s already in your SAP system.

Never heard of BRF+? Open the box →

Yet at many clients it barely gets mentioned.

So what’s going on?

I’ve heard most of the reasons. Some are sensible questions. Some are habits dressed up as architecture. Some just mean nobody in the room has used BRF+ before.

BRF+ may well solve your business-rule problem. Being allowed to use it is a different case altogether. That might become your biggest challenge. Let’s look at the suspects.

The usual suspects

“Nobody here knows BRF+.”

Then someone has to go first. Even with no prior BRF+ experience, a working demo like the one on the Play page takes about two hours.

“We’ve always done this in ABAP.”

Fair enough. So what did the last rule change cost, from specification to transport?

“Our architect doesn’t like it.”

Which part, exactly? Each concern can be tested. Most of them never have been.

“We don’t have BRF+ skills.”

Gaining them is easier than you’ve been told. The scarcity isn’t in the tool. It’s in the people who were told it’s hard.

“Who supports it when the consultant leaves?”

Who supports the custom code now? And can they read it?

“What about performance?”

If performance were a problem, would SAP use it to build its own S/4HANA functionality?

“The implementation partner didn’t propose it.”

Did anyone ask them to?

“Management won’t approve another technology.”

It’s already in the system you run. What exactly needs approving?

The quiet failure

Sometimes BRF+ gets approved and nothing changes. The functional consultant still writes a specification. A developer still creates new custom tables and extends the code.

The idea was embraced. The commitment never arrived. No announcement, no training plan, no plan to become a little more Clean Core, one step at a time.

A woman in a dark suit jacket faces the viewer, a plain document held against her chest, with a small, determined smile, an office stairwell rising behind her.

Take it upstairs

You’re convinced, or nearly. The person who signs off isn’t, yet.

The BRF+ white paper makes the case in their language. Inside:

  • the cost of custom code, and where to find it in your own tickets

  • why BRF+ deserves a chance

  • the four places a buried rule usually hides: Fix, Control, Excel and Clean

  • the inevitable performance question, and a better one to ask first

  • what BRF+ won’t do, and why not

  • how to prove BRF+ works for your organisation without disturbing business as usual

  • who plays a vital role in getting BRF+ accepted, including you

  • why doing nothing is also a decision

A quick read, written to be forwarded.

One email with the white paper. Nothing else, no mailing list. Privacy policy