Sap Earlywatch Check



SAP EarlyWatch Alert is an automatic service analyzing the essential administrative areas of an SAP system. Alerts indicate critical situations and give solutions to improve performance and stability. SAP EarlyWatch Alert is most effective when activated for all SAP components in your solution. Standard users, including SAP. and DDIC, have default passwords. Run report RSUSR003 to check the usage of default passwords by standard users. Ensure that: –User SAP. exists in all clients –Users SAP., DDIC, SAPCPIC, and EARLYWATCH have non-default passwords in all clients –Profile parameter login/noautomaticusersapstar is set to 1. In order to activate the SAP EarlyWatch Alert configuration, in your SAP Solution Manager System, execute transaction SOLMANWORKCENTER and navigate to the System Monitoring tab. Click the Setup Link then Configure for a Single Solution and click Active. Check transaction SDCCN, the SAP EarlyWatch Alert task should now be scheduled.

Skip to end of metadataGo to start of metadata

Overview


SAP Solution Manager Usage

The number of managed systems, diagnostics systems, implementation projects, and solutions indicates the scale of usage of this SAP Solution Manager.

The number of connected managed systems is derived from the available systems in transaction SOLMAN_SETUP, whereas the number of diagnostics systems is the number of systems for which Solution Manager Diagnostics is active.

The projects can be found in transaction SOLAR01, whereas the solutions can be found in the Solution Manager Administration work center.

Furthermore, the total number of EWA sessions in the system is evaluated.

Sap Earlywatch Check Card

The rating is set to GREENautomatically.

Sap earlywatch check card


The number of EWA sessions is evaluated from table DSVASSESSIONHEAD, where these sessions are marked with a particular status as shown in the following table. In general, you want the system to keep this data for a longer time. Since some of this data may be quite extensive (service sessions 1-20 MB, documents 1-10 MB), the database of the SAP Solution Manager system might increase remarkably in size depending on how many systems have been connected.
For details about archiving service sessions in SAP Solution Manager, see SAP Note 2075483 - Archiving in Solution Manager (operation).

Application-Specific Usage

The tables in this section provide an overview as to whether and to what extent some selected scenarios in SAP Solution Manager are used. For an overview of all the supported processes, check the SAP Solution Manager Processes in the SAP Support Portal. Icone rocketdock.

The rating for each is set to GREEN automatically.

Collaboration

The collaboration scenario includes service delivery, problem management (with issues, top issues, and tasks), and expertise on demand (EoD). The number of service delivery objects counts delivered standard remote services such as SAP EarlyWatch Check, SAP GoingLive Check, SAP GoingLive Functional Upgrade Check, and SAP OS/DB Migration Check. The 'Last Created' column indicates whether the functionality is still in use. For more information about the collaboration platform, see SAP Note 914722.

IT Service Management

This check shows how many Business Partners and transaction types exist in the system for the IT Service Management functionality. For the different transaction types, the entries with the number of objects show how many messages exist in the system and how many of them were created in the EWA time frame.

Change Request Management

Sap Earlywatch Check Status

In standard Change Request Management, SAP delivers seven messages types; all other message types are created by the customer. The number of change request transactions (created in the last 10 days) indicates whether and to what extent the scenario is used.


Quality Gate Management

With this Quality Gate Management check, you can review whether, and to what extent the Quality Gate Management scenario is used within your SAP Solution Manager. The number of gate switches, the number of created and released transport requests under the control of Quality Gate Management, and the number of SAP Solution Manager projects used to run Quality Gate Management indicate how, and how much this scenario is used.


Implementation Scenario

The number of defined business scenarios and defined business processes and steps indicate whether and to what extent the implementation scenario is used. It includes all business scenarios and business processes that have been defined in the different projects and can be checked in transaction SOLAR01.

Test Management

The test management scenario is part of the implementation scenario. A number larger than zero indicates whether and to what extent the test management functionality is used. Hoyle casino 2003 free download. The functionality can be accessed using the Test Management work center.

