Show TOC

Process documentationUsing SAP EarlyWatch Alert Locate this document in the navigation structure


This process identifies potential problems early, avoids bottlenecks, and monitors the performance of your ABAP and JAVA systems and your most important business processes, regularly, automatically and effectively. The ABAP data collection infrastructure is the Service Data Control Center, and the JAVA data collection infrastructure is the root-cause analysis data which is read from the SAP Solution Manager Business Intelligence (BI). The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.

To be able to use it, you have:

  • entered the non-ABAP systems in the transaction Solution Manager System Landscape (SMSY)

  • RFC connections between:

    • Your managed systems and the SAP Solution Manager system

    • SAP Solution Manager and the SAP Service Marketplace

    • the SAP Solution Manager system and Solution Manager Diagnostics

      See: SAP Solution Manager customizing

  • checked the availability of the tools required for the SAP service sessions (add-on ST-A/PI), with the report RTCCTOOL

  • activated Alert Monitoring for all SAP managed systems and the central SAP Solution Manager of your solution, and set-up the Service Data Control Center (SDCCN) in the managed systems

  • set-up your systems in a solution landscape in the SAP Solution Manager

  • set-up Solution Manager Diagnostics for the root-cause analysis


SAP EarlyWatch Alert for ABAP systems

  1. Configure the SAP EarlyWatch Alert in SAP Solution Manager scheduling. You have:

    • scheduled the service sessions of your solution in the SAP Solution Manager solution directory.

      Note Note

      The Default value is Mondays. You should retain this value.

      End of the note.
    • activated or deactivated SAP EarlyWatch Alert data download from the Service Data Control Center, for the systems in your solution.

  2. You have activated SAP EarlyWatch Alert monitoring for the systems in your solution.

  3. Data collectors in the managed systems aggregate analysis-relevant system and performance data, weekly.

  4. The system forwards this data to the SAP Solution Manager by automatic download via the Service Data Control Center (SDCCN).

  5. The job SM:EXEC SERVICES triggers the processing of the data in a session.

  6. The procedure continues according to the following rules which SAP put in the system:

  • Red: Very critical/error.

    1. Analyze the report. The SAP Solution Manager system sends the data to SAP.

    2. The SAP Support checks the problems and contacts you, if required, to discuss possible activities.

    3. If you regard the alert as critical, discuss possible reactions with SAP.

    4. Take the agreed action.

  • Yellow: Critical/warning. Analyze the report.

  • Gray: System status cannot be determined. Check why the system status could not be determined.

  • Green: No errors.

The system sends a session to SAP, initially and monthly, using the SAP Service Marketplace, independently of the analysis of the weekly SAP EarlyWatch Alert reports.

SAP EarlyWatch Alert for non-ABAP systems

Solution Manager Diagnostics is set-up for the root-cause analysis The Solution Manager Diagnostics collects data for all monitored systems, centrally. The SAP EarlyWatch Alert reads this data directly from the SAP Solution Manager BI and processes it. The ABAP stack is used to generate the SAP EarlyWatch reports.