Skip to Content

Blueprint Generator

With SAP Solution Manager 7.1 SP10, a new method has been introduced in to document the business process using Solution Documentation.

The traditional ways to document the business processes are Manual, Excel Template Upload or  RBPD/SoDocA. Let us have a brief overview on each of these methods

  • Manual/Excel Upload:

If the Business Process information is up-to-date and readily available, then Documentation of business process can be done manually or using Excel Upload interface. Excel upload interface saves lot of time since the standard template is useful not only to build the baseline documentation (3 level hierarchy and transaction code) but also helps to upload multiple process documents in a faster way.

  • RBPD/SoDocA:

In a situation where the Business processes are not documented and readily available, earlier we had the option to run RBPD analysis and get a jump start to document business processes based on usage analysis. SoDocA can be useful to update the existing project defined in solution manager based on usage analysis.

Now SAP has introduced ‘Blueprint Generator’, which is the faster way to document business processes in a modular approach. It is also called Process step library.

Purpose: The aim is to get the SAP Module based Business Processes in solution manager based on usage analysis data from the managed system.

Usage data source:

Option 1: Work load statistics data from ST03N of the managed system

Option 2:  From SolMan UPL cube


System Preparation, Basic and Managed system configuration should be complete.

For Option 2, additionally, UPL should be activated in the managed system and the usage data should be available in Solution Manager infocube. For more information please refer below link–solution-manager-update

SAP Note 1955847:UPL: Activation Procedure and Authorization Handling in SAP Solution Manager.


Below are the steps to run Blueprint generator:

  1. Run Report RUTILITY_BLUEPRINT_GENERATION (This feature is also available in SEA – Scope and Effort Analyzer with SolMan 7.1 SP11 onwards)


   2.  This report execution will take some time depending on the usage data. Also it is advisable to run this report during off peak load period of the day.


  1. Once the report is executed, the project is created with the defined name. Go to solman_admin transaction code



   2.  Go to solar01 Transaction code to see the Business processes.

   3.  See that the business processes are defined as below with 3 Level hierarchy defined in the project.


  4.  The graphical view shows the correlation between 3 level hierarchy and process step library


  5.  Similarly the process step library as seen in the project


  6.  The custom transactions are seen as a separate folder ‘Customer’, they are grouped by development class.


Define E2E Business Process from Process step library

Once the process step library is ready, we can manually define E2E Business process as under

A new scenarios is created say ‘Order to Cash’ and the relevant business process along with the steps can be copied from the process step library and arranged sequentially. For example:



  • Faster documentation of business process based on usage analysis
  • Get insight into the custom transaction and reports based on usage analysis
  • Re-usage of centralized Business Process across all phases in Test Management
  • Once the Productive solution is in place, Business Process Monitoring can also be setup.


This document will help you to understand the concept of Blueprint Generator to create process step library to document Business Processes in Solution Manager

About the Author:

     She is part of TCS RunSAP CoE team having expertise in SAP Solution Manager functionality from ALM & RSlaF like Solution Documentation, SoDocA, Test Management, BPCA, BPMon,            BPAnalytics, JSM etc.

