The analysis lists in the Solution Documentation Assistant include detailed information about systems, time periods, and general analysis settings. This detailed information is in the Analysis Projects Overview, the Analyses Overview, and the Analysis Results Overview.
The detailed information tells your the analysis settings, which you can then, for example, adjust for a new analysis.
You have called one of the following views in the Solution Documentation Assistant:
You have selected an analysis in the analyses table.
Or you have called the Analysis Results View and chosen the Settings
tab page.
You can find the detailed information in the Settings
area on the following tab pages:
Systems
shows a table of the logical components and their systems and clients.
Note
All logical components which were used in the underlying analysis project when the analysis was created, are shown.
The following is displayed for each analysis:
Name of the logical component. The name is copied from the underlying Solution Manager project.
System. The system was specified when the analysis was created.
Installation number of the system
Client specified when the analysis was created
RFC destination. The target address of the specified system is required , for example to include customer objects in the analysis by RFC.
Workload Analysis. The flag shows whether, for example, check steps of the transaction or report type are included in the analysis. Function modules (RFC) can be included in the analysis, if the current version of component ST-PI is installed in the managed systems.
SQL analysis. The flag shows whether the analysis includes SQL check steps.
Note
To include SQL check steps, you have to specify the corresponding RFC destination.
BAdI analysis. The flag shows whether the analysis includes check steps for Business Add-Ins (BAdIs).
E2E Diagnosis. The flag indicates whether the analysis includes objects which are covered by the E2E Diagnostics, for example Java Web Dynpro applications and components, Java Web services, Servlets and iViews.
Usage Procedure Logging: Indicates whether the analysis includes usage data (determined by usage procedure logging) on the processing of reports, function modules (RFC), and methods.
Periods
specified when Creating the Analysis. These time periods are complete months for which you can expect analysis data from the specified systems.
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.
Scheduling for managed systems specified when Creating the Analysis. These periods are specified for every managed system that was selected to execute SQL check steps.
Note
In creating an analysis that includes SQL check steps, the start and end time, and the maximum number of work processes to be used (absolutely or as a percentage), are specified.
The analysis takes the currently available resources into account. If the specified period is exceeded for a system, the analysis for this system is terminated so that the resources can be released.
Parameters
: Settings that you made when creating the analysis:
Include Identifying Check Items
Include Informative Check Items
Include high system-load-inducing SQL statements
Get All Customer Objects
Use Optimization
Work process types, for example, dialog, background, or spool.