Isard Haasakker

Watercolour of Isard Haasakker in glasses and an open-necked white shirt, no tie, smiling with his hand to his temple, seated at a wooden desk with books, a notebook and a coffee mug, a city skyline in the window behind him.

SAP Detective. Cutting through your mysteries.

I’m Isard Haasakker, with 30 years of SAP experience somewhere between functional and technical. Most of it at ground zero: configuring, building, testing, and finding out why things broke. I still rent SAP systems with my own money to see whether an idea works.

After enough years you notice that every project has the same suspects. So I wrote them down.

Why fiction

A case study tells you what went wrong. A story lets you sit in the room while it does. I did not set out to write a manual. I wanted to capture the human side of transformation: how people behave when deadlines breathe down their necks and data refuses to behave.

The BRF+ connection

BRF+ is not a prop in these books. It comes up in every case, and that is no accident. SAP created BRF+ for SAP. It is there for you too. Nobody told you.

In most organisations it is unknown, unloved and underused. Not because the tool is the problem. Custom development is the consensus; BRF+ is a decision. Nobody needs courage to propose another piece of ABAP. Somebody has to suggest BRF+, understand it well enough to defend it, and explain why the familiar route may no longer be the best one.

Meanwhile, the business decisions hide in custom code. The rules change, the original developer moves on, an auditor asks why SAP did what it did, and finding the answer becomes an archaeological dig. BRF+ does not make the business simple. It makes the decision visible.

For me, BRF+ is the bridge between the functional and the technical side. The books show what it looks like inside a project under pressure. The real thing deserves its own site.

To see when BRF+ is worth evaluating outside a novel, and when it is not, read the BRF+ white paper on BRF.plus →

When the mystery is yours

Some readers recognise their own project. If yours has a case that needs cracking, send me a message on LinkedIn.