EWA work flow.

Purpose
The purpose of this article is to provide information about the EWA workflow, since the session creation in
the solution and going through the automatic processes which trigger the data collection and return the
data to the solution manager for the report processing. By knowing this process the system administrator
will be able to easily determine where an issue occurred when the report is not generated.
Overview
Together with other articles referenced below, this article details every step of the EWA generation, giving
hints on how to look for issues and how to resolve them.
Please also check the related information section at the end of this page for any additional information
you may need.
To generate an EWA report, different configurations must be set in the solution manager and also in the
managed(also called satellite) systems. The solution manager does not do the entire process itself. The
matrix below show the steps for the EWA creation for an ABAP system and which system is responsible
for each step. All of them will be detailed afterwards.

Step/System where the step is performed

1. Session creation

Solution Manager

Managed System

2. Creation of the data collection task

3. Data collection

4. Data transfer

5. EWA data processing

Session creation

The session creation consists of scheduling the EWA report in the solution manager system. This can be
done in transaction DSWP in Solution Manager 7.0 and 7.01 or in the work center "System Monitoring".
For that, follow the steps below:
1.

Call transaction SOLMAN_WORKCENTER and select the "System Monitoring" work center.

2.

Click on "setup".

3. Click on "Configuration for a single solution" or "configuration for all solutions", depending on what
you want to do.

4.

If you click on "Configuration for a single solution", select the solution in the popup.

5. In the following screen, you can activate an EWA report and also set other configurations, like
including the system in the EWAfs, send the EWA to SAP, etc. See below:

The screen above can be reached directly for all solutions by calling transaction SOLMAN_EWA_ADMIN.
From transaction DSWP(solution manager 7.01) it can also be called via the "Operations setup". For that,
see the steps below.
1.

Call transaction DSWP and click on "Operations Setup".

2.

Select the "Solution Monitoring" and then the "EarlyWatch Alert".

3.

Click on "Setup EarlyWatch Alert", it will take you to the same screen above.

Session display
Sessions can be displayed in transaction DSWP in Solution Manager 7.01 or in the work centers "SAP
Engagement and Service Delivery" and "System Monitoring" in any solution manager from 7.01
SP18 or higher versions, including 7.1. The work centers transaction is SOLMAN_WORKCENTER.

Requirements
The requirements to be able to create a session are that the managed system is included in a solution in
the solution manager. For that the managed system information must be made available in the SLD so
that it can be read by the solution manager and made available in the SMSY. When the information is in
the SMSY the system can be added into a solution via transactionSOLMAN_DIRECTORY, as described
in KBA 1795238 : "Adding a system to a solution".
If your system is not available in the SMSY you must ensure that you have performed the necessary
steps for that:
1. The managed system itself must report its data to the SLD. This can be done via
transaction RZ70 for an ABAP system and via the Visual Administrator tool in OS level for a non-ABAP
system.
2. From the SLD, the solution manager can read this data. Depending on the solution manager
version, the workflow is different.:
a. In Solution Manager 7.01, the information is read directly from the SLD into the SMSY via job
LANDSCAPE FETCH*.*
b. In Solution Manager 7.1, the information is read from the SLD into the LMDB and from
the LMDB into the SMSY. For a better understanding of this scenario please read
note1592461 : "Troubleshooting LMDB Notification Consumers" and in the Setup Guide Landscape
Management Database (LMDB).
Usually all the jobs above are scheduled via the System Preparation and Basic configuration in the
solution manager, in transaction SOLMAN_SETUP.
3. Once the data is in the SMSY, it can be added into a solution as per KBA 1795238 : "Adding a
system to a solution".
4. When the system is added into the solution an EWA is automatically created for it. You can control
the activation of EWAs per solution via transaction SOLMAN_EWA_ADMIN. Also check the availability of
EWA for each product in note 1257308.
Once the EWA task is created in the solution manager, it remains there as an empty bottle, waiting to
filled with the data for processing the report. Until the session is filled with data the Solution Manager
won't do anything with the session.
Creation of the Data Collection Task
As stated in the previous section, it is not the solution manager that makes the data collection happen for
the EWA, the solution manager only creates the session and wait.

It is the managed system which is responsible to check in the solution manager, via an RFC connection, if
there is any EWA task scheduled to run and then create a data collection task in its ownSDCCN. This is
done in the SDCCN of the managed system via a task named "Refresh Sessions". The requirements to
make this happen are:
1.

The SDCCN must be activated in the managed system.

