note 1040343 - early watch alert (ewa) for solutions

09.05.2011 of 5

SAP Note 1040343 - EarlyWatch Alert (EWA) for Solutions

Note Language: English Version: 11 Validity: Valid Since 28.04.2010

Summary

SymptomActivating EarlyWatch Alert (EWA) for Solutions in SAP Solution Manager

Other termsEWA, monitoring, service

Reason and PrerequisitesYou want to activate EarlyWatch Alert for Solutions in your SAP SolutionManager to generate cyclic reports about the status of selected solutionlandscapes.This note describes the scheduling of EarlyWatch Alert for Solutions andcontains information about its usage.

Solution

Important note:Release ST 400 Support Package 12 (FP04) provided a maintenance interfacethat already supports scheduling of EarlyWatch Alerts for Solutions.Since the report contents are available only as of ST-SER Release700_2008_1, the processing of this service level for earlier ST-SERreleases does not currently return any results.

For this reason, the EarlyWatch Alert (EWA) for Solutions should beactivated as of ST-SER Release 700_2008_1 only.

Supported productsThe BI-based part of EWA for Solutions is only available for products andproduct versions that are supported by the BI of the Solution ManagerDiagnostics (SMD).The following is a list of supported product versions for each SolutionManager software version:

As of ST-SER 700_2008_1 SP00 and ST 400 SP15

- SAP ECC 5.0

- SAP ECC 6.0

- SAP NetWeaver 04

- SAP NetWeaver 7.0

- SAP NetWeaver 7.1

- SAP CRM 4.0

09.05.2011 of 5


- SAP CRM 5.0

- SAP CRM 5.2

- SAP CRM 2007

- SAP BI ACCELERATOR 2004S

- SAP SOLUTION MANAGER 4.0

- SAP A1S 1.0

- DUET 1.0 ON SAP NW 04

As of ST-SER 700_2008_2 SP00 and ST 400 SP18

- SAP ECC 6.0

- SAP ERP 6.0

- SAP NetWeaver 04

- SAP NetWeaver 7.0

- SAP NetWeaver PI 7.1

- SAP NetWeaver CE 7.1

- SAP CRM 4.0

- SAP CRM 5.0

- SAP CRM 5.1

- SAP CRM 2007

- SAP CRM 7.0

- SAP BI ACCELERATOR 7.0

- SAP SOLUTION MANAGER 7.0

- SAP A1S 1.0

09.05.2011 of 5


- DUET 1.0 ON SAP NW 04

- DUET 1.5 ON SAP NW 7.0

- SAP SCM 7.0

- SAP SRM 7.0

As of ST-SER 700_2008_2 SP05 and ST 400 SP18All previously specified product versions and also:

- SAP ERP 6.0 up to EHP 6

- SAP NetWeaver 7.0 up to EHP 3

- SAP NETWEAVER AS ABAP 7.1

- SAP NETWEAVER AS ABAP 7.2

- SAP NETWEAVER AS JAVA 7.1

- SAP NETWEAVER AS JAVA 7.2

- SAP NETWEAVER CE 7.1

- SAP NETWEAVER CE 7.2

- EHP1 FOR SAP CRM 7.0

- EHP2 FOR SAP CRM 7.0

- SAP SOLUTION MANAGER 7.0 EHP 1

- SAP SOLUTION MANAGER 7.0 EHP 2

- EHP1 FOR SAP SCM 7.0

- EHP2 FOR SAP SCM 7.0

- EHP1 FOR SAP SRM 7.0

- EHP2 FOR SAP SRM 7.0

If the reporting uses an SAP system in EWA for Solutions which does not useany of the product versions listed above, the sections "Workload andPerformance Analysis", "Exception Analysis" and "Change Analysis" remainempty.

09.05.2011 of 5


Scheduling EWA for Solutionsa) Solution-specific administrationCall transaction DSWP or SOLUTION_MANAGER and choose the required solutionlandscape. Activate the operations setup mode and choose SolutionMonitoring -> EarlyWatch Alert.

b) Cross-solution administrationCall transaction SOLMAN_EWA_ADMIN to go directly to the maintenance viewfor EWA and EWA for Solutions.

By setting the indicator for "Active" for the required solution landscape,EWA for Solutions is scheduled at solution level. By choosing "AutomationWeekday", you determine the day, on which the service is processed in thebackground once a week.

During the activation, the system includes all systems of the solution thatare classified as productive in the report. You can modify this selectionat any time and therefore delete or add individual systems or softwarecomponents.

Practical hintsa) SchedulingEWA for Solutions is based in part on EWA and, like EWA, provides cyclicalreports on a weekly basis.Therefore, you must ensure that the scheduled weekday for generating EWAfor Solutions is not before the scheduled weekday for the last singlesystem EWA of the solution.

b) Display of business processesEWA for Solutions works solution-based. If the selection of systems differsfrom the proposed default selection, you should ensure that all systemsrelevant for the business process are taken into account in the report.This is based on the assumption that the solution landscape was previouslycreated according to business processes, and that the core businessprocesses were maintained in Solution Manager. If the focus in the designof the solution landscapes is on technical or organizational aspects, thepractical value of EWA for Solutions decreases in some areas of the report.

To increase the value of a report, we recommend that you maintain allrelevant core business processes of a solution first in Solution Manager.If this information is available when you generate a report, EWA forSolutions provides a specific evaluation of the performance of these coreprocesses. Otherwise, only the most frequently used transactions areevaluated.

Keep in mind that the list of business process steps or list oftransactions assigned to process steps in the report may be longer thanrequired.In particular, this is the case if all of the process steps entered in theproject planning phase were transferred to the Solution Directory.If you want to display the report unit for the business processes clearly,we recommend that you manually delete all business process steps andtransactions from the Solution Directory that are only relevant in theproject planning phase but are not in use.

09.05.2011 of 5


Header Data

Release Status: Released for CustomerReleased on: 28.04.2010 11:32:16Master Language: GermanPriority: Recommendations/additional infoCategory: FAQPrimary Component: SV-SMG-SER SAP Support Services

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

ST-SER 620 620_2006_2

620_2006_2

X

ST-SER 700 700_2006_2

700_2008_1

X

ST-SER 701 701_2008_2

701_2008_2

Support Packages

Support Packages Release Package Name

ST-SER 701_2008_2 SAPKITLOQ5

Related Notes

Number Short Text

1161294 Name chg, SAP Solution Manager 4.0 to Solution Manager 7.0

1074428 EWA for Solutions: ABAP runtime error MEMORY_ID_TOO_LONG

note 1040343 - early watch alert (ewa) for solutions

Documents