Page tree
Skip to end of metadata
Go to start of metadata


SAP Solution Manager 7.2 provides an export/import function for solution documentation that allows you to transfer solution documentation between SAP Solution Manager 7.2 systems. As of SP05, this transfer includes Business Process Monitoring configuration. You can export your Business Process Monitoring objects from any solution/branch into an JSON file and later on import the exported file in the target solution/branch.

The export/import of Business Process Monitoring configuration includes the tranfer of the following object types:

  • Alerting (technical type: BPMON)
  • Analytics (technical type: BPANA)
  • Alerting on Analytics or BW based Alerting (technical type: BPALA)
  • Interface Channel Monitoring (technical type: IC_MON)
  • Job Monitoring (technical type: JOB_MON)

NOTE: Job Documentation is not included in Job Monitoring export/import and is not included in the solution export/import either. Interface Documentation is also not included in the Interface Channel Monitoring export/import, but is included in the general solution export/import.

How it works

 The solution export/import happens within the Solution Administration. You can access the Solution Administration via

  • Option 1: Use transaction SLAN
  • Option 2: Use transaction SM_WORKCENTER to access the Solution Manager Launchpad and in there use the tile "Solution Administration"

 Both options will bring you to the same main screen of the Solution Administration.

Export procedure

 In the Solution Administration you should decide what you would like to export. For that, choose a solution name and then select "Export" in the Global Functions dropdown box at the top-right corner.

In the opened popup window you decide what to export.
Select the branch from which you want to export the monitoring objects and select the flag for Monitoring objects.

As a scope, you can choose the default scope (= all business processes and all monitoring objects are exported) or select a reduced scope. See "How to create Scope" on how to create a reduced scope. At the end, choose "Export". This will create the JSON file with the solution content.

NOTE: Do not forget to save this file locally to your file system. Keep in mind that the export happens ind ialog, so the export for large solutions might result in a timeout.

You can find an example of such a JSON file below:


Import procedure

Once you have a JSON file, you can continue with the import. For that you should open the Solution Administration on your target Solution Manager system and choose the target solution from the dropdown list.

Keep in mind that import is only possible in SAP Solution Manager 7.2 systems as of SP05. Before importing Business Process Monitoring configuration, please make sure that all requirements listed below are fulfilled:

  1. Braches and system landscape are correctly maintained in the target solution
  2. Target solution has same logical component groups or at least logical component groups with similar product type families (ERP, SRM, SCM, Solution Manager, etc.) like in the source solution

 NOTE: You do not need to have a business process structure in the target solution. All business process contexts such as scenarios, business processes, steps and so on, will be automatically created during the import.

In the Solution Administration find tab "Imports". This tab has a history of all imports already executed in the selected solution. On the left hand side find the "Import" link. Select the link to upload your JSON file.

Specifiy the path to your JSON file and choose "Next". In the following screen, you have to define the target.

First, you have to select into which branch you want to import. You can also provide an import name.

Next, you have to select your import option. You can choose between two options:

Import option 1: New Import

  • Initial Import
  • Reimport of Business Process Configuration into a newly created business process structure  

Import option 2: Update Deployment  

You should use the first option one only in case of an initial import or if you would like to reimport configuration to create new entities. Import option 2 works as a pure update. Via this option you can update your previously imported configuration.

Last but not least you have to maintain the correct mapping between the source and target logical component groups. We strongly recommend to define the same system landscape in the target solution as you have it in the source or at least make sure that you map logical component groups of the same product family type (ECC, SCM, SRM, etc.).

To start the actual import procedure, select "Import". By default, the import takes place in background and can be monitored using transaction SM37.

After we imported part of the solution in the example above, this deployment is now available for updates when importing again (option 2).

How to create Scope

To only transfer a reduced scope of your solution, access the solution-branch via tile "Solution Documentation - Monitoring Configuration".

In there, access the correct solution/branch. Afterwards, choose the scope selection as displayed below.

In the following screen you see all scopes that are available. You cancreate new scopes via "Create New Scope".

In the next screen, open the drop-down for view and choose "Create Custom View".

In the scope selection, you can select which parts of the solution structure are included in the scope. In the example below, only the business process "Tester BPOTEST_13 process" is included.

Afterwards, make sure that "Include Originals" is selected and save the scope.

In the saving dialog, make sure that you povide a meanigfull name and decide whether others should be able to see your scope as well.

This concludes the creation of the scope. It is now available to you when exporting part of the solution documentation.



  • No labels