Skip to end of metadata
Go to start of metadata
  • Purpose

    •  Workmode Management is used to manage systems from solution manager such as business or technical outage situations. In order to use the functionality, managed system configurations and specific solution manager configurations must be complete. This page will contain further information regarding configurations and functionality as well as common current issues.

  • Overview

    • Workmode management
      • Allows to schedule and maintain Work Modes (e.g. Down Time, Peak Business Hour) for technical systems, databases and hosts.
      • Long term planning of recurring work modes as well as ad-hoc definition of single work modes.
      • Automatic notification of users about upcoming system downtimes.
      • Central execution of system downtimes.
      • Downtime Reporting and Work Modes planning based on the data from CCMS or BI reporting.
      • Certain alerts can be switched on or off for different work modes.


    • Service Availability Management (SAM)
      • SAM reports SLA-relevant downtimes of managed objects based on data which is adjusted by system administrators to match the end user experience.
      • This can be the single source of truth for Service Level Agreement (SLA) reporting of system downtimes.


    • IT Calendar
      • Provides a calendar-based overview of the planned Work Modes, and allows to further schedule and maintain them.
      •  Display of planned work modes for one or several technical systems in the same calendar view.
      • The display of both inactive and active work modes in the IT calendar supports the work mode planning and scheduling process.


    • Downtime Reporting
      • Compare actual versus planned down times.
      • Check which proportion of planned downtimes was really used.
      • Check whether downtimes occurred outside the planning windows or within.


    • Alert Inbox
      • It is the central access point for analyzing and solving Technical Monitoring problems in an SAP Solution Manager landscape.
      • Notification management will create an unavailability alert for unplanned outages.


  • Supported Managed Systems


    • ABAP
    • Netweaver JAVA
    • BOE


  • Prerequisite

    • SAP Solution Manager 7.1 with the latest support pack.

    • Managed System Setup.


  • Configuration

    • Solman setup
    1. System Preparation

    2. Basic Configuration

    3. Managed System Configuration must be complete, for more information regarding managed system configuration, please refer here.

      Image1: Sample setup of completed Managed System Configuration. This configuration is essential for reliable monitoring.

      • Technical Monitoring Configuration for System Monitoring must be compete.
        Image 2 Ensure 'System Monitoring' is selected within Technical Monitoring tab.

        Image 3 Ensure all ratings are green in 'step 5 Define Scope' to validate complete Technical Monitoring configuration.

      • Activate the third party component from Step 2.3 default setting and from Step 4 Template Maintenance. For more information, refer to SAP KBA 2125482. In the KBA, please pay attention to further changes required in template settings.

        Image 4: Please confirm the third party connection activation after your change.

      • Technical Scenario can be created in Step 5. For more information regarding use of technical scenario, refer to SAP KBA 2014587.

        Image 5: 'Create Scenario' can be used at any time to group multiple systems.

    4. Service Availability Management is mandatory only when SAM functionality is to be used.


  • FAQ 

    1. Do I have to create a separate workmode for database?
      • Yes you have to create separate workmode for each database. There is no way for database to inherit workmodes due to MCOD (Multiple Components in One Database) scenarios.

    2. Can I create Workmode for different systems in one step?
      • Yes you can create a technical scenario to group different systems. This way, one workmode created on technical scenario level will inherit to underlying systems. However, the workmodes will not inherit to database or hosts. For more information refer to SAP Note 2123252.


  • Current Issues

    1. Synchronization issue between Work Mode Management and IT Calendar.
      Possible Symptoms for this issues are:
      •  Recurrent workmodes are not displayed correctly in IT calendar, while they are in WorkMode Management or vice versa. Either only the first of the recurrent workmode is maintained or a random few.
      • Workmodes in either IT calendar or WorkMode Management do not display inherited workmode.
      • Synchronization is successful in English environment but not in any other languages such as German.
      • Unable to open existing workmodes from either or from both WorkMode Management and IT Calendar.


  • No labels