RBPD and continuous verification of Solution Documentation
Reverse Business Process Documentation (RBPD) is a fast and easy way for building up solution documentation in SAP Solution Manager from scratch (please find a detailed description of how to work with RBPD in this blog post). After running an RBPD analysis, you can create a SAP Solution Manager project from this analysis and start adapting this to your needs for example by assigning custom transactions or adding further elements like test cases or other documents.
If you now would like to verify if this solution documentation is still up-to-date, you could just create a new analysis project in Solution Documentation Assistant (SDA) taking your implementation project as a source and running an analysis.
The problem here is that all the SQL-based check rules from the RBPD content (which allow a much more detailed usage analysis than a transactional-based analysis) will not be available for the analysis anymore as they get lost when creating the SAP Solution Manager project mentioned earlier.
Currently, SAP is working on a solution for this issue, but until then, there is is a workaround which will be described here. It might not be perfect, but in many cases it will do the trick.
With SAP Solution Manager 7.1 SP05 a new functionality has been added to SDA which allows copying analysis projects. This copy function has two slightly different modes: the first is just a simple 1:1 copy (the source analysis project will be copied straightforward without any changes despite a new name), the second copy mode allows to additionally select a SAP Solution Manager project as a “reference”. Selecting a reference project will copy the analysis project and merge the delta from the referenced SAP Solution Manager project into the newly created copy. And this is basically the “heart” of the workaround.
To be able to perform a continuous verification of a solution documentation created from RBPD you now should create a copy of the original RBPD analysis project (the one where your SAP Solution Manager project was created from) with a reference to this SAP Solution Manager project. This will then create a new analysis project containing the original information (business process structure and RBPD check rules) AND it will merge all your changes and modifications into this newly created analysis project. This means that for example your changes to the business process structure and your manually assigned transactions will be added to the structure of the original analysis project and will be evaluated when running an analysis. Obviously, there will not be any SQL check rules assigned to your added entries as these rules are not known to the SAP Solution Manager project.
Using this workaround will allow you to continously verify an existing solution documentation created with RPBD without losing any SQL check rules from the initial analysis. The limitation currently is that no new SQL check rules will be added when using the “reference copy” feature, but at least not all check rules will get lost as it was the case before.