2. The "back RFC", from the managed system to the solution manager, must be created and assigned
as 'Master' RFC in the SDCCN of the managed system.
You can activate the SDCCN in the managed system via the SDCCN itself. For that, access the
transaction and in the top menu select Utilities(M) -> Activate. When the SDCCN is activated the task
processor must be running and the "Maintenance Package" and "Service Preparation Check" must be
running daily and weekly, respectively. For more details see note 763561.
In relation to the "back RFC", it is created via the solution manager itself.
In solution manager 7.01 it is created in transaction SMSY by using the wizard.
In solution manager 7.1 it is created during the managed system configuration in
transaction SOLMAN_SETUP. During this process, the SDCCN can also be activated, remotely.
The creation of RFCs consists of creating 4 RFCs in the solution manager, pointing to the managed
system, and one in the managed system, pointing to the solution manager:
Having al the requirements performed, a simple execution of the "Refresh sessions" task in
the SDCCN of the managed system using the "back RFC" will create the EWA data collection task in
theSDCCN. Please notice that it is not necessary to have a periodic "Refresh sessions" task because this
task is executed daily when the maintenance package task runs.
If the data collection task is not created automatically, please troubleshoot according to KBA 1769513:
"EWA not generated - red flag is shown in the status".
Data Collection
The data collection runs usually on Monday at 4AM. The data collection task is automatically started if the
task processor is running.
This task executes a set of function modules responsible for collecting the data for the different sections
of the EWA report. Once this is done, a package is build, called SDCCN download, with the raw data that
will be used for the EWA session. This package can be checked in transaction SDCCN under tab "To Do",
by clicking the truck icon in the already executed data collection task.

The data collection depends on updated modules for data collection and also on service definitions up-todate.
The data collection modules impact directly in the quality of the data collected for the session, these
modules are updated by component ST-PI and ST-A/PI. There are also further configurations to be done,
all of them outlined by report RTCCTOOL, which can be run in transaction SE38.
In relation to the service definitions, they're related to the service which can be carried out in
the SDCCN of the managed system. Service definitions ARE NOT the service content. Please read our
wiki which provides more information about both: Information about service content and service definitions.
Data Transfer
The data transfer is automatically done at the end of the data collection task in the SDCCN. It uses the
"back RFC" for that purpose, if any error occurs, please check the logs of the data collection task. Errors
will be usually related to invalid users or RFC connection issues.
EWA Data Processing
Once the managed system transfers the data to the solution manager, the icon in the session will change
to a bottle, meaning that the session is ready to be processed.
The session is usually processed at 6AM on Mondays, by the job SM:EXEC SERVICES. The processing
of these sessions is done by many different reports, which are responsible for different sections or
different data to be processed. These reports are delivered via component ST-SER in the solution
manager or alternatively via service content update, which can be performed in
transaction AGS_UPDATE. Service content IS NOT the same as service definitions. Please read our wiki
which provides more information about both: Information about service content and service definitions.
EWA work flow.
http://wiki.scn.sap.com/wiki/display/SM/The+EWA+workflow+-+a+closer+look

Purpose
The purpose of this article is to provide information about the EWA workflow, since the session creation in
the solution and going through the automatic processes which trigger the data collection and return the
data to the solution manager for the report processing. By knowing this process the system administrator
will be able to easily determine where an issue occurred when the report is not generated.
Overview
Together with other articles referenced below, this article details every step of the EWA generation, giving
hints on how to look for issues and how to resolve them.

Please also check the related information section at the end of this page for any additional information
you may need.
To generate an EWA report, different configurations must be set in the solution manager and also in the
managed(also called satellite) systems. The solution manager does not do the entire process itself. The
matrix below show the steps for the EWA creation for an ABAP system and which system is responsible
for each step. All of them will be detailed afterwards.

Step/System where the step is performed

1. Session creation

Solution Manager

Managed System

2. Creation of the data collection task

3. Data collection

4. Data transfer

5. EWA data processing

Session creation
The session creation consists of scheduling the EWA report in the solution manager system. This can be
done in transaction DSWP in Solution Manager 7.0 and 7.01 or in the work center "System Monitoring".
For that, follow the steps below:
1.

Call transaction SOLMAN_WORKCENTER and select the "System Monitoring" work center.

2.

Click on "setup".

3. Click on "Configuration for a single solution" or "configuration for all solutions", depending on what
you want to do.

4.

If you click on "Configuration for a single solution", select the solution in the popup.

5. In the following screen, you can activate an EWA report and also set other configurations, like
including the system in the EWAfs, send the EWA to SAP, etc. See below:

The screen above can be reached directly for all solutions by calling transaction SOLMAN_EWA_ADMIN.
From transaction DSWP(solution manager 7.01) it can also be called via the "Operations setup". For that,
see the steps below.
1.

Call transaction DSWP and click on "Operations Setup".

2.

Select the "Solution Monitoring" and then the "EarlyWatch Alert".

3.

Click on "Setup EarlyWatch Alert", it will take you to the same screen above.

Session display
Sessions can be displayed in transaction DSWP in Solution Manager 7.01 or in the work centers "SAP
Engagement and Service Delivery" and "System Monitoring" in any solution manager from 7.01
SP18 or higher versions, including 7.1. The work centers transaction is SOLMAN_WORKCENTER.
Requirements
The requirements to be able to create a session are that the managed system is included in a solution in
the solution manager. For that the managed system information must be made available in the SLD so
that it can be read by the solution manager and made available in the SMSY. When the information is in
the SMSY the system can be added into a solution via transactionSOLMAN_DIRECTORY, as described
in KBA 1795238 : "Adding a system to a solution".
If your system is not available in the SMSY you must ensure that you have performed the necessary
steps for that:
1. The managed system itself must report its data to the SLD. This can be done via
transaction RZ70 for an ABAP system and via the Visual Administrator tool in OS level for a non-ABAP
system.

