The biggest mistake is to treat Business Rule Framework as a tool. The potential to save your company money through efficiency and productivity could be enormous. Tapping into that opportunity is often not that easy.
The first hurdle is the fear of the unknown. Even though BRF+ exists as a NetWeaver component since 2006, businesses running SAP are not aware it exists. Probably the first time it gets on their radar is when they need to maintain decision tables in S/4 HANA to activate new or enhanced functionality (e.g. revenue recognition). Then the risk is that you only focus in learning the bare minimum and discard that you can build complex decision making solutions for your custom developments.
The second hurdle is the people working with Business Rule Framework. Too often this tool is seen as an extension for development and therefore given to developers to learn and apply. However, BRF+ should be seen as configuration, generating the object oriented ABAP code with the press of a single button. The built in simulation capabilities are ideal to discuss and challenge business requirements, which is not a common task given to developers. Hence it makes more sense to teach business analysts how to use Business Rule Framework as an extension of their customising skills.
The third hurdle is linked to change management. BRF+ allows you to become agile within a waterfall project. Successful introduction of Business Rule Framework will trigger closer interaction with key users, business analysts and developers. The powerful simulation features allows the design of complex decision making prototypes before a functional specification is written by the business analyst. Decision making itself does not require a technical specification, as code is generated by BRF+. Of course technical specifications are needed to identify when to call BRF+ functions, how data is supplied to the function and what to do with the returned result. It might surprise you how difficult it will be to reorganise the teams to fit into this new way of working. The wish for change has to come top-down.
The fourth hurdle is resistance from the IT service supplier. Imagine the company running SAP uses external resources for development. With the arrival of Business Rule Framework, much of the needed development resources will evaporate and instead moved to business analysist. Knowing the previous hurdles, it is easy for the IT partner to discredit BRF+ and persuade to keep the status quo. Only forward thinking service providers with a rich portfolio of clients will embrace BRF+ as a method to expand their own customer base and claim market share from their competitors.
When all these hurdles are taken, then you need to be fortunate that you have employees who want to learn this new tool. They need to be given enough support and time to play with Business Rule Framework and become familiar with the core functionality. Some can build complex decision making within days, others need weeks. But eventually everyone can learn BRF+. It takes courage to make the first step. It takes dedication to get through the moments when you believe you are stuck. Gradually you get the confidence that any problem can be solved with Business Rule Framework. After a few successful implemented BRF+ functions you will be glad that the hurdles have been taken, as your company will reap the benefits and will never look back.