Show TOC

Procedure documentationCreating an Analysis Project


You want to create a new analysis project. You set the following properties when you create an analysis project:

  • Source of the analysis project

  • Parameters for importing data from the source

  • Definition of nodes from the source structure


  • You have called the Solution Documentation Assistant.

  • You have a source for the analysis project, a Solution Manager project, for example.


Under Common Tasks choose Create Analysis Project.

You can also create an analysis project in the Analysis Projects:

  1. Choose Analysis Project.

  2. Choose Create in the Analysis Projects area.

The Create Analysis Project guided procedure is displayed, to help you create the analysis project.

Selecting the Source for an Analysis Project

You determine the source of the analysis project, for example a Solution Manager project. Specify the type of the source and then select the source on which you want to base the new analysis project:

  1. Open the input help for Source Type and choose an entry, for example Solution Manager Project.

    The standard view of the table of available sources for the selected type is displayed. The source type is displayed in the table header.

  2. Select a source in the table.

  3. Choose Continue to call the next step.

Note Note

One or more other analysis projects may already be based on this source. You are told if this is so.

Using a source more than once is necessary, for example, if you do not want to overwrite an existing analysis project. You create another analysis project for the same source, with different or new definitions, instead.

End of the note.
Defining Profiles

Specify the name of the analysis project and the parameters for transferring specified object types from the source.

A name for the analysis project is proposed in Name. The proposal includes the name of the source (the description of a solution or the project ID of a Solution Manager project) and the number of analysis projects already created for that source.

Example Example

SM_PROJ01_00003 for the name of the third analysis project for source SM_PROJ01.

End of the example.
  1. Optional: To change the name, click on the name and overwrite the proposal.

  2. Now specify the parameters for importing the following objects from the source:

    • Import Structure Objects, for example, business scenarios, business processes, or business process steps. Set the identifiers for the following options as required:

      • Only copy structure objects in scope. The flag is not set, by default. This indicator is not supported by all source types and is thus not always visible.

        Note Note

        In Scope refers here to the source, for example the Business Blueprint structure of the underlying Solution Manager project. Choose this option only to copy objects into the analysis project that are identified as In Scope in the source.

        End of the note.
      • Copy master data. The flag is set, by default. Clear the flag if you do not want to analyze the master data.

      • Copy organizational units. The flag is set, by default. Clear the flag if you do not want to analyze the organizational units.

      • Copy interface scenarios. The flag is not set, by default.

    • Import Content Objects, for example, transactions, reports, and function modules (RFC). Flag one of the following options:

      • Only copy content objects in scope. The flag is not set, by default.

        This indicator is not supported by all source types and is thus not always visible.

      • Copy all content objects. The flag is set, by default.

      • Do not copy any content objects. The flag is not set, by default.

    • Threshold Value: The default value is 1.

      The objects you selected (transactions, reports, RFC-enabled function modules) are converted into check steps during the import. The selected threshold value that you select applies to all check steps of your analysis project. You can change the threshold value for specific check steps if required.

      Example Example

      If you want to determine whether transactions or reports are even used, for example, leave this value set to 1.

      If you want to check which objects are productive and therefore used frequently, select a corresponding estimated value as the threshold value, based on the size of the organization, for example.

      End of the example.
  3. Choose Continue to the next step, or Back to the previous step.

Defining Structures

Do not copy specified source structure nodes to the analysis project.

The structure of the future analysis project is displayed under Analysis Project Structure (name).

All nodes are transferred, by default. The Selected flag is set for all nodes.

  1. Remove the flag to not copy a specified node.

    Note Note

    Selecting a node also selects its higher-level objects. If, by contrast, you deselect a node, all its subnodes are automatically deselected as well (as in Business Blueprint structure).

    End of the note.
  2. Choose Create to create the analysis project, or Back to call the previous step.


  • The analysis project is created.

  • The name of the analysis project is displayed.

  • The time when then analysis project was created is displayed.

  • The number of copied business scenarios, business processes, business process steps, and master data is displayed, as well as the number of check items and check steps.