2. From the SLD, the solution manager can read this data. Depending on the solution manager
version, the workflow is different.:
a. In Solution Manager 7.01, the information is read directly from the SLD into the SMSY via job
LANDSCAPE FETCH*.*
b. In Solution Manager 7.1, the information is read from the SLD into the LMDB and from
the LMDB into the SMSY. For a better understanding of this scenario please read
note1592461 : "Troubleshooting LMDB Notification Consumers" and in the Setup Guide Landscape
Management Database (LMDB).
Usually all the jobs above are scheduled via the System Preparation and Basic configuration in the
solution manager, in transaction SOLMAN_SETUP.
3. Once the data is in the SMSY, it can be added into a solution as per KBA 1795238 : "Adding a
system to a solution".
4. When the system is added into the solution an EWA is automatically created for it. You can control
the activation of EWAs per solution via transaction SOLMAN_EWA_ADMIN. Also check the availability of
EWA for each product in note 1257308.
Once the EWA task is created in the solution manager, it remains there as an empty bottle, waiting to
filled with the data for processing the report. Until the session is filled with data the Solution Manager
won't do anything with the session.
Creation of the Data Collection Task
As stated in the previous section, it is not the solution manager that makes the data collection happen for
the EWA, the solution manager only creates the session and wait.
It is the managed system which is responsible to check in the solution manager, via an RFC connection, if
there is any EWA task scheduled to run and then create a data collection task in its ownSDCCN. This is
done in the SDCCN of the managed system via a task named "Refresh Sessions". The requirements to
make this happen are:
1.

The SDCCN must be activated in the managed system.

2. The "back RFC", from the managed system to the solution manager, must be created and assigned
as 'Master' RFC in the SDCCN of the managed system.
You can activate the SDCCN in the managed system via the SDCCN itself. For that, access the
transaction and in the top menu select Utilities(M) -> Activate. When the SDCCN is activated the task
processor must be running and the "Maintenance Package" and "Service Preparation Check" must be
running daily and weekly, respectively. For more details see note 763561.

In relation to the "back RFC", it is created via the solution manager itself.
In solution manager 7.01 it is created in transaction SMSY by using the wizard.
In solution manager 7.1 it is created during the managed system configuration in
transaction SOLMAN_SETUP. During this process, the SDCCN can also be activated, remotely.
The creation of RFCs consists of creating 4 RFCs in the solution manager, pointing to the managed
system, and one in the managed system, pointing to the solution manager:
Having al the requirements performed, a simple execution of the "Refresh sessions" task in
the SDCCN of the managed system using the "back RFC" will create the EWA data collection task in
theSDCCN. Please notice that it is not necessary to have a periodic "Refresh sessions" task because this
task is executed daily when the maintenance package task runs.
If the data collection task is not created automatically, please troubleshoot according to KBA 1769513:
"EWA not generated - red flag is shown in the status".
Data Collection
The data collection runs usually on Monday at 4AM. The data collection task is automatically started if the
task processor is running.
This task executes a set of function modules responsible for collecting the data for the different sections
of the EWA report. Once this is done, a package is build, called SDCCN download, with the raw data that
will be used for the EWA session. This package can be checked in transaction SDCCN under tab "To Do",
by clicking the truck icon in the already executed data collection task.
The data collection depends on updated modules for data collection and also on service definitions up-todate.
The data collection modules impact directly in the quality of the data collected for the session, these
modules are updated by component ST-PI and ST-A/PI. There are also further configurations to be done,
all of them outlined by report RTCCTOOL, which can be run in transaction SE38.
In relation to the service definitions, they're related to the service which can be carried out in
the SDCCN of the managed system. Service definitions ARE NOT the service content. Please read our
wiki which provides more information about both: Information about service content and service definitions.
Data Transfer
The data transfer is automatically done at the end of the data collection task in the SDCCN. It uses the
"back RFC" for that purpose, if any error occurs, please check the logs of the data collection task. Errors
will be usually related to invalid users or RFC connection issues.

EWA Data Processing

Once the managed system transfers the data to the solution manager, the icon in the session will change
to a bottle, meaning that the session is ready to be processed.
The session is usually processed at 6AM on Mondays, by the job SM:EXEC SERVICES. The processing
of these sessions is done by many different reports, which are responsible for different sections or
different data to be processed. These reports are delivered via component ST-SER in the solution
manager or alternatively via service content update, which can be performed in
transaction AGS_UPDATE. Service content IS NOT the same as service definitions. Please read our wiki
which provides more information about both: Information about service content and service definitions.