Creating an Analysis 
You want to create a new or an optimized analysis. You set the following attributes when you create an analysis:
The analysis project for which you are creating the analysis
The analysis name
The analysis start time
The systems
Timeline
General settings
You have called the Solution Documentation Assistant.
You have an analysis project for which you want to create the analysis.
Analyses that check function modules (RFC) ensure that the current SAP Support Package for software component ST-PI is installed in the managed systems.
For analyses that comprise the checking of transactions and function modules (RFC), the workload statistics are drawn from the possible sources in the following order:
BI InfoProvider
SAP EarlyWatch Alert (EWA)
Managed System (via RFC)
For the data to be read from the SAP NetWeaver Business Warehouse, you have ensured the following:
An RFC connection between the SAP NetWeaver Business Warehouse and the SAP Solution Manager system has been set up.
The BI objects are installed and activated.
Data for at least one closed month is available.
Analyses of applications covered by E2E Diagnostics, e.g. Java Web Dynpro applications and components, Java Web Services, Servlets and iViews, ensure the following:
The SAP NetWeaver Business Warehouse, which contains E2E Diagnostics data, is correctly configured.
The SAP NetWeaver Business Warehouse contains InfoCube OSMD_PE2D.
The InfoCube OSMD_PE2D has been filled with data for the systems to be analyzed regularly, for at least the last complete month.
Under Common Tasks choose Create Analysis.
You can also create an analysis for a specific analysis project in Analysis Project Overview:
Choose Analysis Project.
Select the analysis project for which you want to create an analysis in the Analysis Project area.
In the Analyses for Analysis Project '<name of analysis project>' area, choose Create.
The Create Analysis guided procedure is displayed, to help you create the analysis.
Enter data as required.
Choose Continue to call the next step.
Specify the analysis project for which you are creating the analysis, and the time to start the analysis.
Note
If you start creating the analysis in the Analysis Project Overview, specify the analysis project there.
Open the input help for Analysis Project and select an entry; this is not necessary if the analysis project has already been set.
Click the Name field and give the analysis a name.
Open the input help for Scheduling Mode and choose one of the following entries:
Immediately, to start the analysis immediately after creation (default).
Scheduling to set a start time for the analysis as follows:
Click in the Planned Start Date field or open the corresponding entry help to specify a Date for starting the analysis.
Click in the Planned Start Time field and enter a Time.
In this step, you determine the logical components that are to be used for the analysis. The logical components that are assigned to the analysis project are displayed in the Logical Components list.
The Selected indicator is always set for logical components that have been assigned in at least one test step in an analysis project. To include logical components in the analysis to which no check steps are yet assigned, set the flag.
Note
Only use logical components in the analysis, to which no test steps have been assigned yet, if you receive data, for example workload statistics in the analysis results and wish to automatically create test steps for transactions, reports or function modules (RFC). This can be useful, for example if you create an analysis for the first time and wish to check which objects are used at all and if so, how often. In this way you can create test steps automatically, expand the analysis project or create or enhance the Solution Manager project, for example. Afterwards, repeat the analysis on the basis of the expanded project or the project created anew for the updated Solution Manager project with the new test steps. For more information, see Creating Check Steps for Transactions, Reports or Function Modules (RFC) Automatically.
Note
You can only create an analysis if systems and client can be found for at least one logical component. Check the logical components in the source of the analysis project that you base your analysis on, and the check steps assignments in the analysis project.
In this step you determine the system role:
System roles can be either system-wide or individual.
Open the input help for System Roles above the System Selection, and choose an entry to set up a system role for all listed logical components.
To set up a system role for a logical component, open the input help of the System Role and choose an entry.
The systems and clients can be derived from the logical components that were assigned to the underlying analysis project with test steps and the role that a system assumes. Logical components, the systems and clients for a logical component, and the selected system role are displayed in the System Selection area.
The following is displayed for each logical component in the System Selection:
Name of the logical component
System role. You can set up the system roles individually.
System defined by the logical component and the assigned system role.
Client defined by the logical component and the assigned system role.
Status. Displays whether system and client problems can occur for the defined combination of logical components because, for example, a system or a client cannot be found. In the case of a problem, the usage data, which is usually transferred during the processing of the SAP EarlyWatch Alert (EWA), is not available:
Yellow status: The usage data can only be obtained via an RFC connection to the managed system.
Check whether the SAP EarlyWatch Alert (EWA) has been correctly scheduled and conducted, for example.
Red status: The usage data cannot be obtained via an RFC connection or via an SAP EarlyWatch Alert (EWA)
Check, for example:
Whether the SAP Early Watch Alert (EWA) has been correctly scheduled and conducted
Whether the RFC connection has been set up and works
Whether data from the workload statistics is available at all in the administered system
Click the value assignment indicator for more details.
Check steps. Displays the number of check steps to be executed.
Workload, SQL, BAdI, E2E Diagnosis, UPL. If the check boxes Workload, SQL, BAdI, E2E Diagnosis, and UPL are ready for input, statistics data will be provided for the corresponding types for the analysis. In this case the flag is set by default. The analysis includes the data.
Note
The analysis only includes those logical components for which the flag is set.
If the check box is not ready for input, you cannot expect any data for analysis because, for example, the system or client is not defined.
To remove data from the analysis, clear the flag.
Recommendation
SQL check steps can generate a heavy system load. You can therefore improve the performance of the analysis by omitting the SQL step checks from the analysis.
Note
You can only create an analysis if systems and client can be found for at least one logical component. Check the logical components in the source of the analysis project that you base your analysis on, and the check steps assignments in the analysis project.
Limit the time period for which data can be expected from the specified systems, according to your needs. These time periods are complete months.
Note
The planned start of the analysis is relevant for the time period. For an immediate start, the current month is never available for analysis, only completed months.
For a planned start in the future, the month in which the analysis is started is not available for analysis either. However, months that are still in the future at the time of analysis creation might be available.
In the Time Period area, the available time periods are displayed with the following attributes:
Time period is a specific, complete month
Selection. The flag for including the time period is set by default for all available time periods. Clear the flag, to remove a time period from the analysis.
Status displays whether data is available from the specified systems for this time period. The following statuses are displayed with the corresponding status flag for each time period:
Data is available for all systems.
Data is not available for all systems. Click on the status flag for details about systems for which there is no data.
Recommendation
To improve the performance of the analysis, restrict the number of periods to be analyzed as much as possible.
In this step you set the period for the execution of the analysis for a particular managed system and define the maximum amount of resources to be used.
Note
If the table is empty or does not contain all systems assigned in the Select System step, this is due to the unavailability of check steps of certain check step types (such as SQL).
The following information is displayed and entered in the table:
System: Managed system that has at least one check step for a particular type (for example SQL)
Start date: Start date of the analysis
Start time: Start time of the analysis
End date: Date by which the analysis in the respective managed system must be completed. This date must be agreed with the system administrator.
End time: Time at which the analysis in the respective managed system must be completed. This time must be agreed with the system administrator. The analysis is automatically terminated at the specified time.
Recommendation
To keep the system load low, choose a longer time period for the analysis to be carried out. To influence the runtime of an analysis, you have the following options:
Set the maximum number of background processes
Include or exclude the execution of informative check items
Include or exclude the execution of costly SQL check steps
Change the number of periods to be analyzed
Your experience with analyses will be a good guide to how to balance the execution time period and the system load.
Max WP: Maximum number of background work processes in the affected managed system. You must consult system owners concerning this number. The actual number of background processes available for an analysis is determined by the system at the time of the analysis.
Max % WP: Maximum percentage of background work processes to be used in the affected managed system. You must consult system owners concerning this percentage. The actual number of background processes available for an analysis is determined by the system at the time of the analysis.
Note
Operating Mode Switch
If the system uses operating system switching, the number of background work processes changes dynamically. In consultation with the system owners, set the relative number of background work processes (max % WP). He will inform you of the available capacity and the optimal period for executing the analysis. You can then set a high Max WP value.
Recommendation
To complete the analysis as quickly as possible, use the maximum possible system load allowed by your system administrator. You must ensure that the system has enough background processes, or a sufficient proportion of them, at its disposal, for the analysis to be completed within the specified timeframe.
Choose Continue to the next step, or Back to the previous step.
Specify the following settings for the analysis:
Use optimization. Optimization means that, for example, analysis of a check item ends as soon as a result for the check item evaluation is sufficient.
Recommendation
Set the flag to keep the load on the system as low as possible during the analysis.
Include Identifying Check Items. The flag is set by default. You must include these check items to get results for the analysis structure node from the analysis.
Include Informative Check Items. The flag is not set by default.
Recommendation
Informative check items are not required for the evaluation of the structure nodes. Only include informative check items in the analysis if you are sure that you need them.
SQL check steps generate a high system load. It is therefore a good idea to include SQL check steps in informative check items.
Threshold Value. Define a global threshold value for the analysis. This global value overwrites all threshold values where the the value for assigned check steps is set to zero.
System load check steps, for example, dialog, background, or spool. All types are included by default. Select one or more entries from the selection list, to change the default setting.
SQL Check Steps.
If the analysis includes SQL check steps, the Very expensive SQL statements check box is ready for input. The flag is set by default.
If you do not select the checkbox, the system does not execute any SQL check steps that are classified as especially costly.
Recommendation
Lowering the System Load
SQL check steps can generate a heavy system load.
Check whether it is necessary for the analysis to execute SQL statements (for example to check the contents of database tables).
Ensure that the time and resources allocated by your system administrator are sufficient for complete execution of the SQL statements. How precisely you are able to estimate the expected system load will depend on your experience with executing SQL statements.
Descriptive Result Limit: If SQL check steps have to be carried out, you can limit the number of result lines for each SQL check step. This allows you to reduce the data volume and thus also the execution time and system load.
Object Usage – Not in Analysis: Select the object types for which you wish to display usage data, but which is not or not yet part of your analysis. The usage data is transferred during the SAP EarlyWatch Alert (EWA), for example. You can display the data in the analysis results under Object Usage and create new check rules for it. For more information, see Display Object Usage.
Under Unused Customer Objects, select the types of objects that you have created yourself and whose usage you wish to check. The customer objects that are not used are displayed in the analysis results under Object Usage.
Note
If you include unused customer objects in the display, the analysis results on the tab may show more objects than are defined for the object type.
Under Most-Used Objects you set for each object type the number of most-used objects for which you want to display the usage data. The most-used objects include SAP objects as well as customer objects.
Depending on the object type you can set maximum values of 0 (default), 100, 1,000 or 10,000.
Example
For the documentation of your solution, focus on the top 100 most-used transactions.
Note
Including customer objects requires RFC connections to the corresponding systems.
Recommendation
Avoiding Memory Problems
You can avoid memory problems in the following ways:
Reduce the number of object types selected under Unused Customer Objects
Reduce the number of object types selected under Unused Customer Objects
Reduce the number of analyzed periods
The analysis is created.
The summary displays the name of the analysis, the planned start time, the selected systems, and the time periods of the analysis are displayed.