Obviously you would like to use standard SAP functionality as much as possible, but there are circumstances where you have business processes that require an enhancement. When you need to build custom solutions then there are decisions that need to be made by the new programs in order to get to the desired result.
Coding decision making is often very complex for many different reasons:
- The business requirements are not fully known when you start building the new functionality. This is very common, as it is difficult to know all scenarios up front. Quite often the real requirements appear during testing, or even after deployment.
- The scope for functionality expands after deployment. As the world is constantly changing, it is to be expected that business processes will be affected as well. This is especially true for new functionality that is not available in standard SAP. These new processes are bound to change.
- New acquisitions trigger new requirements. You might have a stable new process that fits your current enterprise structure. However, when new companies are added to the SAP system, do not be surprised when new rules need to be applied.
The reasons listed above have nothing to do with the quality of the deliverable that has been deployed. Unfortunately you can expect that coding decision making in the first version will undergo changes in the future. If you wonder why coded enhancements become a jungle after many years, then it is simply due to the need to adopt to changing circumstances.
Business Rule Framework is the ideal tool to handle the complex decision making, as you design the solution like it were configuration, you have power simulation to validate the known business scenarios and the code gets generated by pressing a single button.
This tool is especially able to make a huge impact when you have a remote development team in a different continent, as these developers only need to focus on collecting the data for decision making, offering this to the BRF+ function and do the correct action based on the returned result. These tasks are much easier to code and chance of errors are greatly reduced.
Using Business Rule Framework allows you to apply the core concepts of rapid application development:
- You can prototype decision making and get business approval before a single line of code is written.
- An approved prototype is the basis for the functional specification.
- There is no need to write a technical specification for the decision making, as BRF+ generates the code and no developer needs to get involved.
- While the developers are coding the collection of data and actions based on decision making, you configure the decision making using BRF+ in parallel.
- If new business rules require new decisions and the signature of the BRF+ function requires no change, then developers only need to get involved when new actions need to be coded as a result of decision making.
You quickly realise that BRF+ can reduce the lead time for development enormously. Also the chance to deploy solutions fit for purpose will dramatically increase.
Knowing these benefits, makes you wonder why Business Rule Framework is not embraced by all companies running SAP.