EWA Creation Problem

[Former Member]

Hi gurus,

I tried to make EWA creation for my SAP instance with no avail.

I've done every step required, like setting RFC connection between solman and client, setting logical component and system landscape.

Test connection was ok for RFC from and into solman.

My problem is when i logged in into client and run tcode 'SDCCN', and create task 'refresh session', the task always 'done' with this message (please note the underline message):

13.02.2009 13:19:59 Refresh of session overview completed from destination SM_SOMCLNT200_BACK /BDL/SAPLBDL11 0 SAPSUPPORT

13.02.2009 13:19:59 > Sessions are up to date /BDL/SAPLBDL11 0 SAPSUPPORT

13.02.2009 13:19:53 Refresh of session overview started from destination SM_SOMCLNT200_BACK /BDL/SAPLBDL11 0 SAPSUPPORT

no EWA's created after that..

I have several clients i want to connect to solman, some has been successfull for EWA generation, but some failed with very same message mentioned above.

This is the message for successfull "Refresh Session" task for several clients (please note also the message I underline):

09.02.2009 17:54:54 Refresh of session overview completed from destination Solman /BDL/SAPLBDL11 0 SAPSUPPORT

09.02.2009 17:54:54 > New session 2000000000999 0000000405 with date 20090216 scheduled for 20090216040000* /BDL/SAPLBDL11 0 SAPSUPPORT

09.02.2009 17:54:42 Refresh of session overview started from destination Solman /BDL/SAPLBDL11 0 SAPSUPPORT

I've executed some steps and still no success:

- Execute notes that tells me to replace service definitions

- Run RTCCTOOL and fix any given issues, like upgrading ST A/PI and ST/PI

- Upgrade kernel

- Apply support packages

Are there suggestions for my problem, gurus?

Edited by: Antonius Erwin Handoko on Feb 13, 2009 7:37 AM

Edited by: Antonius Erwin Handoko on Feb 13, 2009 7:37 AM

Edited by: Antonius Erwin Handoko on Feb 13, 2009 7:38 AM

[Former Member]

Thanks for all of the suggestions and cares.

Especially to Rohit.

[Former Member]

Hi,

to prevent inaccurate data being entered into SMSY i use SMSY_SETUP to retrieve information from SLD. its more robust. you need to configure txn RZ70 on satellite systems so they send thier data to SLD and solman will use this to populate SMSY and eliminate human error.

regards,

Mani

[Former Member]

Also go through this note 1293657

I guess the notes mentioned in above posts and this one might help

Let me know if this helps

Rohit

[Former Member]

If you want to set up,you should not use refresh sessions

use request session data and then select for earlywatch alert.

I am sure if everything is set up correctly,it will work

Rohit

[Former Member]

but when I check in tcode solution_manager in my company's solman, there's no activities on that instance. That is, there's no EWA report regarding that instance.

Is there something i miss in my step?

I've spent a whole week in this case, still got no clue.

Thanks, gurus.

[Former Member]

Hi,

perhaps the service definitions in the managed system where the sessions don't appear are not uptodate. That would mean the managed system is not able to recognize that sessions are waiting to be picked up in Solution Manager. It's probably a good idea to delete and replace the service definitions: note 727998 explains how to do that.

best regards,

-David.

[Former Member]

I guess there is some problem with the configuration if early watch

Rohit Goyal

[Former Member]

David, if you read my first post thoroughly, i've replaced service definitions and applied that notes, no luck though.

Edited by: Antonius Erwin Handoko on Feb 13, 2009 3:46 PM

[Former Member]

Rohit, could you be more specific?

[Former Member]

sure...let me post the config steps for earlywatch...

check if anything is missing in ur setup...

......................................................................................................

Prerequisites

u2022 Set-up RFC connection among Solution Manager,

System and OSS.

u2022 checked the availability of the tools required for the

SAP Service sessions (in Add-On ST-A; ST-PI), with

