BRF.plus: take SAP business rules out of custom code
Fix.
Half the code looks dead. Nobody can prove it. So how do you change anything?
Control.
Requirements change weekly. So does the custom code. How do you hit a moving target?
Excel.
Run SAP using spreadsheets. Yes, really. And finally see why SAP gave that discount.
Clean.
Clean Core says lose the custom code. Some of it runs your business. Now what?
Never heard of BRF+?
Don’t worry, you are not the only one. SAP uses BRF+ to build S/4HANA functionality without hard-coding every business rule in ABAP. Yet for many SAP professionals, like you, BRF+ has been sitting there waiting to be discovered.
The idea is surprisingly simple: give it some data, apply your business rules, and get an answer back.
Want to know more? Open the box →
When your business rules are hiding in code
Somewhere in your SAP system a threshold decides who gets approval. A table of exceptions decides which customer gets which price. A validation decides whether a product can be sold. Nobody wrote these down. Somebody wrote them into custom code with some custom tables to boot, years ago, and then moved on.
Spaghetti code, and a broken navigation system to find your way. Countless hours of debugging to try to understand when what breaks where, and why. Stick to that strategy and it only becomes worse to maintain.
Move those rules into BRF+. Your program stops deciding and starts asking. The answer stays the same, but how it is decided now lives in a set of rules you can follow.
Why nobody told you
BRF+ has been in SAP for years. It sits inside the ECC or S/4HANA system you already run, on-premise or in a private cloud. So why has nobody mentioned it? The reasons have nothing to do with the tool. The tool is innocent. Meet the usual suspects →