Business Process Monitoring

For the Business Process Monitoring (BPM) scenario, the number of solutions with BPM, the number of processes with BPM, and the number of monitoring objects in BPM is shown. The functionality can be accessed using the Business Process Operations work center.

Job Scheduling Management

This check shows how many job requests and how many job documents have been created in SAP Solution Manager and how many of them were created in the EWA time frame.

SAP BASISCard

SAP EarlyWatch Alerts is a very useful report that measures or reactively identify problems or potential problems with your SAP production systems. These weekly reports can be easily understood and even by a non-technical person and are very useful to a SAP BASIS Administrator. Recommendations are also provided by SAP to tune your SAP system for better performance and security.

Your SAP Production system (the managed system) is connected to your SAP Solution Manager (the managing system) through the ABAP Remote Function Call (RFC).

The SAP EarlyWatch Alerts requires the following configuration steps to be performed in order for the report to be completely generated.

Step-by-Step Configuration Procedure

(Please note that the steps below are applicable to SAP Solution Manager 7.1)

Sap Cqc Earlywatch Check

  1. Your managed system should have the latest ST-PI and ST-A/PI packages installed. (Use transaction SPAM and SAINT to update these)
  2. Ensure that your SAPOSS RFC connection is properly connected to SAP. (Your SAProuter should be properly installed, configured to connect to SAP OSS, and the certificate is still valid)
  3. Run ABAP report RTCCTOOL once the above has been updated or installed. (Use transaction SE38) and comply with all corrective measures. Only proceed to the next step if all alerts are green. Make sure you re-run RTCCTOOL to make sure that there are no errors. This step of the SAP EarlyWatch Alert configuration is very important for complete data collection.
  4. Add the managed system to the SAP Landscape Directory (SLD) using RZ70. If your SLD is your SAP Solution Manager, then add the IP address of the SAP Solution Manager to the Gateway Host field and ‘sapgw<instance no.>’ in the Gateway Service field.
  5. Wait for about 10 minutes for the data to be collected. Check if the SID is available in the SAP Landscape Management Database (LMDB) in your SAP Solution Manager.
  6. Make sure that the correct product system has been assigned once the system is available in LMDB.
  7. Add the system to a Logical Landscape and Solution.
  8. Log-in to the managed system, enter transaction SDCCN and navigate to Goto -> Settings -> Task Specific. In the resulted screen, select the RFC destination and enter the SAP Solution Manager RFC from the managed system and set SAP Solution Manager RFC as the master system.
  9. Next login to your SAP Solution Manager and enter transaction SMSY and navigate to Environment -> Solution Manager Operations -> Administration SDCCN. This will add the new service data control center to the SAP Solution Manager, Click on add system to add the new SDCCN to the SAP Solution Manager. Select the managed system and client from the resulting screen and confirm.
  10. In order to activate the SAP EarlyWatch Alert configuration, in your SAP Solution Manager System, execute transaction SOLMAN_WORKCENTER and navigate to the System Monitoring tab.
  11. Click the Setup Link then Configure for a Single Solution and click Active.
  12. Check transaction SDCCN, the SAP EarlyWatch Alert task should now be scheduled.

By default you will be receiving your SAP EarlyWatch Alert reports every Monday. Automated email of your SAP EarlyWatch Alert may also be configured but I’ll feature it in a separate post. You may now run an ad-hoc SAP EarlyWatch report or wait for the next Monday.

References:

  1. Simple About Basis [http://simplesapbasis.blogspot.com/2012/10/71-scheduling-and-viewing-earlywatch.html]
  2. Durga Prasad Blog [https://sapbasisdurgaprasad.blogspot.com/2011/06/how-to-configure-early-watch-alert.html]
  3. SAP Support Portal [https://support.sap.com/support-programs-services/services/earlywatch.html]

Have any questions or suggestions? Feel free to message me in the form below.

Related