You must be Logged on to comment or reply to a post.
  • Hi Kavita,

    This is great functionality. Does it catch anything non-ABAP? For example:

    • Webdynpro (which is ABAP, but different)
    • Java
    • EP


    Lori Sanders

      • Hello Kavita,

        many thanks!

        The question still is whether or not the complete Business Blueprint will be generated for all the tcodes, reports, etc. for Addons like IS-H, IS-U.

        I do not have any doubs that in case of usage of standard modules FI/CO, MM such Business Blueprint will be generated.

        Or what is in case of usage of customer tcodes, beginning with Z or Y?

        • Dear Alex,

          I have no clue for the IS-H or IS-U specific transaction usage as we didnot have that scenario.

          However for custom transaction code (Z or Y), there is a separate Scenario created - Customer and all the Z and Y tcodes are stored. Point 6 of the above document shows the same with screen shot.

          Best Regards,

          Kavita Meswani

  • Hello Kavita,

    great blog!

    How much time (after activation of UPL) is needed to collect the data (tcodes, reports, etc.) and to have working business blueprint with the report RUTILITY_BLUEPRINT_GENERATION?

    • Dear Alex,

      After UPL activation, typically we should run the report after one month of UPL data is available in the info cube. Advisable is to have 3 months data to have exhaustive usage data that cover transaction usage that are not frequent, eg in finance - month end transactions/reports.

      The execution time of the Blueprint generator report depends on the amount of usage data of the business processes that are used in the system. However we were able to run the report within few hours.

      Best Regards,

      Kavita Meswani

      • Hello Kavita,

        is there any information, which data (standard sap module and/or Add-Ons) will be collected within managed system.

        For example we use besides standard sap modules also Add-Ons IS-U, IS-H.

        Will the data for those Add-Ons (tcodes, reports, etc.) also available within Business Blueprint?

        Thank you!

        • Dear Alex,

          We had executed this report and got results for standard as well as custom Transaction codes/programs running in the Managed system.

          However I have no clue for the IS specific transactional usage data, I believe it depends on whether this data is captured by UPL or not.

          If you have activated UPL in the managed system then please check and do let us know.

          Best Regards,

          Kavita Meswani

          • Hello Kavita,

            the very interesting point is which Business Blueprint structure do you get for custom transactions/programs? It will be great, if Solution Mansger does have so much "inteligence" right now. 😆

            Some questions about configuration:

            We just executed the both UPL tasks within managed configuration (see the picture bellow):


            As consequence the job /SDF/UPL_PERIODIC_EXT_JOB will be scheduled within client 000 in managed system.

            What are the additional settings for the usage of UPL?

            We do not realy need to activate the whole Custom Code Management within our Solution Manager. We primarily want to use UPL for Blueprint.

            Thank you!

  • Hello Kavita,

    thanks for sharing this interesting description related to the usage of Blueprint Generator: here the process you described for option 2 is based on the usage SolDocA.

    In the past I used SolDocA: in my experience, in order to properly analyze the ST03N (or now UPL cube content), it was crucial to start from a "good" analysis project (i.e. a project with a good business process hierarchy and transactions assigned to the proper process steps).

    Unfortunately when I tried to create an analysis project from the SolMan BPR ( I was not able to create one with a good business process hierarchy and a proper transaction assignment.

    But in the printscreen after point 5 ("5. Similarly the process step library as seen in the project") in your article I notice a nice business process hierarchy and I imagine that core transactions are properly assigned to process steps.

    Is this content part of the Report RUTILITY_BLUEPRINT_GENERATION? Could you share addtional info about this content?

    BR and thanks, Andrea

    • Dear Andrea,

      Below are the points for clarification:

      Blueprint generator is different from SoDocA or RBPD, here the report RUTILITY_BLUEPRINT_GENERATION will give you the results in terms of modular structure as shown in point # 4

      So you just need to run above report and a new implementation project will be created that has the required Modular Structure based on the usage of the Transaction in the sysytem. There is no separate content/Existing project required to run this report.

      Hope this answers your query.

      Best Regards,

      Kavita Meswani

      • Hi Kavita,

        thanks for your answer!

        Would be great to have the chance to execute RUTILITY_BLUEPRINT_GENERATION in a real system: is there a sandbox system/landscape where the Blueprint Generator is configured and some usage data are available?

        BR and thanks, Andrea

  • Hello Kavita,

    one additional question regarding the usage data source.

    You write, that there are 2 possible ways to do this:

    Option 1: Work load statistics data from ST03N of the managed system

    Option 2:  From SolMan UPL cube

    How this selection works?  Where can I choose whether ST03N load statistics or solman UPL cube option should be used?

    Thank you!

    • Dear Alex,

      There is no selection option provided when we run the Blueprint Generator report.

      I believe if UPL is activated in the managed system, then preference is given to the UPL data, else the report will fetch the usage data from ST03N.

      Best Regards,

      Kavita Meswani

  • Hello Kavita,

    is it possible to select the upl data in the selection screen of this report? You were refering to upl but I dont know how to select it.

    Best Regards and thanks!


  • Hello Kavita,

    We have a business blueprint created using the utility program. How to update that existing blueprint with the latest changes that have been made.


    • Volker,

      The way we did the update to the existing documentation was to create a delta project and run the RUTILITY_BLUEPRINT_GENERATOR on the delta project which captured the changes/ updates since the last it was run. Once the transactions have been captured, you can insert them in the existing hierarchy.  This might be a bit time consuming.