Focused Run for SAP Solution Manager provides Guided Procedures to support standardized execution of regular tasks. Guided procedures may include automated or manual activities.
For many different tasks SAP provides activity plug-ins for re-use. These plug-ins help you to develop your own guided procedures that include tailored, automatic activities. These activities can be triggered manually or executed entirely in the background as part of an alert reaction, service level reporting, health check guided or regular operational task procedure.
For detailed information about Guided Procedure Activities please refer to
This document helps you with the following aspects of Guided Procedure Authoring:
• Automatic execution of the CSA policy validation
• Distribution of validation results via mail
• Distributed result can be configured regarding 'Validation result only' (with link to CSA), 'Only Non-Compliant items' or 'All compliance items'
The configuration of a Guided Procedure is either started by the tile ‘System Management – Guided Procedure Configuration' (up to FRUN 2.00 SP01) or within the tile ‘System Management – Guided Procedures' (as of FRUN 2.00 SP02):
Figure: Guided Procedure for Advanced System Management
Select application area ‘Guided Procedure for Advanced System Management', click on the ‘Add' button to create a new GP and enter a name and description:
Figure: Create New Guided Procedure
For release levels below FRUN 2.00 SP02 use button ‘Create' -> ‘New' of tile ‘System Management – Guided Procedure Configuration'.
If the Guided Procedure is only intended for local use in the system, then use $TMP as package name. Otherwise, choose a custom package to allow transporting.
Switch to edit mode and enter a step name, description and a documentation:
Figure: Edit Guided Procedure
At ‘Step Content' click on button ‘New' at tabstrip ‘Automatic Activities':
Figure: Add a step content
Select the CSA Plugin and enter the technical policy name:
Figure: Select CSA PlugIn
If enabled, the final output will contain the corresponding check item results in plain text. Depending on the content of the selected policy it may happen that sensitive configuration data is disclosed to users who shall not have the authorization to see this data.
Note: In CSA, some config stores are protected with additional authorization checks. When running a policy from a Guided Procedure, the validation checks on these config stores are executed by the technical user GP background user that is allowed to read all stores.
Recommendation: Only enable ‘Show Details' if you are sure that the policy does not distribute security relevant information to the recipients. In general it is recommended to disable this feature. In this case the output does contain a link for a direct execution of the CSA validation displaying the policy results. This includes an authorization check of the end user.
The technical name of the CSA policy.
Display Only Non-Compliant Items:
The output will only display non-compliant items. This reduces the output in case the policy does contain many check items.
Select the scope of the GP execution, either ‘Technical System' or ‘Database'. Here, the scope must match to the check items of the policy.
Confirm the step.
A GP configuration requires for technical reasons a final step:
Figure: Add a final step
Click on button ‚Report Configuration' and disable the options as shown.
Figure: Report Configuration
Finally, save and activate the GP using the corresponding buttons:
Figure: Save and activate
Select the Guided Procedure and click on run:
Figure: Running a Guided Procedure
In older releases use button ‘Execute' at tile ‘System Management – Guided Procedure Configuration'
Create a scope using the ‘Add' button:
Figure: Create new execution instance
Execute the GP:
Figure: Execute the Guided Procedure
Click on button ‘Add' at the Guided Procedure Planning:
Figure: Guided Procedure Planning
In older releases use button ‘Create Plan' at tile ‘System Management – Guided Procedure Configuration'
Choose the GP and enter a plan name:
Figure: Enter a plan name
Define the scope of the GP planning (here: All ABAP systems):
Figure: Define scope of GP planning
Define the schedule:
Figure: GP Planning schedule
In case the result is to be forwarded to a recipient list this must be maintained in the GP environment. In general, create a recipient list with report receivers and create a recipient list with “admin receivers” who will receive notification if GP job fails.
For details, please refer to the GP documentation.
Figure: Planning notification