In my opinion BRFplus is one of the most useful development tools of AS ABAP. It provides tools for administration, transport analysis, trace, especially lean trace, catalogs but I think even great products can still be improved. In the following I suggest some improvements.
At the moment SAP ships improvements with an AddOn SAP NetWeaver Decision Service Management which need an additional license, but At the moment I don’t know about those license model but DSM has some really cool features as well as additional tools: a debugger, new UIs and deployment of rules into SAP HANA. Moreover there are complementary Partner solutions for SAP NetWeaver Decision Management. This strategy makes perfectly sense but there are still some features I would like to see in BRFplus.
Copy of Expressions with Mappings
When I create rules usually I’m working with different BRFplus applications side by side. Then I’m experimenting a lot:
- What happens to execution time if I change the expressions?
- Can I simplify rules by changing the implementation of an expression to another expression type?
- How can I make the application easier to understand?
- How can I make the application easier to maintain?
This procedure is challenging: sometimes reuse is necessary, sometimes I find out that it leads to unwanted side effects and so on. And during the process I often have to copy one expression from one project to another. Here the problem is that neither deep copy nor copy with reference to old objects makes sense: deep copy requires adjustments and exchanges afterwards and the other option will lead to fact that I work with objects having the same technical names but are still different (which you can see by the different GUIDs). For me a copy with mapping would be useful and I give you an example. Take a function f := a + b. Here a and b have guids 0815 and 0816. In the target system there are elements a and b having guids 4711 and 4712. I would like to have either the chance that the copied function uses 4711 and 4712 instead of either new objects or the old guids. As an alternative a mapping of references objects would be useful.
Documentation of Installation Prerequesites
In my opinion the BRFplus documentation of help.sap.com has a good quality. Unfortunately I couldn’t find prerequisites for the use of BRFplus: authorizations, WDA enablement, activation of certain ICF nodes and so on. Of course there are many other places on SCN in the fantasic book of Carsten Ziegler and Thomas Albrecht about BRFplus but I prefer those information contained in SAP Library. Moreover the feedback functionality of help.sap.com seems to be gone which makes me really sad.
Documentation of BRFplus-Artefacts as HTTP Resource
BRFplus offers the possibility to document artifacts. In my development projects I use wikis and office documents for documentation purposes. I would be nice to link both. If a BRFplus object or its documentation would be available as HTTP resource I could like from my documentation to BRFplus.
Proper documentation is important part of governance and administration process so I appreciate the features of BRFplus and I’m really curious what DSM has to offer.
BRF Migration Support
BRF migration to BRFplus is a difficult topic and it is likely that I will write some blogs in the future about it. I accept that automation will lead to problematic results because the result will have the weaknesses of BRF. But nevertheless additional tools would be helpful and I will make some suggestions:
- Export and import as a model: I would like to export the BRF implementation as stub objects in BRFplus that have to be customized.
- To control the migration a Network Graphic for BRFplus like in BRF would be neat: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4e/e2114b05e61eade10000000a4218 9d/content.htm?frameset=/en/4e/e2112505e61eade10000000a42189d/frameset.htm. But this would be a useful feature in general.
- There should be the possibility to compare the results of BRF and to migrated BRFplus rules.
BRFplus should be ready for HANA without Additional Tools
In fact this is one of the first questions I will ask at SAP TechEd. As HANA customer it is my expectation that the whole SAP NetWeaver platform as well as SAP Business Suite will be optimized to become a Next Generation IT System. Of course this will take some time because it is an evolutionary process but most tools should be able to benefit from HANA so that customers don’t have much effort to implement HANA. The reason is simple: a HANA implementation is expensive because we have to pay licenses, we have to buy new hardware, our administrators have to learn how to use HANA, we have to perform migrations, we have to install new clients for development and so on.
But what happens if every tool of SAP NetWeaver needs some additional licences to become HANA-ready. This would be a nightmare because we would have to evaluate a plethora of tools to evaluate and to implement. Before enterprise architects like me have the chance to evaluate whether certain HANA optimizations make sense we have to install new software components and perhaps new systems and pay licenses. This doesn’t make any sense and slows down the adoption of HANA: SAP NetWeaver has to be HANA-ready out of the box so that we have the chance to define the outline of our HANA optimization strategy of our SAP onPremise installations. Making HANA optimizations available only with certain additional licenses is a wrong signal to all IT managers because it means that the costs of Business Suite on HANA implementations are difficult to calculate because more and more additional licenses will become necessary. If IT managers get this impression then it will harm the adoption of SAP HANA.
For me it makes perfectly sense that DSM offers advanced features so that in the end we will use it in HANA and non-HANA scenarios because it makes our solutions more agile and lowers TCO. But I would like to have the possibility to test the effect of code push down to SAP HANA without any additional tools and I would like to have to benefit from it without additional systems and licenses.