the report RTCCTOOL .

u2022 Set-up the Automatic Session Manager (ASM) in the

Service Data Control Center (Transaction SDCCN), for

all Sattelite system and Centerl SAP Solution manager

( See Note No.: 91488)

u2022 Set-up System Landscape for Sattelite system in SAP

Solution Manager.

Process:

Execute transaction DSWP

u2022 From Menu goto->Solution Overview

u2022 Click on solution for which we need to activate Early

Watch.

u2022 Click on Solution Landscape tab.

u2022 Click on Solution Landscape Maintenance

u2022 Select Solution Setting tab.

u2022 Give the Day in field Day to Process EarlyWatch Alert

Sessions.

u2022 Click on Setup EWA push button

and then just activate the early watch alert.

.......................................................................................................

This is very simple but a fool proof setting,I have implemented and it has worked for me.

Check everythng in ur setup and let me know of any issues

Rohit

[Former Member]

i'll check again on monday and re-read EWA best practice implementation once more..

i'll update later..

thanks for help so far, gurus.

[Former Member]

Gurus,

Everytime I choose 'Maintenance Package' Task, it failed and there is this message in the log:

16.02.2009 10:11:08 Error fetching license data from destination SM_SOMCLNT200_BACK /BDL/SAPLBDL11

16.02.2009 10:11:08 > ( AGS_MK_GET_MAINT_KEYS ) /BDL/SAPLBDL11

16.02.2009 10:11:08 > Function module for retrieval of license data not available on Solution Manager /BDL/SAPLBDL11

Any ideas of what happening?

Thanks.

[Former Member]

have u checked for the configuration of EWA as mentioned by me in the previous post

Rohit

[Former Member]

Hi,

Run the report RTCCTOOL on solman and satellite systems and check if any addons like ST* are missing

This may be the reason for the error

and again check the config

Rohit

[Former Member]

Yeah, i've read your step and run RTCCTOOL in satelitte system and solman, and everything's green. I've told everything I've done in 1st post I think.

I can't find any notes regarding this "get license error" though.

Why solman can't get maintenance package...?

Trims.

[Former Member]

Hello Antonoius,

Please have a look at the following notes: 1229904,1280664 and 1134886

I guess this might help resolve your issue.

Rohit Goyal

[Former Member]

I'll try applying it.

Now I found another clues..

When I choose task 'Delete old session and log data', there's this log:

Deletion of old SDCC data completed

0 entries in message log table deleted

0 task/session entries in internal tables deleted

0 reference sessions deleted

Deletion of old SDCC data started

It seems that satellite system can't get session data from solman.

but when I check RFC connection, SOM_BACK, authorization, all's working.

[Former Member]

try creating a new maintenance package task in solman and see what happens

Rohit

[Former Member]

what happens is what i posted before, error in maintenance module...

don't know if it'll be any difference when i apply notes you mentioned earlier.

Still downloading the notes now..

[Former Member]

ok....just check with the notes..go through them and try to maintain settings as mentioned by them

they might help

[Former Member]

Finally after one full week of struggling, i've found the culprit.

The problem lied on Database name and System name in tcode: SMSY.

For those who experienced problem in EWA creation, maybe you could look into this:

We MUST type the exact name of Database and System in satellite system in solution manager.

But what if I already had that Database and System name for other system? Well, good question, since that's the root of my problem. Because SAP doesn't allow system to have the same name, I use other random name which doesn't reflect system and database name in satellite system.

For example system name is DEV. Because I've already this 'DEV' on my system, I use 'PED'.

This result in EWA failure.

So what to do next?

Solution

-

---

Use <SID><suffix> for naming convention (there's help for this in SAP, which i didn't notice earlier)

SAP will only use the first three character. That's your <SID>!! And suffix will be used to differentiate between two systems.

After changing this, voila!! All of my systems are able to generate EWA report.